Individual skill

apexcloud-retention-ops

Build exact JSON-only reports from the ApexCloud Retention Operations API. Use when a prompt mentions ApexCloud retention data, task environment API calls, account metrics, billing, support tickets, NPS, A/R aging, opportunities, HR summary, event performance, churn exports, renewal risk queues, QBR packets, receivables reviews, retention boards, or any similar structured business output that must match an answer template and controlled label vocabulary.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_004/fewshot/cc/fewshot_attempt_01/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 Ops

Use this skill for the staged ApexCloud reporting tasks.

## Workflow

1. Read the prompt and the answer template first. Treat the template as the contract for keys, nesting, item order, and allowed enum values.
2. Identify the report family and requested slice. Read [references/api_patterns.md](references/api_patterns.md) when the prompt combines multiple data sources or the endpoint mapping is not obvious.
3. Fetch only the needed records from the local task environment described in `environment_access.md`.
4. Build a local fact table from the live data, then calculate the requested rankings, summaries, or validation metrics.
5. Keep every controlled label exactly as written in the prompt or template. Do not invent synonyms or widen the vocabularies.
6. Normalize the final JSON:
   - currency: 2 decimals
   - percentages: precision requested by the prompt