Menu

Individual skill

apexcloud-retention-ops

0upvotes

Use this skill for ApexCloud Retention Operations tasks that ask for renewal-risk queues, QBR metric packets, receivables and pipeline operations reviews, churn validation, or high-touch retention action boards. Trigger whenever the prompt references ApexCloud customer success, retention operations, support/NPS/billing/A/R reconciliation, churn exports, or structured JSON outputs with controlled enum labels.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_004/reflect-3/reflect-3_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 workflow to build structured JSON answers from the ApexCloud Retention Operations API. The task usually combines CRM accounts, monthly account metrics, support tickets, NPS, billing snapshots, A/R aging, opportunities, HR context, event performance, and churn exports.

## Core Workflow

1. Read the prompt and the answer template before touching data.
2. Copy the required top-level structure, nested field names, enum vocabulary, and output cardinality from the template.
3. Fetch only the endpoint families named or implied by the prompt.
4. Filter locally by account IDs, dates, months, quarter, region, and event IDs from the prompt.
5. Reconcile accounts by `account_id` first, then exact legal name or listed aliases. Avoid fuzzy matching unless the prompt explicitly asks for it.
6. Apply exclusions before counting or scoring: duplicate/spam tickets, retracted NPS, out-of-window opportunities, non-posted billing snapshots, and A/R records from the wrong `as_of` date.
7. Round only at the final output step: currency to 2 decimals, percentages to 1 decimal, integer counts and ranks, churn probabilities to 3 decimals when requested.
8. Return JSON only. Do not include explanatory text, markdown, comments, or trailing notes.
Back to top