MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Write the next part of the outline to the house style, check it with chaff, cite what came from the sources, and mark it done.
$ npx skills add receptron/mulmoterminal --skill blueprint-write-draft -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install receptron/mulmoterminal blueprint-write-draft --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/blueprints/write/skills/draft .claude/skills/blueprint-write-draft && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "blueprint-write-draft" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/draft into .claude/skills/blueprint-write-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-draft", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/draftType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add receptron/mulmoterminal --skill blueprint-write-draft -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install receptron/mulmoterminal blueprint-write-draft --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .agents/skills && cp -r skills-src/blueprints/write/skills/draft .agents/skills/blueprint-write-draft && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "blueprint-write-draft" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/draft into .agents/skills/blueprint-write-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-draft", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add receptron/mulmoterminal --skill blueprint-write-draft -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install receptron/mulmoterminal blueprint-write-draft --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/blueprints/write/skills/draft .cursor/skills/blueprint-write-draft && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "blueprint-write-draft" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/draft into .cursor/skills/blueprint-write-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-draft", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/receptron/mulmoterminal.git --path blueprints/write/skills/draft--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add receptron/mulmoterminal --skill blueprint-write-draft -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install receptron/mulmoterminal blueprint-write-draft --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/blueprints/write/skills/draft .gemini/skills/blueprint-write-draft && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "blueprint-write-draft" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/draft into .gemini/skills/blueprint-write-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-draft", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install receptron/mulmoterminal blueprint-write-draftInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add receptron/mulmoterminal --skill blueprint-write-draft -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .github/skills && cp -r skills-src/blueprints/write/skills/draft .github/skills/blueprint-write-draft && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "blueprint-write-draft" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/draft into .github/skills/blueprint-write-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-draft", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add receptron/mulmoterminal --skill blueprint-write-draft -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install receptron/mulmoterminal blueprint-write-draft --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/blueprints/write/skills/draft .opencode/skills/blueprint-write-draft && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "blueprint-write-draft" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/draft into .opencode/skills/blueprint-write-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-draft", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
blueprint-write-draftWrite the next part of the outline to the house style, check it with chaff, cite what came from the sources, and mark it done.
Blueprint Write Draft is an agent skill from receptron/mulmoterminal. Write the next part of the outline to the house style, check it with chaff, cite what came from the sources, and mark it done.
Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. The repository describes itself as: Run multiple Claude Code and Codex sessions in parallel — a browser terminal grid that shows which agent needs you. Local, tmux-backed, MIT. The licence is MIT.
Read from SKILL.md and the folder at commit 9182c53. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
shnodeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Blueprint Write Draft loads about 735 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 394 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from receptron/mulmoterminal at commit 9182c53, republished under its MIT licence (© receptron). 394 words, ~735 tokens.
.claude/skills/blueprint-write-draft/SKILL.md (or your agent's skills folder).Take the first part in .blueprint/outline.json whose status is "todo". Write that part only; the
next round writes the next one.
Read .blueprint/brief.md, the part's points, and — when the folder has one — STYLE.md. Read the parts
already written, so terms, tone and numbering continue rather than restart.
file, beginning with its title as a heading.STYLE.md: voice, sentence endings, terms, structure. It is the part of the style a machine
cannot check, and the reason it exists.points.For each sentence that states something taken from a source, record the source passage in
.blueprint/citations/<part id>.json:
[{ "source": "annual-report.md", "address": "h1.2", "quote": "売上は前年比 12% 増えた" }]address is where the passage sits in the source's tree: sh <base pack>/checks/chaff.sh tree .blueprint/sources/<file> prints it (a heading's h1.2, an article's 3.2). quote is the source's own
words, copied, not your paraphrase. The check runs chaff cite on each source.
sh <base pack>/checks/chaff.sh <the part's file> must report no warning or error. Fix the text, not the
style. Set a finding aside only in one of two cases, by adding it to the part in .blueprint/outline.json:
{ "id": "intro", "file": "01-intro.md", "status": "done",
"dismissed": [{ "rule": "max-sentence-length", "line": 8, "because": "meaning", "why": "資料の一文をそのまま引用している" }] }"because": "wrong" — chaff misread the text (a heading it took for a sentence, a name it took for jargon).
Each one becomes a draft report to chaff in the report step."because": "meaning" — chaff is right, but fixing it would change what must stay exact (a quotation).rule and line are exactly as chaff reports them now, one dismissal per finding; the check refuses a
dismissal chaff does not report.
why is one line the person can judge. Never silence a rule in chaff.yaml or with stet to get past it.
Then set the part's status to "done".
node <usecase pack>/checks/parts.mjs verify (with BLUEPRINT_BASE and BLUEPRINT_USECASE set to the
pack folders from your prompt) passes: every done part is written, raises no finding it did not set aside, and quotes its
sources faithfully. Run verify, never progress: progress is the executor's check at the end of the
round and records how many parts were done, so running it yourself makes the real check fail.
© receptron, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in blueprints/write/skills/draft of receptron/mulmoterminal.
Open the folder on GitHubat commit 9182c53
Blueprint Write Draft next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Blueprint Write Draft this skillreceptron/mulmoterminal | 236 | — | ~735 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
receptron/mulmoterminal
Help desk for "MulmoTerminal is broken". An agent skill from receptron/mulmoterminal.
receptron/mulmoterminal
Check what this project's humans have already been asked, and how they answered, before asking them something similar.
receptron/mulmoterminal
Decide which moments MulmoTerminal beeps or pushes for, and what each one plays — soundKinds, sounds and pushKinds in ~/.mulmoterminal/config.json, plus a per-project sound / sounds in…
receptron/mulmoterminal
Build a colour scheme of your own for MulmoTerminal — one that joins Midnight, Nord, Daylight and Solarized in Settings' theme picker and can then be pinned per project.
receptron/mulmoterminal
Answer each question from the named documents only, quoting where the answer is written, or saying plainly that the documents do not say — changing nothing yet.
receptron/mulmoterminal
Review the finished Worker against OWASP Top 10:2025, fix what is exploitable, prove each fix with a test, and report.
Categories
Write the next part of the outline to the house style, check it with chaff, cite what came from the sources, and mark it done. Blueprint Write Draft is an agent skill from receptron/mulmoterminal. Write the next part of the outline to the house style, check it with chaff, cite what came from the sources, and mark it done.
Blueprint Write Draft fits situations like: agent Workflows work in your project.
Run `npx skills add receptron/mulmoterminal --skill blueprint-write-draft -a claude-code`. Or copy the skill folder (blueprints/write/skills/draft in receptron/mulmoterminal) into .claude/skills/blueprint-write-draft in your project. Claude Code loads it when a task matches its description.
Run `npx skills add receptron/mulmoterminal --skill blueprint-write-draft -a codex`. Or copy the skill folder (blueprints/write/skills/draft in receptron/mulmoterminal) into .agents/skills/blueprint-write-draft in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add receptron/mulmoterminal --skill blueprint-write-draft -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blueprint-write-draft, .gemini/skills/blueprint-write-draft, .github/skills/blueprint-write-draft and .opencode/skills/blueprint-write-draft in your project.
Going by SKILL.md and its folder, Blueprint Write Draft needs the command-line tools its instructions call (sh and node).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Blueprint Write Draft is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 735 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Blueprint Write Draft: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
receptron (a GitHub organization) maintains it in receptron/mulmoterminal, which has 236 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 8, 2026.
Source: receptron/mulmoterminal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.