Menú
Use when the task needs relevant prior notes, vault context, or stored project decisions before planning or execution.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use as the canonical first-stage Agmo workflow when the user wants idea exploration, design tradeoffs, or requirement shaping before planning or implementation.
Run a Codex-native structured code review using agmo-critic and agmo-verifier where evidence is needed.
Harvest `debt:` markers across the repo into a read-only ledger without modifying code.
Audit and maintain the vault-backed llm-wiki knowledge base, including stale pages, low-confidence or contested captures, superseded captures, missing frontmatter, and broken wikilinks.
Use when prior notes, durable project knowledge, or vault-backed context should influence the current task.
Use when one execution lane is no longer enough and work should escalate to the durable `agmo team ...` runtime.
| name | vault-search |
| description | Use when the task needs relevant prior notes, vault context, or stored project decisions before planning or execution. |
| argument-hint | [search topic, note name, or past decision] |
Use this before planning or execution when prior durable context matters.
The main session should delegate note lookup and synthesis to agmo-wisdom, then bring the result back into the active workflow.
After the delegated result is integrated, call close_agent for the agmo-wisdom lane so the completed native subagent session releases its thread slot.
Use this to:
Search is not just filename grep.
Default retrieval order:
Use metadata as evidence when available:
project_noteparentrelatedaliasestype/...When returning results, include:
Before ending a meaningful vault-search stage, make the final response or delegated result save-ready: