memory
/memory
This skill should be used when the user asks to record a design decision, search past project decisions, inspect the Alfred memory timeline, or work with the alfred-memory MCP server. Use it to call the namespaced MCP tools instead of inventing history.
- Author
- 686f6c61 ↗
- Repository
- alfred-dev ↗
- Licence
- MIT
- Last repository change
- 15.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 15.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
This skill should be used when the user asks to record a design decision, search past project decisions, inspect the Alfred memory timeline, or work with the alfred-memory MCP server. Use it to call the namespaced MCP tools instead of inventing history.
Original author description
This skill should be used when the user asks to record a design decision, search past project decisions, inspect the Alfred memory timeline, or work with the alfred-memory MCP server. Use it to call the namespaced MCP tools instead of inventing history.
How it works
- Nombres reales de las tools
- Qué se escribe y qué no
- Consulta
- UI
SKILL.md preview
--- name: memory description: This skill should be used when the user asks to record a design decision, search past project decisions, inspect the Alfred memory timeline, or work with the alfred-memory MCP server. Use it to call the namespaced MCP tools instead of inventing history. --- # Memoria persistente de Alfred Registrar y consultar decisiones del proyecto a través del servidor MCP `alfred-memory`. No inventar historial. Si la herramienta no está disponible, decirlo y no simular resultados. ## Nombres reales de las tools Claude Code expone las tools del plugin con prefijo MCP. Usar estos nombres, no los cortos: - `mcp__plugin_alfred-dev_alfred-memory__memory_search` - `mcp__plugin_alfred-dev_alfred-memory__memory_get_decisions` - `mcp__plugin_alfred-dev_alfred-memory__memory_get_iteration` - `mcp__plugin_alfred-dev_alfred-memory__memory_get_timeline` - `mcp__plugin_alfred-dev_alfred-memory__memory_stats` - `mcp__plugin_alfred-dev_alfred-memory__memory_log_decision` - `mcp__plugin_alfred-dev_alfred-memory__memory_update_decision` - `mcp__plugin_alfred-dev_alfred-memory__memory_link_decisions` - `mcp__plugin_alfred-dev_alfred-memory__memory_health` Si el runtime muestra un prefijo distinto, usar el que aparezca en la lista de tools, siempre del servidor `alfred-memory`. ## Qué se escribe y qué no Sí: decisiones de diseño, resultado de gates, handoffs, UAT y commits hechos en una sesión de Alfred. No: historial antiguo de Git, cada Read/Glob/Grep, consejos operativos ni kanban vacío. Llamar a `memory_log_decision` solo cuando haya una elección real de diseño, seguridad o entrega. No registrar cada edit. Si la decisión es de arquitectura o compliance, el Markdown vivo (`docs/adr/`, `docs/project/compliance.md`) es lo que lee un humano; la memoria no lo sustituye. Campos mínimos: título, contexto, alternativas descartadas, justificación, etiquetas. ## Consulta Para "por qué decidimos X" o "qué hicimos la última vez": `memory_search` o `memory_get_decisions` con el término y, si aplica, rango o tags. Si no hay filas, responder que no hay registros. No inferir. No existe el agente `librarian`. Esta skill y `/alfred-dev:memory-ui` son la vía de consulta histórica. ## UI La vista gráfica es `/alfred-dev:memory-ui`. Esta skill no arranca el servidor HTTP. Para cerrarla: `/alfred-dev:memory-ui stop`. Al terminar la sesión de Claude se detiene sola.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · 686f6c61/alfred-dev | 90 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| topoteretes/cognee-integrations | 100 | Apache-2.0 |
| topoteretes/cognee-integrations | 100 | Apache-2.0 |
| topoteretes/cognee-integrations | 100 | Apache-2.0 |
| thebtf/engram | 100 | MIT |
| stxrmik/antigravity-plus | 100 | MIT |
| boshu2/agentops | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 91144b829dd4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95memmachine
Operate MemMachine/MemMachine, the agent long-term memory server, Python/TypeScript clients and MCP integration. Use when a task names this exact repository, its server, memory APIs, deployment or MCP tools. For general memory architecture selection use… - 90agent-memory
Recall durable project decisions, capture explicitly authorized lessons, and review memory history or corrections using the bundled local memory server. Use when continuity across sessions matters; skip standalone tasks that need no prior context. - 100mcp-server-memory
Use this skill when installing, configuring, and executing tools with the persistent knowledge-graph entity and relation memory MCP server. - 95memory-search
Search conversation history and semantic memory to recall previous discussions, decisions, and context. Use when the user asks to "search memory", "what did we discuss", "remember when", "find previous conversation", "check history", or before starting work to recall prior decisions. - 100memory-search
Search and retrieve information from the Appie brain — daily logs, project notes, decisions, topics, and long-term memory files stored in ~/.hermes/memory/. Use this skill whenever you need to recall past conversations, decisions, project context, personal preferences, or… - 100memory-search
Search and retrieve information from the Appie brain — daily logs, project notes, decisions, topics, and long-term memory files stored in ~/.hermes/memory/. Use this skill whenever you need to recall past conversations, decisions, project context, personal preferences, or…