Individual skill

asteria-fleet-dq-reconciliation

Solve an Asteria "Fleet Data Quality Hub" reconciliation task. Use when a task gives you payloads/case_scope.json plus payloads/answer_template.json and asks you to reconcile overlapping source records from a read-only data hub (catalog, schema, SQL query, source-snapshot, contact/transaction/maintenance, and reference alias/conversion/fx interfaces) and return exactly one JSON object. Covers three task families: contact-master reconciliation, transaction normalization (fuel/freight), and maintenance-log integrity.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_021/reflect-3/reflect-3_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

# Asteria Fleet Data Quality Hub — reconciliation tasks

## What these tasks look like
Each task ships two payloads and points at a shared read-only data hub:

- `payloads/case_scope.json` — the scope: `collection_id`, a business cutoff /
  as-of, the focus/anchor/decision IDs you must report on, and (sometimes)
  status thresholds or a certification gate + status→action map.
- `payloads/answer_template.json` — the answer contract: exact keys, enums,
  array lengths, ordering rules, and numeric precision. **This file is the
  spec. Read every field description, `enum`, `pattern`, `minItems/maxItems`,
  `multipleOf`, and ordering note before writing any code.**

Connection details (base URL and a read-only bearer token) are provided
Back to top