Individual skill
apexcloud-retention-ops
Build strict JSON reports from the ApexCloud Retention Operations API for customer success QBR metrics, renewal risk queues, receivables and pipeline operations reviews, retention action boards, and churn export validation or outreach ranking. Use when a task mentions ApexCloud, Retention Operations API, account health metrics, billing snapshots, A/R aging, support/NPS, opportunities, HR/event context, or churn CSV exports.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_004/fewshot/codex/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
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,134 bytesSKILL.mdcore · 5,134 bytesSKILL.mdcore · 5,134 bytesagents/openai.yamlasset · 234 bytesreferences/apexcloud_workflows.mddoc · 10,887 bytesscripts/apexcloud_report.pyruns · 26,616 bytesyaml.pyruns · 2,044 bytes
Read excerpt
# ApexCloud Retention Ops
## Workflow
1. Read the prompt and its answer template first. Extract the base URL, date range, month list or quarter, A/R as-of date, account IDs, due dates, requested count/order, allowed enum labels, and required JSON shape.
2. Fetch only the allowed ApexCloud Retention Operations API endpoints needed for the requested report. Filter dates inclusively and filter rows locally if an endpoint returns a full year or full portfolio.
3. Read [references/apexcloud_workflows.md](references/apexcloud_workflows.md) for endpoint fields, joins, and report recipes before doing nontrivial calculations.
4. Use [scripts/apexcloud_report.py](scripts/apexcloud_report.py) for deterministic normalization when helpful. It uses only the Python standard library and outputs helper JSON for QBR rows, account risk facts, receivables/pipeline summaries, and churn export summaries.
5. Return only JSON matching the prompt/template. Do not include notes, citations, markdown, or extra keys.
## Core Conventions
- Treat ISO date ranges as inclusive. Treat month ranges as inclusive by `YYYY-MM`.
- Prefer billing snapshot ARR over account `crm_arr` or profile ARR whenever the output asks for current ARR, ARR at risk, revenue exposure, or the model check asks whether billing ARR was used.