Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Edit a content draft โ structure, voice, tightness.
Record one atomic friction โ the gap between what is and what could be โ into the learning inbox (via the inbox MCP friction tool).
Record the session โ progress, problems, insights and context gaps โ into the learning inbox (via the inbox MCP journal tool).
The local governance pass โ list and clear the pending frictions within your reach (via the inbox MCP pending/resolve/rescope tools). Invoked by the human; never run spontaneously.
Route a request to the right purpose/persona of this workspace.
Draft a content piece in acme's voice from a brief.
| 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
${CLAUDE_SKILL_DIR}/format.md. 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.