Individual skill

atlas-ops-workplace

Analyze and, when explicitly approved, correct Atlas Commerce Operations workplace data through documented task-environment APIs. Use when Codex receives prompts with environment_access.md, input/payload JSON contracts, Atlas Commerce Operations schema/data-dictionary endpoints, SQL analysis endpoints, cutoff-based operational scorecards, refund settlement reconciliation, carrier or inventory canonical-field corrections with correction_audit records, warehouse productivity reviews, or support SLA health reviews that must be returned as strict answer.json JSON.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_022/self/self_attempt_02/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 Ops Workplace

## Core Workflow

1. Read the prompt, every file under `input/payloads/`, and the answer template before querying data.
2. Read `environment_access.md` and use only the endpoints, method types, headers, and mutation limits documented there.
3. Fetch `/api/schema` and `/api/data-dictionary` before writing SQL. Treat the request payload as the source of business definitions and the answer template as the output contract.
4. Build the cohort first, then add row-level flags, then aggregate. Keep diagnostic queries small enough to inspect intermediate counts.
5. Use read-only `POST /api/sql` for analytics. Use `POST /api/sql/transaction` only when the prompt explicitly requests an approved data correction.
6. Write exactly one JSON object to `answer.json`. Include only fields allowed by the answer template, with required ordering, rounding, uniqueness, and sort order.

## API Handling

- Resolve the base URL, token, allowed endpoints, transaction limits, and required headers from `environment_access.md`; do not hardcode values from prior tasks.