Individual skill

asteria-fleet-reconciliation

Use this skill for Asteria Fleet Data Quality Hub tasks that ask Codex to audit, reconcile, certify, normalize, or close fleet contact, fuel, freight, or maintenance collections and return a strict JSON answer from payloads/case_scope.json and payloads/answer_template.json. Use it whenever the prompt mentions Asteria, Fleet Data Quality Hub, source snapshots, aliases, unit or FX normalization, duplicate source records, compact control codes, readiness, quarantine, certification, or ledger close decisions.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_021/fewshot/opencode/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

# Asteria Fleet Reconciliation

This skill solves Asteria Fleet Data Quality Hub reconciliation tasks. Treat each task as a data audit, not a writing task: collect the full scoped data, apply the task's answer contract exactly, derive every count and code from the live records, and return only the requested JSON object.

## First Moves

1. Read the task prompt, `payloads/case_scope.json`, `payloads/answer_template.json`, and the task's `environment_access.md`.
2. Extract the collection id, cutoff or `as_of`, population scope, requested focus ids or decision panels, required top-level keys, allowed code enums, ordering rules, and numeric precision.
3. Identify the collection family from the prompt, catalog, or endpoint names:
   - contacts: partner onboarding, field service roster, dealer, warranty, or other contact master tasks
   - fuel: fuel purchases or charging transactions
   - freight: carrier invoice charges or accrual close tasks
   - maintenance: maintenance events, work orders, odometer history, or reliability history
4. Read the domain reference that applies before computing:
Back to top