Individual skill
asteria-quality-reconciliation
Reconcile Asteria Fleet Data Quality Hub tasks for contacts, fuel, freight, and maintenance audits. Use when a task provides a case scope, answer contract, source snapshots, operational records, reference aliases/conversions/FX, and asks for canonical entities, duplicate retention, quarantine/exception counts, normalized totals, ranking panels, compact control codes, or release/certification decisions.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_021/reflect-3/reflect-3_attempt_01/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- legal Derived category
- data Derived category
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 Quality Reconciliation
## Required Workflow
1. Read the prompt, case scope, answer contract, and environment access supplied with the task.
2. Inspect the catalog/schema before querying records. Identify the collection family (`contacts`, `fuel`, `freight`, or `maintenance`), business cutoff/as-of time, requested focus IDs, output precision, and ordering rules.
3. Pull all in-scope source rows for the scoped collection. Keep raw rows for raw counts, then build a retained logical record set for calculations.
4. Use source snapshot metadata to identify the authoritative basis. Prefer certified/authoritative rows when overlapping logical records exist; otherwise retain the latest available row by business update and ingestion time. Report duplicate groups from all overlapping raw occurrences, not only the retained row.
5. Build the answer directly from the answer contract. Preserve exact key names, enum values, list lengths, sort orders, uniqueness rules, and numeric precision.
## Ledger Audits
Use this for fuel-purchase and freight-charge collections.
