ApexCloud Retention Ops
Use this skill to solve ApexCloud Retention Operations tasks by fetching the allowed API/export data, reconciling source precedence, and returning the requested JSON only.
Standard Workflow
Read the user prompt and any input/payloads/answer_template.json.
Identify the task family: renewal risk queue, retention action board, QBR metrics packet, receivables/pipeline operations review, or churn validation/outreach ranking.
Use the API base URL supplied in the prompt. If the prompt contains <TASK_ENV_BASE_URL>, substitute the task environment base URL available to the solver.
Prefer the bundled helper for deterministic extraction and shaping:
python scripts/apex_ops.py \
--prompt /path/to/input/prompt.txt \
--template /path/to/input/payloads/answer_template.json \
--base-url http://task-env:9004/
Omit --template when there is no template. The script writes one JSON object to stdout.
Inspect the JSON before returning it. Verify top-level keys, enum values, sort order, and precision against the prompt/template.
Return only JSON. Do not include commentary, markdown fences, or intermediate calculations in the final answer.
Source Rules
Read references/apex_rules.md when you need to reason manually or verify the script output. The most important conventions are:
- Current ARR comes from posted
/api/billing/snapshots at the task as-of date; fall back to account profile ARR only when no snapshot exists.
- Clean support tickets exclude duplicates, spam, and cancelled tickets; count only
open and closed tickets.
- SLA compliance is the percentage of clean tickets where both first-response and resolution SLA flags are true.
- A/R overdue balance uses only older buckets:
61_90 + 90_plus.
- A/R rows link to CRM accounts by exact legal-name match, not aliases or similar names.
- Open expansion pipeline is summed from open opportunities with close dates inside the requested window.
- Currency uses two decimals, percentages use one decimal, scores/counts are integers, and probabilities use three decimals unless the prompt says otherwise.
Helper Coverage
The helper script is intentionally portable: it uses only the Python standard library and API/export endpoints listed in the task environment. It can parse common prompt wording for:
- Account IDs, date ranges, months, as-of dates, and top-N requests.
- Retention-board follow-up calendars.
- Receivables follow-up due dates.
- QBR account, quarter months, and review due date.
- Churn candidate shortlists.
If parsing fails, do the same computation manually from the rules reference, then shape output with the template.
Policy Codes
When the answer template asks for policy code fields, use the ApexCloud conventions inferred for this API:
- Risk model:
RS-6
- ARR source:
REV-4
- Support hygiene:
SUP-8
- Action priority:
ACT-5
- Board sort:
BORD-4
- Exposure formula:
EXP-6
- Calendar policy:
CAL-5
- Receivable trigger:
RCP-7
- CRM match:
CM-5
- Pipeline window:
PW-6
- Follow-up scope:
FS-4
- Churn model protocol:
MOD-7
- Churn probability scale:
PRB-4
- Churn deployment rule:
DEP-5
- Outreach mapping:
OUT-2
1---2name: apex-retention-ops3description: Use this skill whenever a task asks for JSON from the ApexCloud Retention Operations API, including renewal risk queues, retention action boards, QBR metrics packets, receivables and pipeline reviews, churn export validation, outreach rankings, A/R aging, billing snapshots, support/NPS/usage health, CRM opportunities, HR/event operations context, or ApexCloud policy codes. Trigger even when the user only mentions ApexCloud, customer success operations, QBR metrics, AR aging, churn exports, or a controlled-answer template.4metadata:5 source: https://skillmd.com/skills/prism-shadow/apex-retention-ops6---78# ApexCloud Retention Ops910Use this skill to solve ApexCloud Retention Operations tasks by fetching the allowed API/export data, reconciling source precedence, and returning the requested JSON only.1112## Standard Workflow13141. Read the user prompt and any `input/payloads/answer_template.json`.152. Identify the task family: renewal risk queue, retention action board, QBR metrics packet, receivables/pipeline operations review, or churn validation/outreach ranking.163. Use the API base URL supplied in the prompt. If the prompt contains `<TASK_ENV_BASE_URL>`, substitute the task environment base URL available to the solver.174. Prefer the bundled helper for deterministic extraction and shaping:1819 ```bash20 python scripts/apex_ops.py \21 --prompt /path/to/input/prompt.txt \22 --template /path/to/input/payloads/answer_template.json \23 --base-url http://task-env:9004/24 ```2526 Omit `--template` when there is no template. The script writes one JSON object to stdout.275. Inspect the JSON before returning it. Verify top-level keys, enum values, sort order, and precision against the prompt/template.286. Return only JSON. Do not include commentary, markdown fences, or intermediate calculations in the final answer.2930## Source Rules3132Read [references/apex_rules.md](references/apex_rules.md) when you need to reason manually or verify the script output. The most important conventions are:3334- Current ARR comes from posted `/api/billing/snapshots` at the task as-of date; fall back to account profile ARR only when no snapshot exists.35- Clean support tickets exclude duplicates, spam, and cancelled tickets; count only `open` and `closed` tickets.36- SLA compliance is the percentage of clean tickets where both first-response and resolution SLA flags are true.37- A/R overdue balance uses only older buckets: `61_90 + 90_plus`.38- A/R rows link to CRM accounts by exact legal-name match, not aliases or similar names.39- Open expansion pipeline is summed from open opportunities with close dates inside the requested window.40- Currency uses two decimals, percentages use one decimal, scores/counts are integers, and probabilities use three decimals unless the prompt says otherwise.4142## Helper Coverage4344The helper script is intentionally portable: it uses only the Python standard library and API/export endpoints listed in the task environment. It can parse common prompt wording for:4546- Account IDs, date ranges, months, as-of dates, and top-N requests.47- Retention-board follow-up calendars.48- Receivables follow-up due dates.49- QBR account, quarter months, and review due date.50- Churn candidate shortlists.5152If parsing fails, do the same computation manually from the rules reference, then shape output with the template.5354## Policy Codes5556When the answer template asks for policy code fields, use the ApexCloud conventions inferred for this API:5758- Risk model: `RS-6`59- ARR source: `REV-4`60- Support hygiene: `SUP-8`61- Action priority: `ACT-5`62- Board sort: `BORD-4`63- Exposure formula: `EXP-6`64- Calendar policy: `CAL-5`65- Receivable trigger: `RCP-7`66- CRM match: `CM-5`67- Pipeline window: `PW-6`68- Follow-up scope: `FS-4`69- Churn model protocol: `MOD-7`70- Churn probability scale: `PRB-4`71- Churn deployment rule: `DEP-5`72- Outreach mapping: `OUT-2`