Individual skill
atlas-commerce-ops
Use this skill for Atlas Commerce Operations workplace tasks that ask for strict JSON answers from an authenticated TASK_ENV_BASE_URL service, /api/schema, /api/data-dictionary, /api/sql, or /api/sql/transaction. It is especially relevant for cutoff-based fulfillment, refund, carrier quality, warehouse productivity, inventory, payments, support-health, and controlled correction tasks that require SQL over the Atlas Commerce Operations database and saving answer.json.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_022/fewshot/cc/fewshot_attempt_01/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
SKILL.mdcore · 5,910 bytesSKILL.mdcore · 5,910 bytesSKILL.mdcore · 5,910 bytesSKILL.mdcore · 5,910 bytesSKILL.mdcore · 5,910 bytesSKILL.mdcore · 5,910 bytesSKILL.mdcore · 5,910 bytesSKILL.mdcore · 5,910 bytesreferences/atlas_sql_patterns.mddoc · 7,991 bytesscripts/atlas_api.pyruns · 4,459 bytesscripts/check_answer.pyruns · 5,705 bytes
Read excerpt
# Atlas Commerce Operations
Use this skill to solve Atlas Commerce Operations database tasks end to end: read the request payload and answer template, query the authenticated workplace API, compute the requested metrics with cutoff-consistent SQL, optionally apply an explicitly approved canonical correction, and write only `answer.json`.
## Required Workflow
1. Read the task prompt, the business request JSON under `input/payloads/`, and `input/payloads/answer_template.json` before querying.
2. Resolve the workplace connection from the prompt or the task environment. If the prompt shows `<TASK_ENV_BASE_URL>`, use `TASK_ENV_BASE_URL`, `ATLAS_BASE_URL`, or an `environment_access.md` file when one is present in the task workspace. Use the bearer token from the named token env var, usually `TASK_ENV_API_TOKEN`.
3. Fetch fresh schema and data dictionary from the service. Do not assume the schema from memory; the service is the authority for the current task.
4. Convert the business request into named CTEs that mirror the request language: cohort, effective source rows, cutoff state, rollups, rankings, status/risk classification, and final projection.
5. Use read-only `POST /api/sql` for analysis. Use `POST /api/sql/transaction` only when the request explicitly authorizes a correction and defines the approved mutation and audit requirements.
6. Validate the final JSON against the answer template, including exact keys, no extra fields, array lengths, ordering, enum values, numeric precision, and ID sorting. Save only the JSON document to `answer.json`.
Useful bundled files: