Menu

Individual skill

reflect-3_attempt_02

0upvotes

Not available

experiments/claude_code_deepseek_v4_pro_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.

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.

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
Read excerpt
# Asteria Fleet Data Quality Hub — Audit & Certification Skill

## Overview

Use this skill to process Asteria Fleet data-quality audit and certification tasks. Every task reconciles overlapping source records from a shared read-only data hub, detects data-quality issues, normalises values against reference tables, assigns internal control codes, and returns a single JSON object conforming to a supplied answer contract.

## Step 1 — Discover the collection and its schema

Read the task's `case_scope.json` for the `collection_id` and business cutoff or as-of date. Read `environment_access.md` for the base URL, authorization header, and the list of allowed endpoints.

**Catalog.** Call `GET /api/catalog/collections` to confirm the collection exists and to learn its source systems, approximate row count, and time range.

**Schema.** Call `GET /api/catalog/schema` to list every available logical view and its fields. Match the task domain — contacts, fuel transactions, freight charges, maintenance events — to the correct view (`v_contacts`, `v_fuel_transactions`, `v_freight_charges`, `v_maintenance_events`, `v_reference_aliases`, `v_unit_conversions`, `v_fx_rates`, `v_source_snapshots`). Study the `meaning` annotations on each field; they describe the business purpose and expose aliases (e.g., `purchased_description` in fuel is the text you match against reference aliases).

## Step 2 — Load source-snapshot metadata
Back to top