Individual skill
atlas-commerce-ops-review
Solve Atlas Commerce Operations cutoff-based analytical review tasks (fulfillment, refund, carrier, warehouse, support). Read request + template contracts literally, replay event history at a cutoff, dedup imported rows, and produce a JSON object that conforms exactly to the answer template.
experiments/claude_code_glm_5_2_max/reports/skills/task_group_022/reflect-3/reflect-3_attempt_01/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
# Atlas Commerce Operations Review
These tasks ask for a **cutoff-based operational review**: take a cohort of production business records, freeze their state at an as-of cutoff, apply stated business definitions/SLAs/status policies, and emit one JSON object conforming **exactly** to an answer template. The plumbing (query service, schema, data dictionary, auth) is provided in the environment; this skill is the analytical methodology.
## 0. Read the contract before writing a line of SQL
Every task ships two JSON files in `input/payloads/`:
- a **request** (`*_request.json`): scope, windows, cutoff, business definitions, thresholds, status rules, ordering/tie-breaks.
- an **answer template** (`answer_template.json`): the exact output schema.
Treat both as load-bearing contracts:
- The **template** is the output law. `required`, `additionalProperties:false`, `minItems/maxItems`, `pattern`, `multipleOf`, and each field's `description` / `x-precision` define what to compute and how to format it. Emit **only** the schema's fields, in its shape, no commentary, no extra keys. Mismatched precision or an extra key fails the whole object.
- The **request definitions** are literal. Every clause carries weight: `inclusive`/`exclusive`, `at or before` vs `strictly before`, `more than 24 hours`, `below` (strict `<`) vs `at least` (>=), which count is the **denominator**. Decide each threshold operator from the wording; `>` vs `>=` flips borderline counts and everything downstream (rates, status, IDs).
