Menu

Individual skill

task-group-004-fewshot-attempt-01

0upvotes

Build ApexCloud CRM retention analytics outputs from the ApexCloud Retention Operations API and strict JSON answer templates. Use for tasks involving renewal risk queues, QBR metrics packets, receivables and pipeline operations reviews, churn model validation, candidate outreach ranking, high-touch retention action boards, or any ApexCloud CRM retention workflow requiring controlled labels, policy codes, deterministic rounding, and JSON-only output.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_004/demonstration_skill/demonstration_skill_attempt_01/demonstration-skill-attempt-01/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 Analytics

## Core Workflow

1. Read the user prompt and the provided answer template first. Treat the template as authoritative for top-level keys, nested fields, nullability, enum vocabulary, and whether policy-code blocks must be returned.
2. Use only the account IDs, date ranges, months, regions, quarters, events, and due dates requested by the prompt. Do not add extra accounts unless the prompt asks for an all-region/all-customer summary.
3. Query the ApexCloud Retention Operations API using the base URL from the current prompt or harness. In this eval family, a shared proxy may be provided at `http://127.0.0.1:8066` even when prompt text references the original local service port.
4. Reconcile data by stable identifiers first: `account_id` for CRM/account/metrics/tickets/NPS/opportunities, exact CRM account or legal customer name for A/R matching, and explicit event or quarter parameters for operations context.
5. Calculate fields from source data, then sort, rank, round, and validate against the template. Return one JSON object only, with no Markdown, comments, or explanatory text.

## API Usage

Use endpoint families named in the prompt. Common ApexCloud public endpoints include:
Back to top