Individual skill
apexcloud-retention-ops
Solve ApexCloud Retention Operations API tasks that require JSON-only customer success, renewal risk, QBR, receivables, pipeline, operations, or churn-export outputs. Use when prompts mention the ApexCloud Retention Operations API, billing snapshots, A/R aging, account metrics, support tickets, NPS, opportunities, HR/event operations context, or churn CSV exports.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_004/fewshot/codex/fewshot_attempt_03/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# ApexCloud Retention Operations
## Core Workflow
Read the prompt and any answer template provided with the task first. Produce only the JSON object requested by the prompt or template; keep key order and controlled enum values from the template.
Resolve `<TASK_ENV_BASE_URL>` from the task environment instructions. Do not hard-code a training URL. Fetch data with the public API/exports named in the prompt, then filter locally when an endpoint returns a portfolio collection.
Prefer these endpoint families:
- Accounts: `/api/accounts`, `/api/accounts/{account_id}`
- Metrics: `/api/accounts/{account_id}/metrics?start=YYYY-MM&end=YYYY-MM`
- Tickets: `/api/accounts/{account_id}/tickets?start=YYYY-MM-DD&end=YYYY-MM-DD`
- NPS: `/api/accounts/{account_id}/nps?start=YYYY-MM-DD&end=YYYY-MM-DD`