Menu

Individual skill

asteria-hub-reconciliation

0upvotes

Reconcile Asteria Fleet Data Quality Hub audit and certification tasks and return schema-valid JSON. Use when a task provides TASK_ENV_BASE_URL plus environment_access.md, payloads/case_scope.json, and payloads/answer_template.json for contact or roster readiness, fuel or freight transaction normalization, maintenance history integrity, source snapshots, aliases, conversions, FX, duplicate records, quarantines, rankings, status decisions, or opaque Asteria control-code panels.

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

# Asteria Hub Reconciliation

## Required Workflow

1. Read the task prompt, `payloads/case_scope.json`, `payloads/answer_template.json`, and `environment_access.md`. Use `environment_access.md` only for the base URL, credentials, and query-interface details needed to access the running hub.
2. Read the hub catalog, schema, source snapshots, and the domain records named by the prompt. Use `/api/query` when endpoint pages are large, when joins are needed, or when source rows must be filtered by collection and cutoff.
3. Build a local working table with every in-scope raw row. Keep public stable IDs, source system, snapshot ID, business time, update time, status, aliases, units, currency, and all evidence fields needed for the answer contract.
4. Select the authoritative snapshot as of the business cutoff, then collapse overlapping rows by their logical business ID or identity cluster. Retain the authoritative/certified occurrence when duplicates cross snapshots, and report all duplicate groups required by the contract.
5. Apply the domain rules in [references/reconciliation_playbook.md](references/reconciliation_playbook.md). Compute all counts from the retained logical records, excluding quarantined records only where the prompt says normalized totals must exclude them.
6. Fill every scoped focus, ranking, watchlist, and decision-panel entry from live hub evidence. Do not reuse example IDs, counts, names, or answer rows from prior tasks.
7. Emit exactly one JSON object matching the supplied answer contract. Sort arrays and round numbers exactly as the contract or case scope requires. Run `scripts/contract_lint.py` as a final shape check when possible.

## Helper Scripts
Back to top