Menu

Individual skill

asteria-data-quality-audits

0upvotes

Reconcile Asteria Fleet Data Quality Hub collections and produce exact JSON audit/certification answers from prompts that provide a case_scope.json, answer_template.json, environment_access.md, and Asteria hub endpoints. Use for contact-master/onboarding/roster readiness, fuel ledger normalization, freight accrual cleanup, and maintenance-history integrity tasks requiring source snapshot selection, duplicate retention, quarantine decisions, normalized totals, ranking panels, and compact Asteria control codes.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_021/self/self_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 Data Quality Audits

Use this skill to solve Asteria Fleet Data Quality Hub audit tasks. Return exactly the requested JSON contract; do not add commentary when the prompt says JSON only.

## Inputs

1. Read the user prompt, `payloads/case_scope.json`, `payloads/answer_template.json`, and `environment_access.md`.
2. Treat the answer template as the output authority: required keys, allowed enum values, sort order, lengths, uniqueness, and precision come from the template even when the prompt is brief.
3. Use only the hub base URL and endpoints/credential in `environment_access.md`. Do not use external sources.
4. Inspect `/api/catalog/collections`, `/api/catalog/schema`, and `v_source_snapshots` before querying facts for the scoped collection.

The authenticated query interface accepts JSON like:

```bash
Back to top