vault-groom
Audit and clean up knowledge base state — archive completed work, fix inconsistencies
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Audit and clean up knowledge base state — archive completed work, fix inconsistencies
Process a meeting transcript — extract decisions, action items, and key discussion points into structured vault entries
Generate a pre-meeting agenda with context gathered from the knowledge base
Capture a stream idea or guest profile for content planning
Process a work brain-dump and sync progress across the knowledge base
Turn code, issues, or context into a handoff brief for another LLM — full context, zero prescribed solution, written to docs/prompts/. Use when packaging a bug fix, an improvement, or a feature request for an external LLM to implement. Don't use for prompts that already prescribe an implementation, simple one-shot questions, or end-user-facing copy.
This skill should be used to generate a "prompt request" one-pager that summarizes the current session for a pull request. It produces one consolidated User block folding together every ask and decision from the session, plus one Assistant block summarizing what was built. Use it when the user asks to "generate a prompt request", recap or summarize the session for a PR, or capture what was requested. Also use it automatically when opening a pull request or writing a PR description, so the PR body includes the asks and decisions behind the change. Works on the current session only and outputs inline markdown ready to paste into a PR.
Audits a backend AGH change for downstream impact on web/, packages/site, agent-operable CLI/HTTP/UDS surfaces, extensibility surfaces, and config.toml. Adds explicit impact subitems to backend tasks, even when the conclusion is no impact. Use when drafting tasks or reviewing TechSpec coverage for changes touching contracts, handlers, CLI verbs, config, extensions, hooks, skills, tools, resources, bundles, registries, bridges, MCP, or agent workflows. Do not use for purely internal refactors with no public, agent, config, docs, or extensibility surface.
Use after ST Go verdict when retrospective records exist and user authorized feedback — consolidate records and POST to REST API