ApexCloud Retention Ops
Use this skill for the staged ApexCloud reporting tasks.
Workflow
- Read the prompt and the answer template first. Treat the template as the contract for keys, nesting, item order, and allowed enum values.
- Identify the report family and requested slice. Read references/api_patterns.md when the prompt combines multiple data sources or the endpoint mapping is not obvious.
- Fetch only the needed records from the local task environment described in
environment_access.md. - Build a local fact table from the live data, then calculate the requested rankings, summaries, or validation metrics.
- Keep every controlled label exactly as written in the prompt or template. Do not invent synonyms or widen the vocabularies.
- Normalize the final JSON:
- currency: 2 decimals
- percentages: precision requested by the prompt
- probabilities: 3 decimals when requested
- counts and scores: integers unless the template says otherwise
- Verify the result before returning it:
- item count matches the prompt
- ranks and sort order match the instructions
- totals reconcile with item-level values
- nulls, booleans, and strings match the template types
- no extra prose, markdown, or code fences
Output discipline
Return only the JSON object. If the template includes policy or model codes, choose from the template's allowed values and do not invent new ones.