Menu

Individual skill

atlas-ops-analytical-scorecard

0upvotes

Use when a task delivers a business "scorecard", "reconciliation", "review", "backlog", or "correction" as three files — a prompt, a request-policy JSON (scope, business definitions, rollups, tie-breaks, rounding, status rules), and an answer_template.json — to be computed against an authenticated, read-only SQL workplace/operations database and written as one JSON object to answer.json. Covers eligibility cohorts, "effective/canonical" entity reduction, exact UTC windows, rate/rounding rules, worst/top-N ordering with tie-breaks, ordered status-rule cascades, and single-row canonical corrections with an audit record.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_022/reflect-3/reflect-3_attempt_01/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

# Operations analytical scorecard & correction tasks

These tasks share one shape: a natural-language prompt points at a **request
payload JSON** (the authoritative policy) and an **answer_template.json** (the
exact output contract), and asks you to compute production results from an
authenticated operations database and write one JSON object to `answer.json`.
They are read-only **analytical** tasks unless the request explicitly asks you
to *apply a correction*. Your answer is graded on exact values and exact
conformance, so precision on definitions, boundaries, rounding, and ordering is
everything.

The environment (base URL, auth, and the available endpoints — schema,
data-dictionary, read-only SQL, and, for correction tasks, a transactional SQL
and correction-audit view) is described in the run's own access file. Read that
Back to top