Individual skill

apexcloud-retention-ops

Solve ApexCloud Retention Operations tasks by querying the task environment API, applying controlled vocabularies, deterministic precision rules, and standardized business-logic patterns for renewal risk queues, QBR packets, receivables reviews, churn model validation, and retention action boards.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_004/fewshot/naive/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# ApexCloud Retention Operations

## When to use this skill

Apply this skill whenever the task references the ApexCloud Retention Operations API, asks you to build retention or renewal artifacts for ApexCloud accounts, or uses any of the controlled enums and precision rules defined here. The skill covers five recurring task families: renewal risk queues, QBR metrics packets, receivables and pipeline reviews, churn model validation, and high-touch retention boards.

## Core workflow

1. Read the task prompt thoroughly and note the assessment date, analysis period, target account IDs, and the required output shape (given as a payload template or described inline).
2. Fetch data from the relevant API endpoints described in [API Endpoints](references/api-endpoints.md). Prefer parallel requests for independent calls (e.g., fetching accounts, metrics, tickets, and NPS simultaneously).
3. Transform raw API responses into derived metrics following the [Business Rules](references/business-rules.md).
4. Select policy codes using the middle-option rule from [Policy Codes](references/policy-codes.md).
5. Assemble the final JSON response using the [Controlled Vocabularies](references/vocabularies.md) and [Precision Rules](references/precision-rules.md). Return only valid JSON with no surrounding text.
Back to top