Individual skill
apexcloud-retention-ops
Solve ApexCloud Retention Operations API tasks that require customer success, billing, receivables, pipeline, event, HR, or churn-export analysis and JSON-only business outputs.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/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
- 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 Ops
Use this skill when a task asks for an ApexCloud Retention Operations API analysis and a structured JSON answer. Treat the prompt and `input/payloads/answer_template.json` as the contract. Compute from the live API at the supplied `<TASK_ENV_BASE_URL>`; never reuse staged example answers or hard-code account-specific results.
## One-Pass Solver Flow
1. Read the prompt, extract the requested account IDs, dates, months, quarter, region/event filters, due dates, ranking size, enum vocabularies, and required top-level JSON shape.
2. Query only the public GET endpoints named in the task or needed for the requested fields. Prefer a small local script using standard-library `urllib`, `json`, `csv`, `datetime`, and `decimal` so calculations are repeatable.
3. Build normalized records first, then fill the answer template exactly. Omit any template-only keys that the prompt excludes, but include required policy/model code blocks when present in the template.
4. Return JSON only. Use numbers, booleans, and nulls as JSON values, not strings.
## Endpoint Guide
Use these endpoint families by data need: