Individual skill

apexcloud-retention-ops

Use this skill for ApexCloud Retention Operations API tasks that ask for customer success, renewal risk, QBR metrics, receivables, pipeline, churn-model validation, or retention action-board JSON outputs. It is especially useful when prompts mention ApexCloud, account metrics, support tickets, NPS, billing snapshots, A/R aging, opportunities, HR/event context, churn exports, controlled labels, policy codes, or answer templates; use it even when the user only asks for the final JSON.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_004/self/self_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
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

This skill helps solve structured ApexCloud retention-operations tasks. The work is mostly data reconciliation: gather the requested records from the public API, apply strict exclusions and date windows, then emit JSON that exactly matches the prompt or template.

## First Moves

1. Read the user prompt and any `input/payloads/answer_template.json` before querying data. The template is the schema source of truth when it exists, including fields such as `policy_codes` that may not be repeated in the prose.
2. Use the environment entrypoint from `environment_access.md` when present. If a prompt says `http://127.0.0.1:8074` but the evaluation supplies a remote `GDPEVO_ENV_BASE_URL`, replace the local URL with the remote base URL and keep the same paths.
3. Query only the endpoint families named by the task, plus directly needed lookup endpoints such as `/api/accounts`.
4. Filter to the exact account IDs, regions, dates, quarters, events, and candidate IDs named in the prompt. Do not expand the portfolio unless the prompt says all regions or all accounts.
5. Return JSON only. No Markdown, explanations, comments, trailing commas, or extra top-level keys.

## Endpoint Habits