Individual skill
asteria-hub-quality-audits
Solve Asteria Fleet Data Quality Hub reconciliation and certification tasks that provide case_scope.json, answer_template.json, and environment_access.md. Use for contact-master/readiness, fuel or freight normalization, maintenance-history integrity, source-snapshot reconciliation, quarantine/mismatch reporting, decision-code panels, rollups, rankings, and strict JSON-only answers.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_021/fewshot/naive/fewshot_attempt_02/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- data Derived category
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 Quality Audits
Use this skill when a task asks for an Asteria Fleet Data Quality Hub audit or certification answer. The task will supply a prompt, `payloads/case_scope.json`, `payloads/answer_template.json`, and `environment_access.md`.
## Core Workflow
1. Read the prompt, `case_scope.json`, and the full `answer_template.json` before querying data.
2. Treat `answer_template.json` as the output contract. Preserve required keys, exact enum values, array lengths, uniqueness, numeric precision, and ordering rules from schema descriptions.
3. Read `environment_access.md` for the base URL, credentials, and allowed endpoints. Never call a judge endpoint.
4. Query `catalog/collections` and `catalog/schema` first to identify the collection family, logical view names, field meanings, and source systems.
5. Pull all in-scope rows. Collections can exceed one response page; page until the returned total is exhausted. If `/api/query` is available, use the logical views directly and filter by `collection_id`, cutoff/as-of time, and business period from `case_scope.json`.
6. Reconcile overlapping snapshots before computing metrics. Pick the authoritative in-scope snapshot by status and cutoff evidence, with `CERTIFIED` preferred over `PROVISIONAL`, and retain that snapshot's occurrence for duplicate logical IDs when present. Report duplicate groups from the full raw in-scope row set.
7. Compute every answer field from reconciled rows, reference tables, unit conversions, and FX rates. Do not estimate from row IDs or generator patterns when data can be queried.
8. Fill scoped panels exactly for IDs listed in `case_scope.json`; sort panels and ID lists by the contract, usually lexicographic or ascending stable ID.