Individual skill

apex-retention-ops

Analyze ApexCloud Retention Operations API tasks that ask for JSON retention queues, QBR packets, receivables reviews, pipeline summaries, high-touch action boards, or churn export rankings. Use when prompts mention ApexCloud, TASK_ENV_BASE_URL, account metrics, tickets, NPS, billing snapshots, A/R aging, opportunities, HR or event summaries, or churn CSV exports and require controlled enums, policy codes, ranking, or deterministic precision.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_004/fewshot/deepagents/fewshot_attempt_02/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

# Apex Retention Ops

## Workflow

1. Read the prompt and the provided answer template first.
2. Query only the task environment endpoints that the prompt calls for.
3. Preserve the template shape exactly, including any extra top-level keys.
4. Use the live API as the source of truth; do not infer values from memorized examples.
5. Format numbers to the precision the prompt requests and return JSON only.

## Core Rules

- Use billing snapshots for current ARR when the task asks for ARR or exposure.
- Use account profile fields for segment, region, renewal date, tenure, lifecycle status, and owner context.
Back to top