con un clic
m3-save
Auto-classified save — picks type/scope automatically, confirms before writing.
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ú
Auto-classified save — picks type/scope automatically, confirms before writing.
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
List registered agents and their last heartbeat. Useful for multi-agent setups.
GDPR Article 20 — export all memories you own as portable JSON.
Search captured chat-log turns from your prior Claude / Gemini / Antigravity sessions.
Delete a memory permanently. Asks for confirmation first.
Fetch one memory by UUID or short prefix.
Show memories related to a given one — knowledge-graph traversal up to 3 hops.
| name | m3-save |
| description | Auto-classified save — picks type/scope automatically, confirms before writing. |
Use this skill when you want to write a new observation, fact, decision, or preference to memory, and want the system to automatically classify its type, scope, and title while verifying it with the user first.
You're about to write to m3-memory. Do not call memory_write yet. First propose a plan:
$ARGUMENTS) plus the last few turns of context.type from this list:
decision — choices made with a whyfact — verifiable assertion about the worldpreference — user's stated like / dislike / conventionnote — informal observation, doesn't fit other typestask — actionable item with statereference — pointer to external doc / URL / locationknowledge — durable understanding of how something worksobservation — what you noticed during a sessionsummary — distilled takeaway from a longer threadscope (default: user) — most personal facts/preferences are user-scoped; project knowledge often isn't.title if missing.{type, scope, title, content} and ask for a single y to write, or any other key to abort.y: call m3:memory_write with those fields.Reasoning for the choices is fine to include but keep it short — the user wants speed, not a treatise.