Menu

Individual skill

apexcloud-retention-ops

0upvotes

Solve ApexCloud Retention Operations API tasks that ask for customer success, renewal risk, QBR metrics, receivables, pipeline, event/HR context, or churn-ranking JSON outputs. Use when a prompt references the ApexCloud Retention Operations API, account metrics, tickets, NPS, billing snapshots, A/R aging, opportunities, HR summaries, event performance, churn CSV exports, or controlled retention policy/action codes.

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

# ApexCloud Retention Ops

Use this skill to produce deterministic JSON answers from the ApexCloud Retention Operations API.

## Operating Rules

1. Read the task prompt and `input/payloads/answer_template.json` first. The template is authoritative for keys, enum vocabulary, nullability, and top-level objects.
2. Replace `<TASK_ENV_BASE_URL>` with the base URL supplied by the task environment. Use only public GET endpoints mentioned by the prompt or environment access file. Never call judge or POST endpoints.
3. Fetch source data, then filter client-side. Some documented per-account endpoint families may be exposed as global collection endpoints instead; tolerate `not_found` and use the collection endpoint.
4. Return JSON only. Preserve the template shape exactly, omit no required keys, and use controlled enum strings exactly as shown.
5. Round only at output boundaries: currency to 2 decimals, percentages to 1 decimal, risk scores/counts as integers, and churn probabilities to 3 decimals.

## Source Mapping
Back to top