memory-snapshot

Use this skill when the user wants to understand why a named Gaia skill has a particular star rank, what its Trust Magnitude (TM) score is, which evidence rows are contributing (or dead), how far it is from the next grade, or what evidence to add to move the needle. Also use when asked for a full leaderboard of all named skills ranked by TM. Triggers: "why does X have 3 stars", "what's the TM for X", "inspect TM", "explain the score for X", "what evidence would rank up X", "show leaderboard", "rank all skills by TM", "what's dragging down X's score", "dead evidence rows", "how close is X to grade A/S".

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.

Triage the Gaia issue backlog and skill-batch intake queue. Use this skill when someone asks to: "triage issues", "clean up the issue tracker", "review the backlog", "close stale issues", "process the intake queue", "review skill-batches", "evaluate draft skill proposals", "approve or reject pending skills", "is this issue still valid?", "what's clogging the backlog?", "run a triage pass", or /gaia-triage. Covers two workstreams: (1) GitHub issue lifecycle — identifying resolved, stale, or need-more-info issues and acting on them via gh CLI; (2) skill-batch intake — evaluating draft proposals in registry-for-review/skill-batches/ and routing them toward promotion or rejection. This is the gatekeeping step before new skills enter the canonical registry; and (3) a cross-repo triage sweep — sizing, P0-P4 prioritization, umbrella/epic synthesis, and assignment across every gaia-research org repo, on the one headquarters tracker.

Use this skill when the user wants to turn code graph analysis into tracked GitHub issues — "audit the architecture", "find god nodes", "triage architectural debt", "run graphify and log issues", "what's over-coupled in this codebase", "create issues from graphify findings", "check for structural problems", "scan for architectural smells", or any request that combines codebase topology analysis with issue tracking. This skill runs graphify to build a dependency graph, parses GRAPH_REPORT.md for god nodes and structural patterns, converts findings into GitHub issue payloads, and optionally pushes them to the repo. It bridges static analysis and project management in a single automated pass. Requires graphify and gh CLI.

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.