Menu

Individual skill

atlas-ops-solver

0upvotes

Solve Atlas Commerce Operations tasks that require querying the authenticated workplace API, computing exact operational metrics from the Atlas Commerce database, emitting schema-conformant JSON answers, or applying narrowly approved canonical data corrections with audit records. Use for Atlas fulfillment, refund reconciliation, carrier quality, warehouse productivity, support health, inventory, order, payment, and similar cutoff-based analytics tasks.

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

Use this skill for Atlas Commerce Operations database tasks. The common shape is: read a prompt plus request payloads, query the workplace API, compute metrics with SQL, and write exactly one `answer.json` object matching the supplied answer template.

## Required Workflow

1. Read the task prompt, every file under `input/payloads/`, and the answer template before querying.
2. Treat the request payload as the metric contract and the answer template as the output contract. If the prompt and payload differ, follow the payload for business rules and the template for field names/types.
3. Resolve the runtime base URL and token from the task prompt or environment. Do not hard-code training URLs, tokens, request IDs, entity IDs, dates, counts, or answer values.
4. Call `GET /api/schema` and `GET /api/data-dictionary` before writing SQL. Use the returned schema as authoritative.
5. For analytical requests, use only `POST /api/sql`. Do not mutate data.
6. For correction requests, mutate only when the prompt explicitly asks for a controlled correction and the request payload supplies an approved correction. Use pre-change queries, the controlled transaction endpoint, audit verification, and post-change queries before reporting `APPLIED`.
7. Never call `POST /api/judge`.
8. Write only valid JSON to `answer.json`. Include no commentary, no markdown, no extra keys, and no trailing text.
Back to top