Individual skill

atlas-ops-request-analysis

Analyze Atlas Commerce Operations workplace requests and produce exact JSON answers from prompt, request payload, schema, data dictionary, SQL query endpoints, and optional controlled correction endpoints. Use when a task asks Codex to compute operational scorecards, reconciliations, SLA/health reviews, cutoff-based state, ranked exceptions, or apply an approved minimal canonical data correction with audit evidence against the Atlas workplace service.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_022/self/self_attempt_03/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 Request Analysis

Use this skill for Atlas Commerce Operations tasks that provide a prompt, one or more request payloads, an answer template, and an authenticated workplace service. Produce the requested `answer.json` exactly; include no narrative in the answer file.

## Required Inputs

1. Read the task prompt first.
2. Read every file under `input/payloads/`, including the business request payload and `answer_template.json`.
3. Read `environment_access.md` only to obtain the allowed base URL, endpoints, headers, and transaction limits.
4. Treat all request timestamps as exact UTC business cutoffs or windows. Do not substitute the current date.
5. Use the answer template as the output contract, even when it uses nonstandard schema spellings such as `additional_properties`, `min_items`, or `decimal_places`.

## Service Access