Individual skill

asteria-fleet-dq-audit

Solve Asteria Fleet Data Quality Hub reconciliation, normalization, and certification tasks. Use for prompts mentioning the Asteria Fleet Data Quality Hub, source snapshots, authoritative snapshots, duplicate logical records, contact readiness, fuel or freight transaction audits, maintenance history integrity, quarantine rows, compact internal control codes, or strict JSON answer contracts.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_021/fewshot/cc/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 11, 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 Fleet Data Quality Hub Audits

Use this skill to produce the single JSON answer required by an Asteria Fleet Data Quality Hub task. The examples behind this skill are data-quality audits over live hub records; do not solve from memory or from the payload names alone.

## Required Inputs

Read these files from the task workspace before querying the hub:

- `prompt.txt`: identify the business domain, relevant endpoints, cutoff/as-of date, and any special inclusion rules.
- `payloads/case_scope.json`: authoritative scope, focus IDs, decision panels, ranking limits, thresholds, and ordering rules.
- `payloads/answer_template.json`: exact output shape. It may be JSON Schema or a custom contract with `field_contract`.
- `environment_access.md`: base URL, credentials, and allowed endpoint list for the running hub.

Return only one JSON object. Do not include Markdown, commentary, or extra keys.
Back to top