Individual skill

apexcloud-retention-ops

Use this skill for ApexCloud Retention Operations API tasks that ask for renewal risk queues, QBR metric packets, receivables and pipeline reviews, churn validation/ranking, or high-touch retention action boards. It gives the endpoint habits, filtering rules, source priorities, controlled enum conventions, precision rules, and common pitfalls needed to produce JSON-only answers from the public ApexCloud environment.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_004/self/self_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 Operations

Use this skill when a task references the ApexCloud Retention Operations API and asks for a structured operations, customer success, finance, or churn-risk JSON output.

## First Moves

1. Read the prompt and the supplied `input/payloads/answer_template.json` before calculating anything. The prompt sometimes omits fields that the template requires, especially `policy_codes`.
2. Use the remote API entrypoint given by the task environment. If the prompt says `http://127.0.0.1:8074` but the evaluation workspace provides a remote base URL, replace only the host/base with the provided remote base and keep the same paths.
3. Query only public API/export endpoints. Do not inspect local environment source or data files.
4. Build a small local table keyed by `account_id`, then join finance, billing, support, NPS, opportunity, HR, event, or churn data into it as the prompt requires.
5. Return only valid JSON. Do not include prose, markdown fences, comments, or explanatory text.

Useful health/schema probe:
Back to top