Individual skill
apexcloud-retention-ops-json
Use this skill for ApexCloud Retention Operations tasks that ask for structured JSON from account, metrics, support, NPS, billing, A/R aging, opportunities, HR, events, or churn export data. Trigger it whenever the prompt asks for renewal risk queues, retention action boards, QBR metrics packets, receivables and pipeline operations reviews, churn validation, or any controlled-enum customer-success operations output.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_004/reflect-3/reflect-3_attempt_01/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- operations Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,415 bytes
Read excerpt
# ApexCloud Retention Operations JSON
## Core Workflow
Start from the prompt and the answer template. The template is the contract: preserve every top-level key, nested key, list shape, enum vocabulary, date string, and null-vs-number convention unless the prompt explicitly says otherwise. Return JSON only.
Use the API base URL supplied in the prompt. If the prompt names endpoint families, prefer those exact paths over guessing from dataset filenames. The service often exposes richer account-scoped endpoints than top-level file-style routes.
Work in this order:
1. Read the prompt parameters: account IDs, region, quarter/date range, months, A/R as-of date, event ID, due dates, and controlled enum lists.
2. Fetch only the relevant endpoint families and date ranges.
3. Build a local reconciliation table keyed by `account_id`, plus legal/display/alias names for A/R customer matching.
4. Apply exclusions and filters before aggregating.