gaia-tm-inspect

Audit and repair Gaia user-tree timelines so every skill's current rank is explained by a chain of Hero's Journey events. Trigger this skill when: a contributor's profile chart shows a stale rank (e.g. still shows 3★ after a demotion to 1★); someone asks to "trace what happened" to a skill's rank; `validate_timelines.py` is failing in CI; you need to backfill missing `demote` or `rank_up` events before cutting a release; a skill was reclassified or Star-Bar-reset and the user tree was never updated; or any time the registry node and user tree disagree on a skill's current level. Uses `scripts/trace_timeline.py` (dry-run + apply) and `scripts/validate_timelines.py` (CI gate). Do NOT hand-edit `timeline[]` arrays — the script synthesises properly labelled events with `previousValue`/`newValue` so the rank chart plots correctly.

Maintain registered routine pull requests through independent verification, bounded shared preparation and an explicit one-shot executor. Use for routine 19, weekly report PRs, or forge.merge_pr/forge.close_pr proposals. Never a general merge permission; missing deployment configuration refuses execution.

Produce the Gaia Steward coverage retrospective: the routine table of registered detectors, what each actually observed in the latest receipt, the remaining gaps, and the no-op versus closure record. Covers all 19 routines, including GitHub issue hygiene (18) and routine pull-request maintenance (19). Use for "/gaia-steward-full --retro", "steward coverage report", "which routines are covered", or "how is steward doing".

Sort open Gaia Steward debt into Class A (deterministic repair), Class B (bounded dispatch) and Class C (founder decision) with priorities, optionally narrowed to one routine or one debt id, without acting on any of it. Use for "/gaia-steward-full --triage", "--routine N", "--debt ID", "what should Steward do next", or "triage Steward debt". This is not issue or intake triage (gaia-triage).

Independently verify one Gaia Steward Class B build: read only the rendered verifier prompt and the sensor evidence, check the diff and proof, and record accept, reject or escalate. Use when a full Steward run emits an agent.verify action, for "/gaia-steward-full --verify", or "verify the steward dispatch". The verifier must be a different agent from the builder.

Comprehensive, reusable playbook for multi-component suite intake under Yggdrasil III. Audits component installability, maps origin candidates to generic capabilities, ingests named components with shared-repo baseline caps, manifests suites via gaia dev fuse, calibrates capstone and component ranks, and closes out via Class S regeneration.

This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.

A relentless interview to sharpen a plan or design.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Teach the user a new skill or concept, within this workspace.

No description in the SKILL.md.

No description in the SKILL.md.

Ask which skill or flow fits your situation. A router over the skills in this repo.

No description in the SKILL.md.

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.