Individual skill
atlas-commerce-ops
Solve Atlas Commerce Operations workplace tasks that require authenticated schema/data-dictionary discovery, SQL analysis, strict JSON answers, and controlled canonical data corrections with audit records. Use when a prompt references an Atlas/GDPEVO workplace service, TASK_ENV_BASE_URL or GDPEVO_ENV_BASE_URL, /api/schema, /api/sql, /api/sql/transaction, answer_template.json, fulfillment, refunds, carrier quality, warehouse productivity, support health, or correction-audit workflows.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_022/fewshot/fewshot_attempt_02/SKILL.md
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
- security 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,938 bytesSKILL.mdcore · 5,938 bytesSKILL.mdcore · 5,938 bytesSKILL.mdcore · 5,938 bytesSKILL.mdcore · 5,938 bytesSKILL.mdcore · 5,938 bytesSKILL.mdcore · 5,938 bytesSKILL.mdcore · 5,938 bytesscripts/atlas_api.pyruns · 4,756 bytesscripts/validate_answer.pyruns · 5,092 bytes
Read excerpt
# Atlas Commerce Ops
## Core Workflow
1. Read the prompt, every request payload, and the answer template before querying data.
2. Read the provided environment access file or user-provided connection details. Do not infer credentials from placeholders.
3. Query `/api/schema` and `/api/data-dictionary` fresh for the current environment. Treat the live metadata as authoritative.
4. Translate the request into exact cohorts, cutoff logic, status rules, rounding rules, and output ordering before writing SQL.
5. Use `POST /api/sql` only for `SELECT` or `WITH` analysis queries. Use `POST /api/sql/transaction` only when the request explicitly asks for a controlled correction.
6. Build results from the live database every time. Do not reuse example counts, IDs, statuses, or answer values.
7. Validate the final JSON against the supplied answer template and write only the JSON object requested by the user.
## API Helpers
