Individual skill
asteria-fleet-data-quality
Reconcile Asteria Fleet Data Quality Hub collections and produce strict JSON audit or certification answers for contact readiness/contact mastering, fuel purchases, freight charges, and maintenance history. Use when a task mentions Asteria Fleet Data Quality Hub, source snapshots, answer_template.json, case_scope.json, contact control codes, fuel/freight normalization, maintenance integrity, or internal decision-code panels.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_021/fewshot/deepagents/fewshot_attempt_01/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
- security 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 Fleet Data Quality
## Workflow
1. Read the task prompt, `payloads/case_scope.json`, and `payloads/answer_template.json`. Treat the template as the output contract: required keys, exact names, enum values, precision, and ordering rules override intuition.
2. Read runtime access details from `environment_access.md`. Use only the listed endpoints. Do not invent data or use prior task answers.
3. Fetch the catalog, schema, source snapshots, and all rows for the scoped `collection_id`. The REST endpoints use `collection` for collection filters, `domain` for aliases, `kind` for unit conversions, and `currency` for FX. They page with `limit` and `offset`.
4. Prefer row-level calculations over shortcut inference. Reconcile duplicates, classify exceptions, compute totals, then fill the decision-code panels from the same evidence.
5. Return only the final JSON object. Before finalizing, check every array is sorted as specified, every count is internally consistent, and every rounded number uses the contract precision.
Use `scripts/fetch_hub_bundle.py` to collect a complete local JSON bundle for a scoped collection:
```bash
python skill/scripts/fetch_hub_bundle.py \