Menu

Individual skill

atlas-operations-analyst

0upvotes

Analyze Atlas Commerce Operations data using a read-only SQL API with schema discovery, compute business metrics from query results, apply domain rules (rates, rankings, severity classification, currency conversion, SLA breaches), perform controlled data corrections through SQL transactions, and write output conforming exactly to a provided JSON answer template.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_022/fewshot/naive/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

This skill covers analytical tasks against the Atlas Commerce Operations database. The solver reads a business request and supporting payloads, discovers the database schema, writes SQL, computes results client-side using the stated business rules, and writes a strict-format JSON answer.

## Environment

Every task provides a base URL in a placeholder like `<TASK_ENV_BASE_URL>` or a literal URL such as `http://task-env:9022/`. Use that value throughout. The authentication is already wired:

[Credential-related source omitted]
- Header `Content-Type: application/json`

Validate connectivity with `GET /health` once at the start.

## API Endpoints

| Method | Path                     | Purpose                                      |
Back to top