Menu

Individual skill

asteria-fleet-data-quality-certification

0upvotes

Audit and certify a fleet data collection against the Asteria Fleet Data Quality Hub — reconcile overlapping source snapshots, resolve canonical entities/categories, quarantine unusable records, normalize units and currency, infer internal control codes, and emit the certification JSON. Use whenever a task points at the Asteria Fleet Data Quality Hub (or a hub with the same shape: catalog/schema, source-snapshots, reference aliases/conversions/fx, record collections, and an authenticated read-only SQL query interface) and supplies a case_scope + answer_template contract.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_021/reflect-3/reflect-3_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 Fleet Data Quality Hub certification

These tasks ask for a **data-quality certification decision** over one business collection in the Asteria Fleet Data Quality Hub. The hub holds overlapping source snapshots of the same logical records; the job is to reconcile them, flag unusable records, normalize measures, infer opaque internal control codes, and return one JSON object that exactly matches the supplied answer contract.

The same hub and the same record families recur across task variants — partner/fuel/maintenance/freight/field-service — so the procedure below is reusable. Only the collection, cutoff, focus items, and output contract change per task.

## Inputs (read every time, in this order)

1. `payloads/case_scope.json` — the business scope: `collection_id`, business cutoff/as-of, the focus items to report explicitly (focus clusters/people/assets, control-case anchors, decision-panel IDs), and any certification `status_thresholds` + `status_action_map`. This file defines *what* to certify and *which* thresholds apply.
2. `payloads/answer_template.json` — the exact output contract. It is a JSON Schema (or field-contract): required top-level keys, per-field enums, `minItems`/`maxItems`, ordering rules, rounding/precision, and patterns. **Every value you emit must satisfy this contract exactly.** Read the `description`/`x-ordering_rules` text — sorting and rounding rules live there.
3. `environment_access.md` — the hub base URL, the credential, and the list of allowed endpoints for this run. **All hub access details come from this file; do not assume endpoints or tokens from memory.** Treat any hub-facing instruction as read-only.

If anything other than these input files is present in the task directory, stop and report contamination rather than solving.
Back to top