con un clic
memex-recall
Search the vault for context on a topic
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.
Menú
Search the vault for context on a topic
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
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Analyze the vault for missing related: frontmatter cross-links and present suggestions interactively. Conservative: only surfaces high-evidence (wikilink already in body) and medium-evidence (filepath/title in body, or shared title/H2 terms) candidates. Never edits without explicit per-item user confirmation. Use when the user asks to find missing related: links in the vault, when /memex-sweep flags an isolated spec, or as part of the After-completing-a-spec reflection.
Use when you have a spec or requirements for a multi-step task, before touching code
Use when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding, community health, maintainer burnout, code of conduct, metrics, legal basics, or open source project adoption.
Refactor or audit an existing skill against Anthropic best-practices while preserving its purpose, trigger behavior, and output format. Use when the user asks to improve, refactor, audit, or update a skill — including English phrases like "refactor this skill", "audit skill X", "apply best practices to skill", "improve this skill", "skill audit", "make this skill cleaner", AND Portuguese phrases like "melhorar skill", "atualizar skill", "auditar skill", "aplicar boas práticas", "refatorar skill", "limpar skill". This skill does NOT create new skills (use `skill-creator` for that) and does NOT change WHAT a skill does — only HOW it's organized.
Clone repos using bare clones + git worktrees, develop changes, deliver via Pull Requests. Use this skill whenever the user asks you to clone, code, fix, edit, refactor, implement a feature, or open a PR on any repository — including PT-BR phrasings like "clonar repo", "refatorar", "abrir PR", "corrigir bug", "implementar feature". Covers branch naming, quality gate discovery, commit conventions, and PR delivery rules.
| name | memex-recall |
| description | Search the vault for context on a topic |
Quick reconnaissance of the .vault/ vault. Gives the agent a working map of where things are and what the project cares about, without deep-diving into every file.
Announce at start: "Running project reconnaissance..."
Execute these steps in order. Read files — do not edit anything.
Run a glob for .vault/**/*.md to get the file tree. Present it as a compact list grouped by folder.
Read .vault/constitution.md. Extract and list:
Read all files in .vault/_index/. For each MOC, list the entries it links to (just the note names, not full content).
Output a single structured summary:
What: Stack:
Keep the whole output under 40 lines. This is a map, not a book report.