Menu

Individual skill

asteria-fleet-data-quality

0upvotes

Reconcile multi-source fleet data through the Asteria Data Quality Hub, resolve duplicate entities, assign quality and control codes, apply certification thresholds, and produce structured answer objects for partner contacts, fuel purchases, maintenance events, field service rosters, and freight charges.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_021/fewshot/naive/fewshot_attempt_03/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

This skill covers data reconciliation tasks against the Asteria Fleet Data Quality Hub, a read-only REST API for cross-source fleet business data. The hub surfaces overlapping record snapshots from multiple operational systems and requires you to resolve canonical entities, detect quality issues, assign internal control and policy codes, and produce structured certification decisions.

## Hub Connection

The hub is always at the base URL supplied in `environment_access.md`. All endpoints return JSON.

**Always start by reading `environment_access.md`** for the base URL, any query authentication token, and the list of allowed endpoints for the current task.

Standard endpoints (availability varies by task; only use those listed in `environment_access.md`):

| Method | Path | Purpose |
|--------|------|---------|
| GET | `/health` | Connectivity check |
| GET | `/api/catalog/collections` | List available data collections |
Back to top