Individual skill

apexcloud-retention-ops

Solve ApexCloud Retention Operations API tasks that require strict JSON outputs for customer success QBR packets, renewal risk queues, retention action boards, A/R aging follow-ups, CRM pipeline summaries, HR/event ops context, or churn model validation and candidate ranking. Use when a prompt mentions the ApexCloud Retention Operations API, account metrics, support/NPS/billing/A/R endpoints, retention risk, receivables, pipeline operations, high-touch retention boards, or churn exports.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_004/fewshot/opencode/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
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.

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 Operations

Use this skill to turn ApexCloud Retention Operations API data into exact, schema-conforming JSON. The user prompt and any `input/payloads/answer_template.json` are authoritative for field names, labels, date windows, account lists, sort order, and rounding.

## Workflow

1. Read the prompt and answer template completely before fetching data.
2. Set the base URL from the prompt placeholder or environment note. The examples use an unauthenticated HTTP API.
3. Fetch only the business endpoints needed for the requested output. Prefer aggregate billing and A/R endpoints, because account-specific billing/A/R routes may be unavailable in the runtime.
4. Read [references/apexcloud_rules.md](references/apexcloud_rules.md) before calculating final values.
5. Optionally run [scripts/apexcloud_ops.py](scripts/apexcloud_ops.py) to normalize account features, QBR monthly metrics, receivables/pipeline summaries, or churn scores. Treat the script as a helper; the prompt/template still win. Use `--include-all-expansion-reasons` only when the prompt is board-style and wants every open expansion context row surfaced.
6. Return only valid JSON. Do not include prose, comments, markdown fences, or extra keys.

## Common Conventions
Back to top