Individual skill

task-group-004-fewshot-attempt-03

Use for ApexCloud CRM retention analytics tasks that call the ApexCloud Retention Operations API and must return strict JSON for renewal risk queues, QBR metrics packets, receivables and pipeline reviews, churn validation/ranking, or high-touch retention action boards. Captures reusable endpoint usage, source-of-truth choices, data hygiene rules, controlled enum mappings, policy-code conventions, and output formatting pitfalls.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_004/demonstration_skill/demonstration_skill_attempt_03/apexcloud-retention-analytics/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 Analytics

## Core Workflow

1. Read the task prompt and answer template first. Preserve the template's top-level keys, nested field names, nullability, list lengths, enum vocabularies, and requested sort order.
2. Use only the API base URL and public endpoint families provided in the current prompt. Do not reuse ports or paths from prior examples if the current task gives different ones.
3. Filter every source by the prompt's account IDs, region, months, date range, quarter, as-of date, and candidate shortlist. Treat date ranges as inclusive.
4. Compute from raw API data, then round only final values: currency to 2 decimals, percentages to 1 decimal, churn probabilities to 3 decimals, counts and risk scores as integers.
5. Return JSON only. Do not include explanations, markdown, comments, extra keys, or enum values outside the template.

## API Source Map

- Account profile: `/api/accounts` and `/api/accounts/<account_id>` provide canonical `account_id`, names/aliases, region, segment, lifecycle status, renewal date, tenure, CRM ARR, and current billing ARR hints.
- Monthly metrics: `/api/accounts/<account_id>/metrics?start=YYYY-MM&end=YYYY-MM` provides recognized revenue, product usage, active seats, monthly NPS status, and coarse support/SLA metrics.
Back to top