Individual skill
apexcloud-retention-ops
Build ApexCloud retention operations artifacts (risk queues, QBR packets, receivables reviews, churn model validations, and retention boards) from the ApexCloud Retention Operations API. Covers all public endpoints, data-cleaning conventions, controlled vocabularies, policy codes, and cross-source reconciliation patterns used in production retention workflows.
experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_004/fewshot/naive/fewshot_attempt_01/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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
- data 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
When a task asks you to produce a retention operations artifact using the
ApexCloud Retention Operations API, follow the process below. Every step is
deterministic and grounded in the API data shapes documented here.
## 1. Connect and Verify
The API base URL is provided in the task prompt as `<TASK_ENV_BASE_URL>`.
Replace that token with the actual URL before making any call. Start with
`GET /api/health` to confirm the service is reachable and to see current row
counts.
All responses are JSON unless the endpoint path includes `.csv`. The API has no
authentication.