Individual skill

atlas-commerce-ops-solver

Solve Atlas Commerce Operations workplace tasks that require authenticated schema discovery, read-only SQL analysis, strict answer_template.json output, and occasionally an explicitly approved canonical correction through /api/sql/transaction and correction audit verification. Use when a prompt mentions TASK_ENV_BASE_URL, Atlas Commerce Operations, /api/schema, /api/data-dictionary, /api/sql, /api/sql/transaction, correction-audit, fulfillment scorecards, refund reconciliation, carrier scan quality, warehouse productivity, or support health analytics.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_022/fewshot/naive/fewshot_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

# Atlas Commerce Operations Solver

## Workflow

1. Read the user prompt, every request payload, and the answer template before querying data.
2. Use the task's environment-access instructions only to obtain the base URL and API token. Never call `/api/judge`.
3. Fetch `/api/schema` and `/api/data-dictionary` for the live task; do not assume the schema is unchanged.
4. Load [references/query-patterns.md](references/query-patterns.md) before writing nontrivial SQL, money logic, active-time logic, or a correction transaction.
5. Build SQL as layered CTEs: cohort, effective source rows, per-entity rollups, final aggregations, ranked rows, and output checks.
6. Prefer several narrow verification queries over one opaque query. Reconcile cohort counts, denominator counts, status distributions, and top/bottom rankings before writing `answer.json`.
7. Write exactly one JSON object matching the template. Include no commentary, no extra fields, and no trailing narrative.

Use [scripts/atlas_api.py](scripts/atlas_api.py) when it helps: