Individual skill

atlas-commerce-ops

Solve Atlas Commerce Operations database tasks that require cutoff-based operational analytics, source-stream reconciliation, or controlled canonical data corrections through the Atlas API. Use when prompts provide JSON request payloads and answer templates for fulfillment, refunds, carrier quality, warehouse productivity, support health, inventory, orders, payments, shipments, or similar Atlas Commerce workflows.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_022/self/self_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 Ops

Use this skill to turn an Atlas Commerce Operations request payload plus answer template into an exact `answer.json`.

## Required Workflow

1. Read the prompt, every request payload, and the answer template before querying.
2. If `environment_access.md` is present, use only its base URL, auth token, and allowed endpoints for network access.
3. Fetch `/api/schema` and `/api/data-dictionary` at the start of each task. Treat the live schema as authoritative.
4. Use `POST /api/sql` only for analytical `SELECT` or `WITH` queries unless the request explicitly asks for an approved correction.
5. Use parameterized constants from the request payload. Do not hard-code values from prior tasks.
6. Build the final object to match the answer template exactly: required keys only, correct nesting, exact enum strings, no extra commentary.
7. Write only the JSON document to `answer.json`.
Back to top