Individual skill

asteria-hub-reconciliation

Reconcile Asteria Fleet Data Quality Hub collections and produce strict JSON audit, certification, release, or close answers. Use for Asteria contact-master or roster readiness, partner/dealer/warranty contact resolution, fuel or freight transaction normalization, maintenance-history integrity, source-snapshot retention, reference alias/conversion/fx reconciliation, and opaque Asteria control, policy, source, ledger, or maintenance code panels.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_021/fewshot/opencode/fewshot_attempt_02/SKILL.md

Read pinned source

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
Network or broad shell
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 points to the Asteria Fleet Data Quality Hub and asks for a JSON answer matching a local `payloads/answer_template.json`.

## Required Inputs

Read these before querying data:

- `prompt.txt` for the business objective and endpoint family.
- `payloads/case_scope.json` for collection IDs, cutoff/as-of times, scoped IDs, ranking limits, status gates, and ordering rules.
- `payloads/answer_template.json` for exact keys, enum values, required lengths, numeric precision, and additional-property rules.
- `environment_access.md` for the base URL, allowed endpoints, and any query credentials.

Do not rely on remembered answer values from previous tasks. Treat every count, ID list, ranking, normalized total, and code assignment as something to derive from the current hub data.