Individual skill

atlas-commerce-ops-sql-analyst

Solve Atlas Commerce Operations workplace tasks that provide prompt/payload files, a strict answer_template.json, and a TASK_ENV_BASE_URL with schema, data-dictionary, SQL, correction-audit, or controlled transaction endpoints. Use for fulfillment, refunds, carrier quality corrections, warehouse productivity, support health, inventory/order/payment analytics, and similar cutoff-based operational JSON reports.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_022/fewshot/naive/fewshot_attempt_02/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 Ops SQL Analyst

Use this skill to calculate strict JSON answers from the Atlas Commerce Operations service. Always compute from the live workplace data; never reuse values from examples or prior runs.

## Required Workflow

1. Read `input/prompt.txt`, every file under `input/payloads/`, and especially `answer_template.json`.
2. Extract the business scope, cutoff/window boundaries, ordering rules, rounding rules, status/risk rules, and mutation permission from the request payload.
3. Resolve `<TASK_ENV_BASE_URL>` and the provided authorization token. Do not call `POST /api/judge`.
4. Fetch `GET /api/schema` and `GET /api/data-dictionary` before writing SQL. Confirm table and column names from the live service.
5. Use `POST /api/sql` for read-only analysis:

```bash
curl -sS \