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.
Polish the next file on the list to the house style without changing what it says, keep the original, and check it.
$ npx skills add receptron/mulmoterminal --skill blueprint-polish-polish -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install receptron/mulmoterminal blueprint-polish-polish --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/polish/skills/polish .claude/skills/blueprint-polish-polish && 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-polish-polish" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/polish/skills/polish into .claude/skills/blueprint-polish-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-polish-polish", 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/polish/skills/polishType 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-polish-polish -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install receptron/mulmoterminal blueprint-polish-polish --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/polish/skills/polish .agents/skills/blueprint-polish-polish && 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-polish-polish" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/polish/skills/polish into .agents/skills/blueprint-polish-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-polish-polish", 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-polish-polish -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install receptron/mulmoterminal blueprint-polish-polish --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/polish/skills/polish .cursor/skills/blueprint-polish-polish && 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-polish-polish" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/polish/skills/polish into .cursor/skills/blueprint-polish-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-polish-polish", 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/polish/skills/polish--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-polish-polish -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install receptron/mulmoterminal blueprint-polish-polish --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/polish/skills/polish .gemini/skills/blueprint-polish-polish && 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-polish-polish" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/polish/skills/polish into .gemini/skills/blueprint-polish-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-polish-polish", 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-polish-polishInstalls 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-polish-polish -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/polish/skills/polish .github/skills/blueprint-polish-polish && 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-polish-polish" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/polish/skills/polish into .github/skills/blueprint-polish-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-polish-polish", 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-polish-polish -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-polish-polish --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/polish/skills/polish .opencode/skills/blueprint-polish-polish && 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-polish-polish" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/polish/skills/polish into .opencode/skills/blueprint-polish-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-polish-polish", 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-polish-polishPolish the next file on the list to the house style without changing what it says, keep the original, and check it.
Blueprint Polish Polish is an agent skill from receptron/mulmoterminal. Polish the next file on the list to the house style without changing what it says, keep the original, and check it.
Its SKILL.md is about 1.2k 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:
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 Polish Polish loads about 1.2k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 722 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). 722 words, ~1,231 tokens.
.claude/skills/blueprint-polish-polish/SKILL.md (or your agent's skills folder).Take the first file in .blueprint/polish.json whose status is "todo". Polish that file only; the
next round takes the next one. When the list is empty, the survey found nothing to polish: change nothing
and stop.
Copy the file to .blueprint/originals/<the same path> before changing anything (create the folders).
The check compares against it, and it is how the person undoes a change.
The document must still say the same thing. What changes is how it is said.
chaff tree), so a
reference such as "第3条第2項" or "Section 4.2" still points at the same place;Follow STYLE.md when the answer scope includes the guide; otherwise, and when there is no scope, fix only what chaff reports.
sh <base pack>/checks/chaff.sh <the file> — with the same --genre as the survey when the answer kind
gives one (see <usecase pack>/kinds.json), and --show-baseline when the answer shelved asks for the shelved
findings too — must report no warning or error, except the ones you set aside.
Set a finding aside — never change the meaning to satisfy a rule — in one of two cases, by adding it to the
file's entry in .blueprint/polish.json:
{ "file": "guide.md", "before": 4, "status": "done",
"dismissed": [{ "rule": "max-sentence-length", "line": 12, "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 the document says.Only a file you mark "done" may set findings aside. rule and line are exactly as chaff reports them now,
one dismissal per finding (two findings of a rule on one line need two); the check refuses a dismissal chaff does not report,
so update the line if your other edits moved it. why is one line the person can judge. Set aside only what
you cannot fix — the report shows every one to the person.
When the answer kind names a kind whose genre has viewpoints in <usecase pack>/viewpoints.json
(genres lists them; viewpoints says what each looks for, and whether you may fix it), read the file
for each of them once chaff is clean, and record every one in .blueprint/viewpoints.json, under the
file's path:
{ "report.md": [
{ "id": "stacked-hedging", "verdict": "fixed", "quote": "増加する可能性があると考えられます" },
{ "id": "actionable-ask", "verdict": "writer", "quote": "ご確認をお願いします",
"note": "誰に、いつまでに確認してもらいますか" },
{ "id": "conclusion-first", "verdict": "ok" }
] }ok — nothing to do. A quote is optional; one you give must be in the file.fixed — only for a viewpoint whose fix is may, and only when the fix adds nothing and drops no fact
(removing a filler sentence, keeping one hedge of two). A fix takes words out; it never puts in a sentence
of your own. When taking the sentence out would leave a heading with nothing under it, it is writer. quote is what was there, copied from the
original; it must no longer be in the file.writer — everything else: a fix that would add a fact (who, by when, a source, a missing section), move
a heading, or change what the writer claims. quote is the place in the file, word for word; note is
the question to ask them, in their language. Do not guess the answer into the document.The check refuses a missing or unknown viewpoint, a fixed the catalog does not allow, and a quotation that
is not where it says.
If the file cannot be polished at all without changing what it says, restore it from the original, set its
status to "skipped" and write a note saying why. Otherwise set it to "done".
node <usecase pack>/checks/targets.mjs verify (with BLUEPRINT_BASE and BLUEPRINT_USECASE set to the
pack folders from your prompt) passes. Run verify, never progress: progress is the executor's check at
the end of the round and records how many files were finished, 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/polish/skills/polish of receptron/mulmoterminal.
Open the folder on GitHubat commit b3f6ff0
Blueprint Polish Polish 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 Polish Polish this skillreceptron/mulmoterminal | 237 | — | ~1.2k | 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 | 36 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
Polish the next file on the list to the house style without changing what it says, keep the original, and check it. Blueprint Polish Polish is an agent skill from receptron/mulmoterminal. Polish the next file on the list to the house style without changing what it says, keep the original, and check it.
Blueprint Polish Polish fits situations like: agent Workflows work in your project.
Run `npx skills add receptron/mulmoterminal --skill blueprint-polish-polish -a claude-code`. Or copy the skill folder (blueprints/polish/skills/polish in receptron/mulmoterminal) into .claude/skills/blueprint-polish-polish in your project. Claude Code loads it when a task matches its description.
Run `npx skills add receptron/mulmoterminal --skill blueprint-polish-polish -a codex`. Or copy the skill folder (blueprints/polish/skills/polish in receptron/mulmoterminal) into .agents/skills/blueprint-polish-polish 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-polish-polish -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-polish-polish, .gemini/skills/blueprint-polish-polish, .github/skills/blueprint-polish-polish and .opencode/skills/blueprint-polish-polish in your project.
Going by SKILL.md and its folder, Blueprint Polish Polish 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 Polish Polish is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.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 Polish Polish: 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.