Menu

Individual skill

atlas-commerce-operations

0upvotes

Use when solving Atlas Commerce Operations workplace tasks that provide a prompt, request payload JSON, and answer_template.json, and require authenticated schema/data-dictionary/SQL API use to produce exact answer.json metrics, reconciliations, support/warehouse/fulfillment scorecards, or approved canonical corrections with correction_audit records.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_022/fewshot/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

## Required Workflow

1. Read the task prompt and every file under `input/payloads/` before querying data.
2. Treat `answer_template.json` as the output contract: preserve required keys, value types, array ordering rules, rounding precision, enum policies, and `additionalProperties: false`.
3. Read `environment_access.md` for the base URL, token, and allowed endpoints. Fetch `/api/schema` and `/api/data-dictionary` at the start of each task; table availability and field meanings are part of the runtime contract.
4. Use `POST /api/sql` for read-only analysis. Use `POST /api/sql/transaction` only when the prompt explicitly requests an approved correction.
5. Compute from the database each time. Do not reuse answer values from examples or prior runs.
6. Write only the final JSON object to `answer.json`; include no markdown, explanation, comments, or extra fields.

Useful API pattern:

```bash
Back to top