Individual skill
atlas-commerce-ops-solver
Solve Atlas Commerce Operations database tasks that provide prompt.txt, request payloads, answer_template.json, and authenticated TASK_ENV_BASE_URL API endpoints. Use for fulfillment, refund, carrier quality, warehouse productivity, support health, inventory, order, payment, customer, SQL analysis, and controlled canonical-correction tasks that must write an exact answer.json.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_022/fewshot/codex/fewshot_attempt_03/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 · 3,483 bytesSKILL.mdcore · 3,483 bytesSKILL.mdcore · 3,483 bytesSKILL.mdcore · 3,483 bytesSKILL.mdcore · 3,483 bytesSKILL.mdcore · 3,483 bytesSKILL.mdcore · 3,483 bytesSKILL.mdcore · 3,483 bytesSKILL.mdcore · 3,483 bytesagents/openai.yamlasset · 221 bytesreferences/atlas-patterns.mddoc · 6,648 bytesscripts/atlas_api.pyruns · 5,120 bytesscripts/validate_answer.pyruns · 5,500 bytes
Read excerpt
# Atlas Commerce Ops Solver
## Core Workflow
1. Read the task prompt, every file under `input/payloads/`, and especially `answer_template.json`. Treat the request payload and template as the contract; do not add narrative or extra fields to `answer.json`.
2. Fetch live Atlas metadata before writing analysis SQL:
```bash
python skill/scripts/atlas_api.py schema
python skill/scripts/atlas_api.py dictionary
```
3. Use [references/atlas-patterns.md](references/atlas-patterns.md) when designing the SQL plan. Build the solution in auditable CTEs: cohort, effective rows or state at cutoff, metric rows, ordered output arrays, risk/status classification.
4. Query through the read-only endpoint unless the request explicitly requires an approved correction: