Menu
SkillsMP has collected 29 skills from iopsystems/skills-mcp. Open a skill to review its source and details.
Showing 29 of 29 collected skills.
Draft the pull-request body as a guide for the human reviewing it: where to look more closely, what was tested and what was not, which calls were rather than deduction, and what will only show up in production. Use when asked to "draft the PR body", "write…
Use when creating or materially revising system architecture diagrams — a build-time structure chart (units, layers, product composition) or runtime charts (thread model, life-of-a-request flow). Triggers include "architecture diagram", "threading diagram",…
Use when creating or materially revising a project's README, code documentation, CLI help, diagrams, onboarding, or other feature documentation for users or developers.
Use when creating or materially revising a project's README, code documentation, CLI help, diagrams, onboarding, or other feature documentation for users or developers.
Use when creating or materially revising system architecture diagrams — a build-time structure chart (units, layers, product composition) or runtime charts (thread model, life-of-a-request flow). Triggers include "architecture diagram", "threading diagram",…
Draw a dataflow or pipeline diagram for a program that already exists in code — a DAG, a processing chain, a stream topology, a service graph. Use when asked to "diagram the pipeline", "show the dataflow", "chart the DAG", "visualize how the data moves",…
Draw the layout of a memory or wire format that already exists in code — a byte anatomy of one encoded instance, the per-variant conventions of a shared encoding, or the linkage between blocks. Use when asked to "diagram the format", "show the byte layout",…
Use when drawing or materially revising a dataflow or pipeline diagram for a program that already exists in code — a DAG, a processing chain, a stream topology, a service graph. Triggers include "diagram the pipeline", "show the dataflow", "chart the DAG",…
Use when starting, continuing, handing off, or closing a non-trivial engineering or research effort in a shared repository; when preserving a measured negative result; when reconciling journal status, index, or backlog drift; or when identifying journal…
Use when starting, continuing, handing off, reconciling, or closing a non-trivial engineering or research effort in a repository with durable project records.
State the word-level bar for technical prose: no hedged modality, no vocabulary that carries no fact, one name per thing. Use when asked to "de-slop this", "tighten this wording", "make this plainer", "cut the AI voice", or when another skill defers here for…
Exchange threaded review notes with another local agent through a repo-local git bridge. Use when asked to "review this branch", "get a second opinion", "check the review feedback", "reply to the review", "what did Codex say", or whenever two independent…
Reconcile the knowledge-iop vault. Two modes, same skill. **Interactive** — invoked after a phase skill commits an artifact; scoped to the touched artifact and its immediate graph neighborhood; applies and merges clean transitions by default. **Dream** —…
Hold code comments and docstrings to a strict quality bar. Use whenever writing or editing comments — adding a comment to new code, being asked to "document this", "add comments", or "make this reviewer-ready" — and as a dedicated staleness sweep before…
Query the knowledge-iop vault as a habit before drafting anything. Before you write a new problem-brief, design-brief, inquiry, decision, discussion, scope, or arc, first check whether a relevant artifact already exists so you can supersede, relate to, or…
Use when a user has approved a catalog skill template to seed, customize, or upgrade, or explicitly asks to perform one of those actions for a project-local installed instance.
Use when a user asks which active skills from this MCP skill catalog or embedded agent-skill templates to use, seed, or adopt for a project; or when checking whether a project-local instance already covers that catalog need.
Scope, frame, and design a feature end-to-end — especially one that spans more than one repo. Runs a multi-turn Q&A covering problem, user value, constraints, surface area, key decisions, and cross-repo coordination, then fans the output out into the right…
Close an open **arc** — mark its narrative complete (`closed`) or explicitly set aside (`abandoned`), and audit that its closing conditions were actually met. Use this when the user says things like "close the X arc", "we're done with this arc", "abandon arc…
Define a new **scope** — a stable reference frame (service, domain, surface, cross-cutting concern) that the vault cares about for years rather than the duration of a narrative arc. Use this when the user says things like "we need a scope for X", "add a…
Capture a conversation or working session as a **discussion** (multiple attendees) or **session note** (solo author, often with an agent) in the knowledge-iop vault, AND surface what existing artifacts the conversation implicates. Discussions are the vault's…
Draft a **problem brief** — the "what actually is the problem" half of the paired briefs convention in knowledge-iop. A problem brief is written before any solution is proposed. Use this whenever the user says things like "we need a problem brief", "let's…
Open a new **arc** — a narrative unit of change in the knowledge-iop vault that spans weeks to quarters. Arcs have a beginning, middle, and end. Use this when the user says things like "let's start an arc for X", "open the Y arc", "we're kicking off a project…
Open a bounded parallel **inquiry** — the knowledge-iop vault's barrier-mode coordination primitive for cases where multiple people should explore a question independently before anyone synthesizes. Use this when the user says things like "let's explore…
Draft a **design brief** — the "how do we solve it" half of the paired briefs convention in knowledge-iop. Every design brief must declare `frames:` pointing at a problem brief (or `frames: none` with a reason, discouraged). Use this whenever the user says…
Record a **decision** — the "because" that cites one or more design briefs (each of which frames a problem brief). Three-hop traceability: why do we do this? → this design → because of this problem. Use this when the user says things like "record the…
Author a single **exploration** within an open inquiry — one explorer's independent take on the question, drafted in isolation from other explorers. Use this when the user says things like "I want to contribute to inquiry X", "let me write my take on this",…
Write the **synthesis** that closes an inquiry — read every submitted exploration, reconcile them against the framing, and produce the inquiry's resolved take. Use this when the user says things like "the barrier has released", "let's synthesize the inquiry",…
Summarize recent development activity in the current repo so the user can catch up on what others have changed in the last hours/days/weeks. Picks the window automatically — since the user's last commit, or else the larger of the last 5 commits vs the last 7…