Menu

Individual skill

reflect-3-attempt-02

0upvotes

ApexCloud Retention Operations — reusable rules and verified conventions for producing renewal-risk, QBR, receivables/pipeline, churn-model, and retention-board answers from the data API.

experiments/claude_code_glm_5_2_max/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 — Verified Conventions

Reusable rules for answering the five task archetypes served by the ApexCloud Retention Operations API. Every rule below was checked against the train judge; conventions marked **VERIFIED** produced correct deterministic fields (train_003 reached 1.0; train_002 deterministic block correct). Items marked **BEST-GUESS** could not be fully recovered from scalar feedback and should be applied with the stated logic.

## Environment & API
- Base URL: read from `ENV_URL.txt` (data API). Judge path from `JUDGE_PATH.txt`. All endpoints are read-only JSON.
- Endpoints: `/api/health`, `/api/accounts`, `/api/accounts/<id>`, `/api/accounts/<id>/metrics?start=YYYY-MM&end=YYYY-MM`, `/api/accounts/<id>/tickets`, `/api/accounts/<id>/nps`, `/api/billing/snapshots`, `/api/finance/ar-aging?as_of=YYYY-MM-DD`, `/api/opportunities`, `/api/hr/summary?quarter=YYYY-QN&region=...`, `/api/events/performance?event=...&quarter=YYYY-QN`, `/exports/churn/{train,validation,candidates}.csv`, `/exports/account_metric_extract.csv`.
- `accounts` endpoint returns `{"accounts":[...]}`; `billing/snapshots` returns `{"snapshots":[...]}` (key `billing_arr`, field `posted: true`, quarterly `as_of` = 03-31/06-30/09-30/12-31); `ar-aging` returns `{"ar_aging":[...]}` (buckets `1_30, 31_60, 61_90, 90_plus`, keyed by `customer_name` = legal name, NO account_id field); opportunities have `account_id`, `stage`, `close_date`, `amount`, `state`.

## Precision (deterministic, apply always)
- Currency → 2 decimals. Percentages → 1 decimal. Counts and risk scores → integers. Churn probabilities → 3 decimals. NPS score → integer. Dates → `YYYY-MM-DD` / `YYYY-MM`.

## 1. ARR source **VERIFIED**
- `current_arr` = `billing_arr` from the **posted** billing snapshot whose **`as_of` == the assessment date**. Snapshots are quarterly; the assessment date (e.g. 2026-06-30) always matches a quarter-end `as_of`.
Back to top