Menu

Individual skill

asteria-data-quality-audit

0upvotes

Reconcile Asteria Fleet Data Quality Hub collections and produce contract-exact JSON answers for contact-master readiness, fuel and freight normalization, maintenance-log certification, source-snapshot retention, and opaque Asteria policy/control/ledger code panels. Use when a task mentions Asteria Fleet Data Quality Hub, case_scope.json, answer_template.json, source snapshots, /api/query, overlapping source records, quarantines, canonical contacts, normalized fuel/freight totals, maintenance history metrics, or Asteria compact decision codes.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_021/fewshot/fewshot_attempt_03/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 Audit

## Start

1. Read the prompt, `payloads/case_scope.json`, and `payloads/answer_template.json` before querying data.
2. Read `environment_access.md` for the base URL and query token. Use those values only; do not infer credentials.
3. Query the hub catalog and schema first:

```bash
curl -sS "$BASE/api/catalog/collections"
curl -sS "$BASE/api/catalog/schema"
curl -sS -X POST "$BASE/api/query" \
[Credential-related source omitted]
  -H "Content-Type: application/json" \