Menu

Individual skill

asteria-hub-reconciliation

0upvotes

Use this skill for Asteria Fleet Data Quality Hub audit tasks that ask Codex to reconcile contacts, fuel transactions, freight charges, or maintenance events from task payloads, environment_access.md, and a JSON answer template. It guides schema-first hub extraction, snapshot selection, deduplication, quarantine handling, unit and FX normalization, contact readiness, maintenance history validation, ranking panels, and compact Asteria control-code decisions.

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

Use this skill when a task asks for one JSON answer from the Asteria Fleet Data Quality Hub. The task will usually provide `payloads/case_scope.json`, `payloads/answer_template.json`, and `environment_access.md`.

## Ground Rules

- Read the prompt, `case_scope.json`, `answer_template.json`, and `environment_access.md` before querying the hub.
- Treat the answer template as the output contract. If it is JSON Schema, obey required keys, types, enums, precision, uniqueness, and ordering descriptions. If it is a prose field contract, treat its field descriptions as binding.
- Use only the collection, cutoff, business period, focus IDs, ranking limits, and code panels named by the task scope.
- Return exactly one JSON object. Do not include markdown, comments, or extra keys.
- Do not guess counts from samples. Fetch every page or use a complete query result.

## Fetching Data
Back to top