merovingian
merovingian contains 12 collected skills from supernova-labs, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
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.
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.
Onboarding and operations guide for a Merovingian tenant. Teaches the mental model (the purpose-graph as desired state, build vs deploy, the graph.yaml shape) and the CLI (init, deploy plan/apply, reset). Use when operating a tenant or unsure which command to run.
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.
Record the session's progress, problems, insights and context gaps into the learning inbox (via MCP). Use when closing a session, at a checkpoint, or to document what was done.
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.
Route a request to the right purpose/persona of this workspace — everyone lands on the shell and route dispatches to whoever decides or executes it. Use when a request is not clearly of a single purpose, or at session start with no set destination.