Menú
Record one atomic friction into the learning inbox (via MCP) — the gap between what is and what could be. Use when something caused friction, confusion, a blocker, or an improvement opportunity appeared.
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
Refresh the Merovingian CLI, rebuild the current generated workspace with its original purpose selection, and fast-forward its context repositories. Use only when the human explicitly asks to update or refresh this workspace.
The heavy governance pass — drain the tenant's learning inbox (journal/friction) AND the in-flight decision log, synthesize tensions WITH the human, turn the agreed ones into graph/library changes and promote converged decisions into ratified records (decisions/), stamp everything drained, and close the git loop. Use when the human asks for a governance pass, to drain the inbox, or to review accumulated frictions, learnings and decisions.
Start-here guide and router for operating a Merovingian tenant. Teaches the purpose-graph mental model, build versus deploy, desired-state authoring, and the CLI; routes tenant administration to tenant-admin and governance passes to drain. Use when starting with Merovingian, operating a tenant, or unsure which workflow or command applies.
Operate the administrative lifecycle of a Merovingian tenant. Use when a tenant admin needs to connect or bootstrap a tenant, onboard or offboard members, manage access and passwords, build or refresh workspaces, sync plugins, verify enforcement, troubleshoot runtime problems, or prepare a production rollout.
The LOCAL governance pass — list and clear the pending frictions within your reach (via the inbox MCP). Invoked BY THE HUMAN when they want to tend the queue; never run it spontaneously at session start or mid-task.
Record the session — progress, problems, insights and context gaps — into the learning inbox (via the inbox MCP journal tool).
| name | friction |
| description | Record one atomic friction into the learning inbox (via MCP) — the gap between what is and what could be. Use when something caused friction, confusion, a blocker, or an improvement opportunity appeared. |
| argument-hint | optional hint about the friction |
Record a friction — the gap between what is and what could be — atomically,
in the moment, with the context fresh. The skill is the method (capture it
well-formed); the record goes to the inbox table in Surreal via the friction
tool of the inbox MCP (append-only, user stamped server-side, drained only by
governance). Never write to disk.
Frictions are the fuel of governance.
Identify the friction in the recent interaction: what ground, confused,
blocked, or what improvement opportunity appeared. If the human gave a hint
($ARGUMENTS), use it as direction; otherwise take the most relevant recent one.
Assemble the record as structured markdown, in the shape of the sibling
format.md file. Be rich and specific in the record (not in
the reply).
Scope it — whose problem is this? The criterion is the MOUNTS: who has the context and access to actually fix it?
scope = your purpose.scope = that
ancestor. Escalation happens HERE, at creation — pick the ancestor now.scope (the root governance queue).Write to the inbox: call the friction tool (of the inbox MCP server)
with the markdown as the text argument, origin = who you are right now
(the purpose/agent acting — a subagent names itself, not the shell that dispatched
it) and the scope from step 3. Each friction is a separate append.
Confirm in one sentence. E.g. "Friction recorded (scope: delivery): X and Y terms are easily confused." No essay, no follow-up.