Individual skill

apexcloud-retention-ops

Build ApexCloud retention-ops JSON deliverables from the public task-env API and churn CSV exports. Use when asked for customer risk queues, QBR packets, receivables and pipeline reviews, retention action boards, or churn validation/ranking from the staged ApexCloud environment.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_004/fewshot/cc/fewshot_attempt_03/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 Ops

## Start

1. Identify the deliverable family from the prompt: risk queue, QBR packet, receivables review, action board, or churn validation/ranking.
2. Read the prompt template first, then mirror its key order exactly.
3. Use [references/apexcloud_rules.md](references/apexcloud_rules.md) for field precedence, joins, and rollup rules.
4. Use [scripts/apexcloud_ops.py](scripts/apexcloud_ops.py) when a normalized draft will save time.

## Data precedence

- Use billing snapshots for ARR when the prompt asks for current ARR, exposure, or ARR at risk.
- Use exact normalized legal-name matching for A/R aging links. Do not fuzzy-match similar subsidiaries or noise rows.
- Exclude spam, duplicate, and cancelled tickets from clean support counts and SLA math.