Menu

Individual skill

asteria-data-quality-reconciliation

0upvotes

Reconcile Asteria Fleet Data Quality Hub audit tasks that use environment_access.md, payloads/case_scope.json, and payloads/answer_template.json. Use for contact survivorship/readiness, fuel or freight ledger cleanup, maintenance history integrity, source-snapshot retention, alias/reference policy decisions, unit/FX normalization, quarantine/exception reporting, compact control-code panels, and strict JSON-only answer contracts.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_021/self/self_attempt_02/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 Reconciliation

## Start Every Case

1. Read `environment_access.md`, `payloads/case_scope.json`, and `payloads/answer_template.json`.
2. Use only the hub endpoints listed in `environment_access.md`. Prefer authenticated `POST /api/query` for complete data; REST endpoints may be page-limited.
3. Query `v_source_snapshots`, the relevant domain view, `v_reference_aliases`, `v_unit_conversions`, and `v_fx_rates` as needed. Check `truncated`; if true, page explicitly with `limit`/`offset` or narrower queries.
4. Fill exactly the answer template: no extra keys, exact required names, numeric precision, sorted arrays, and JSON only.

Useful query pattern:

```bash
curl -sS -X POST "$GDPEVO_ENV_BASE_URL/api/query" \
[Credential-related source omitted]
Back to top