Individual skill
atlas-ops-sql-solver
Use this skill for Atlas Commerce Operations tasks that require exact JSON answers from prompt payloads and the authenticated Atlas database, including cutoff-based fulfillment scorecards, refund reconciliation, carrier-scan canonical corrections, warehouse productivity reviews, support health reviews, and similar operational analytics. It guides schema discovery, SQL against the Atlas API, de-duplication of source imports, event-timeline logic, controlled corrections, rounding, ordering, risk/status rules, and answer.json validation.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_022/fewshot/cc/fewshot_attempt_02/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
- data Derived category
- operations Derived category
- productivity Derived category
- data-databases Derived category
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 Operations SQL Solver
Use this when the task references the Atlas Commerce Operations workplace, `<TASK_ENV_BASE_URL>`, `answer_template.json`, or a request payload asking for an exact `answer.json`.
## Core Workflow
1. Read the prompt, `input/payloads/answer_template.json`, and every request payload before querying.
2. Extract the cohort, cutoff/window boundaries, metric definitions, ranking tie-breakers, rounding rules, status/risk policy, and required output fields.
3. Call `GET /api/schema` and `GET /api/data-dictionary`; do not assume table details from memory if the live schema is available.
4. Use `POST /api/sql` with `{"sql":"..."}` for read-only analysis. It returns `{columns, rows, row_count, truncated}`.
5. For correction tasks, use read-only SQL to identify the single approved target first. Use `POST /api/sql/transaction` only when the request explicitly asks for an approved correction, then verify the business row, audit row, and post-change analytics.
6. Compute with SQL CTEs where possible, keeping unrounded values for ordering and policy thresholds. Round only final reported numbers.
7. Write exactly one JSON object to `answer.json` that conforms to the template: no commentary, no extra keys, arrays in the requested order.
