Individual skill

atlas-commerce-ops

Solve Atlas Commerce Operations analytical and controlled-correction tasks against authenticated workplace APIs. Use when prompts require strict answer.json outputs from the Atlas database, schema and data-dictionary discovery, read-only SQL analysis, fulfillment, refunds, warehouse, support, carrier, inventory, or approved minimal canonical corrections with correction_audit verification.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_022/fewshot/deepagents/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
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
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

SKILL.mdcore · 4,259 bytes
SKILL.mdcore · 4,259 bytes
SKILL.mdcore · 4,259 bytes
SKILL.mdcore · 4,259 bytes
SKILL.mdcore · 4,259 bytes
references/atlas_sql_patterns.mddoc · 8,921 bytes
scripts/atlas_api.pyruns · 3,673 bytes

Read excerpt


# Atlas Commerce Ops

## Operating Rules

- Read the user prompt, every file under `input/payloads/`, and especially `answer_template.json` before querying.
- Treat the payload request as the business contract. Use the schema and data dictionary only to map those definitions to tables and columns.
- Derive every answer value from the current task database. Do not reuse IDs, counts, rates, audit records, or final values from prior examples.
- Use read-only SQL for analytical tasks. Use the transaction endpoint only when the request explicitly approves a workplace correction.
- Preserve raw source fields, source identity fields, and unrelated rows. For correction tasks, update only the approved canonical field and append exactly the required audit row.
- Write only the final JSON object to `answer.json`; include no narrative in the file.

## API Setup

Fetch schema and dictionary at the start of each task, because the prompt can depend on exact field wording: