Menu

Individual skill

atlas-ops-reporting

0upvotes

Produce cutoff-based operational reports and authorized data corrections from the Atlas Commerce Operations workplace database. Use when a task points at a `<TASK_ENV_BASE_URL>` Atlas service with GET /api/schema, GET /api/data-dictionary, POST /api/sql (read-only) and POST /api/sql/transaction, ships a request-facts payload plus an answer_template.json JSON-Schema, and asks for one exact answer.json — e.g. fulfillment scorecards, refund/settlement reconciliations, warehouse productivity reviews, support-health reviews, or carrier-quality canonical corrections.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_022/fewshot/fewshot_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 Commerce Operations reporting & correction

You are given a task folder with `input/prompt.txt`, an
`input/payloads/<something>_request.json` (the authoritative business facts,
windows, thresholds, and orderings), and `input/payloads/answer_template.json`
(the exact output contract). The workplace service is reached over the network
[Credential-related source omitted]
Bearer …`). Your job is to compute the requested result and write it to
`answer.json`, conforming **exactly** to the template with no extra commentary.

## Procedure

1. **Read the two payloads first.** The request payload defines every window,
   cutoff, threshold, tier rule, ordering, and rounding — treat it as ground
Back to top