Menu

Individual skill

apexcloud-retention-ops

0upvotes

Solve ApexCloud Retention Operations analytics tasks against the remote Retention Operations API. Encode and reproduce the exact business rules, data-hygiene conventions, policy codes, ranking/precision rules, churn-model spec, and per-archetype output schemas. Use for any CRM retention task (renewal risk queue / save plan, QBR metrics packet, receivables + pipeline operations digest, churn model validation + outreach ranking, high-touch retention action board / watchlist).

experiments/claude_code_glm_5_2_max/reports/skills/task_group_004/fewshot/fewshot_attempt_03/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 — Solver Skill

This skill is the executable experience for the ApexCloud CRM retention-analytics evaluation. A future solver receives ONLY this file + a test prompt + the env URL and must reproduce every convention exactly. Read the test prompt, identify the archetype, apply the universal rules below, then the archetype-specific section.

## 0. Environment

- The API base URL is the REMOTE ApexCloud Retention Operations API. Read it from `ENV_URL.txt` in the task staging directory (a single line like `http://host:port`). Do NOT assume the `http://127.0.0.1:8074` written inside prompt bodies — that is a placeholder; the real base is in `ENV_URL.txt`.
- All endpoints are JSON over HTTP GET unless noted. Append paths to the base URL.

### Endpoints (all confirmed against the live schema)
| Endpoint | Returns | Key fields |
|---|---|---|
| `/api/health` | row_counts + status | sanity check; confirms dataset sizes |
| `/api/accounts` | `{accounts:[...]}` | `account_id`, `legal_name`, `account_aliases`, `segment`, `region`, `renewal_date`, `contract_tenure_months`, `crm_arr`, `billing_arr_current`, `lifecycle_status`, `product_plan` |
Back to top