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.
Turn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources.
$ npx skills add receptron/mulmoterminal --skill blueprint-write-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install receptron/mulmoterminal blueprint-write-brief --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/brief .claude/skills/blueprint-write-brief && 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-brief" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/brief into .claude/skills/blueprint-write-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-brief", 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/briefType 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-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install receptron/mulmoterminal blueprint-write-brief --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/brief .agents/skills/blueprint-write-brief && 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-brief" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/brief into .agents/skills/blueprint-write-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-brief", 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-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install receptron/mulmoterminal blueprint-write-brief --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/brief .cursor/skills/blueprint-write-brief && 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-brief" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/brief into .cursor/skills/blueprint-write-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-brief", 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/brief--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-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install receptron/mulmoterminal blueprint-write-brief --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/brief .gemini/skills/blueprint-write-brief && 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-brief" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/brief into .gemini/skills/blueprint-write-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-brief", 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-briefInstalls 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-brief -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/brief .github/skills/blueprint-write-brief && 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-brief" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/brief into .github/skills/blueprint-write-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-brief", 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-brief -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-brief --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/brief .opencode/skills/blueprint-write-brief && 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-brief" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/write/skills/brief into .opencode/skills/blueprint-write-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-write-brief", 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-briefTurn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources.
Blueprint Write Brief is an agent skill from receptron/mulmoterminal. Turn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources.
Its SKILL.md is about 510 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 b3f6ff0. 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:
nodeFrom 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 Brief loads about 507 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 282 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 b3f6ff0, republished under its MIT licence (© receptron). 282 words, ~507 tokens.
.claude/skills/blueprint-write-brief/SKILL.md (or your agent's skills folder)..blueprint/answers.json holds what the person asked for. The person may not be a writer or an engineer:
say what you do in plain words.
Change nothing in the repository: this step writes only inside .blueprint/. The person reads the brief
and approves it before anything of theirs is written.
sources is not empty)Copy each file, or fetch each page's article body only, as Markdown into .blueprint/sources/, and
list them in .blueprint/sources.json as [{ "file", "origin" }]. Never rewrite a source: a later check
compares quotations against it word for word.
.blueprint/brief.mdIn the language the document will be written in, with these sections (either name works):
## 目的 / ## Purpose — what the document is for, in one or two sentences.## 読者 / ## Audience — who reads it and what they can do after reading.## 要点 / ## Key points — every point from the answer points, plus what the topic needs.## 資料から取る事実 / ## Facts from sources — each fact the document will state, with the source file
it comes from. With no sources, write "資料なし — 事実は書き手の知識による" and say which facts need checking.## 決まっていないこと / ## Open questions — what you would ask the person. Write "なし" if there is none.Do not invent facts. A number, a name, a date or a quotation that is not in the sources goes under open questions, not under facts.
If the answer style is the folder's style, read STYLE.md and chaff.yaml now and note anything in them
that shapes this document. If they are missing, stop: the check tells the person to make the style first
or to choose chaff's defaults.
node <usecase pack>/checks/brief.mjs (with BLUEPRINT_BASE and BLUEPRINT_USECASE set to the pack
folders from your prompt) passes.
© 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/brief of receptron/mulmoterminal.
Open the folder on GitHubat commit b3f6ff0
Blueprint Write Brief 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 Brief this skillreceptron/mulmoterminal | 237 | — | ~507 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 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 | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | 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.
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
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.
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
Help desk for questions about MulmoTerminal itself — what it can do, how a feature or a part of the screen works, how to set something up, what is new in this version or in the latest one.
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.
Categories
Turn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources. Blueprint Write Brief is an agent skill from receptron/mulmoterminal. Turn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources.
Blueprint Write Brief fits situations like: agent Workflows work in your project.
Run `npx skills add receptron/mulmoterminal --skill blueprint-write-brief -a claude-code`. Or copy the skill folder (blueprints/write/skills/brief in receptron/mulmoterminal) into .claude/skills/blueprint-write-brief in your project. Claude Code loads it when a task matches its description.
Run `npx skills add receptron/mulmoterminal --skill blueprint-write-brief -a codex`. Or copy the skill folder (blueprints/write/skills/brief in receptron/mulmoterminal) into .agents/skills/blueprint-write-brief 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-brief -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-brief, .gemini/skills/blueprint-write-brief, .github/skills/blueprint-write-brief and .opencode/skills/blueprint-write-brief in your project.
Going by SKILL.md and its folder, Blueprint Write Brief needs the command-line tools its instructions call (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 Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 507 tokens (SKILL.md is roughly 2k 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 Brief: 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, 297k 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 237 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 10, 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.