Individual skill

asteria-hub-reconcile

Solve Asteria Fleet Data Quality Hub audit and certification tasks that require reconciling contacts, fuel transactions, freight charges, or maintenance events from a running task environment into a strict JSON answer contract. Use when prompts mention the Asteria Fleet Data Quality Hub, source snapshots, contact-readiness, fuel or freight normalization, maintenance-history integrity, reference aliases, FX/unit conversions, or opaque control-code panels.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_021/fewshot/naive/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 Hub Reconcile

Use this skill to produce exact JSON answers for Asteria Fleet Data Quality Hub tasks. Always derive values from the current task payloads and hub data. Do not reuse any prior answer values.

## Inputs

1. Read the user prompt, `payloads/case_scope.json`, and `payloads/answer_template.json`.
2. Read `environment_access.md` for the base URL and allowed endpoints.
3. Inspect `/api/catalog/collections` and `/api/catalog/schema` to confirm the collection family and field names.
4. Fetch all in-scope rows, source snapshots, and relevant reference data. The REST endpoints use `collection=<collection_id>` and paginate with `offset`; each response has `items`, `limit`, `offset`, and `total`.

Use the bundled exporter when helpful:

```bash