Individual skill
reflect-3
Use this skill for ApexCloud Retention Operations-style tasks that provide a remote environment and ask for a precise JSON answer from customer/account, opportunity, retention, billing, support, NPS, churn, or event datasets. It is especially useful when the task involves staged prompts, remote API discovery, exact output schemas, account alias resolution, active/open exclusions, ARR reconciliation, pipeline rollups, renewal windows, or churn-risk style filtering.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_004/reflect-3/reflect-3_attempt_03/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Reflect-3 Retention Operations Skill
Use this skill when a task asks you to answer a retention-operations data question from a remote environment. The work is usually more about careful data access, exact filtering, and exact JSON shape than about producing a narrative analysis.
## Core Workflow
1. Treat the task prompt as the contract.
Read it for the requested output fields, date window, sort order, inclusion/exclusion rules, rounding, and whether the answer should be a scalar, object, or array. Do not add helpful extra fields unless the prompt explicitly asks for them.
2. Use only the provided remote environment.
Start from the base URL or environment note supplied with the task. Do not inspect local environment source, evaluator files, hidden data folders, prior run outputs, or neighboring scratch directories.
3. Probe the public API lightly and deliberately.
Begin with the health/status endpoint if one is available. Use it to learn the service name, seed, and advertised row counts. Then fetch only public data endpoints needed for the task. Confirm each payload's top-level key and row count before analysis.