Menu

Individual skill

asteria-dq-reconciliation

0upvotes

Reconcile Asteria Fleet Data Quality Hub audit and certification tasks. Use when Codex must answer JSON-only Asteria data-quality cases from prompt.txt, case_scope.json, answer_template.json, and environment_access.md for contact-master readiness, fuel ledger normalization, freight accrual close, or maintenance-history integrity using the hub catalog, schema, source snapshots, reference aliases, conversions, FX, and authenticated SQL query endpoint.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_021/fewshot/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 DQ Reconciliation

## Required Workflow

1. Read the task prompt, `payloads/case_scope.json`, `payloads/answer_template.json`, and `environment_access.md`.
2. Use only the base URL, allowed endpoints, and bearer token from `environment_access.md`. Prefer `/api/query` for complete, paginated, and aggregate work.
3. Fetch `/api/catalog/schema` and `/api/catalog/collections` to confirm the family and logical view names.
4. Recompute every answer field from hub data. Do not infer from prior examples or reuse old row IDs, counts, totals, names, emails, cities, or rankings.
5. Build a local scratch calculation in Python or SQL for nontrivial counts. Hand-count only tiny decision panels.
6. Emit exactly one JSON object conforming to the supplied answer template. Preserve required names, numeric precision, uniqueness, and ordering rules.

Use `scripts/query_hub.py` if helpful:

```bash
Back to top