Individual skill
reflect-3_attempt_03
Not available
experiments/claude_code_glm_5_2_max/reports/skills/task_group_021/reflect-3/reflect-3_attempt_03/SKILL.md
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.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,655 bytesSKILL.mdcore · 8,655 bytesSKILL.mdcore · 8,655 bytesSKILL.mdcore · 8,655 bytesreference/alias_matching.mddoc · 2,196 bytesreference/api_query_guide.mddoc · 4,189 bytesreference/control_codes.mddoc · 2,680 bytesreference/quarantine_rules.mddoc · 2,958 bytes
Read excerpt
# Asteria Fleet Data Quality Hub — Audit & Certification Skill
## Purpose
Solve data-quality audit and certification tasks against the Asteria Fleet Data Quality Hub. Each task asks you to reconcile overlapping source records, identify data-quality issues, compute normalized metrics, assign internal control codes, and produce a certification or release decision. The answer is always a single JSON object conforming to a strict schema supplied in `payloads/answer_template.json`.
## Entry Instructions
1. **Read the task materials.** Open `payloads/case_scope.json` and `payloads/answer_template.json` from the task's input directory. The case scope gives you the collection ID, business cutoff, seed/stable IDs, decision panels, certification thresholds, and action maps. The answer template is a JSON Schema that your output must satisfy exactly.
2. **Read `environment_access.md`** for the base URL, auth token, and allowed endpoints.
3. **Discover the catalog and schema.** `GET /api/catalog/collections` lists collections by family (contacts, fuel, freight, maintenance, …) with approximate record counts and source systems. `GET /api/catalog/schema` describes every logical view (`v_contacts`, `v_fuel_transactions`, `v_freight_charges`, `v_maintenance_events`, `v_reference_aliases`, `v_source_snapshots`, `v_unit_conversions`, `v_fx_rates`) and its fields.
4. **Query all required data** using `POST /api/query` with body `{"query": "<SQL>"}`. Paginate with `LIMIT 500 OFFSET n`. Key queries per task: