Menu

Individual skill

asteria-fleet-audit

0upvotes

Audit Asteria Fleet Data Quality Hub tasks and produce strict JSON reconciliation answers for fleet contacts, field rosters, fuel or freight transactions, source snapshots, maintenance history, duplicate resolution, quarantine, mismatch reporting, normalized totals, rankings, certification gates, and opaque control-code panels. Use when a prompt references Asteria Fleet, TASK_ENV_BASE_URL, case_scope.json, answer_template.json, source snapshots, or the Hub query API.

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

Use this skill to solve Asteria Fleet Data Quality Hub reconciliation tasks. The common failure mode is treating these as simple extraction tasks. Instead, reconstruct the authoritative business view from the Hub as of the scoped cutoff, compute every requested set and aggregate, then emit only the JSON object required by the answer contract.

## Inputs

Read these files before querying:

1. The task prompt.
2. `payloads/case_scope.json`.
3. `payloads/answer_template.json`.
4. `environment_access.md`, only for the base URL, credentials, and access rules needed to reach the running Hub.

Use the task's current payloads and Hub data as the only source of final values. Do not reuse IDs, counts, names, metrics, or final records from prior examples.
Back to top