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.
Extract every dated event, time and amount from the named documents into .blueprint/facts.json, each with a quotation it was read from — deciding nothing yet.
Install Blueprint Verify Extract
$ npx skills add receptron/mulmoterminal --skill blueprint-verify-extract -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install receptron/mulmoterminal blueprint-verify-extract --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/verify/skills/extract .claude/skills/blueprint-verify-extract && 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-verify-extract" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/verify/skills/extract into .claude/skills/blueprint-verify-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-verify-extract", 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/verify/skills/extractType 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-verify-extract -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install receptron/mulmoterminal blueprint-verify-extract --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/verify/skills/extract .agents/skills/blueprint-verify-extract && 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-verify-extract" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/verify/skills/extract into .agents/skills/blueprint-verify-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-verify-extract", 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-verify-extract -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install receptron/mulmoterminal blueprint-verify-extract --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/verify/skills/extract .cursor/skills/blueprint-verify-extract && 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-verify-extract" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/verify/skills/extract into .cursor/skills/blueprint-verify-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-verify-extract", 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/verify/skills/extract--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-verify-extract -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install receptron/mulmoterminal blueprint-verify-extract --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/verify/skills/extract .gemini/skills/blueprint-verify-extract && 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-verify-extract" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/verify/skills/extract into .gemini/skills/blueprint-verify-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-verify-extract", 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-verify-extractInstalls 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-verify-extract -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/verify/skills/extract .github/skills/blueprint-verify-extract && 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-verify-extract" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/verify/skills/extract into .github/skills/blueprint-verify-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-verify-extract", 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-verify-extract -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-verify-extract --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/verify/skills/extract .opencode/skills/blueprint-verify-extract && 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-verify-extract" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/verify/skills/extract into .opencode/skills/blueprint-verify-extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-verify-extract", 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.
Facts
- Skill name
blueprint-verify-extract- GitHub stars
- 237
- Token cost
- ~1.1k tokens
- SKILL.md length
- 573 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
Extract every dated event, time and amount from the named documents into .blueprint/facts.json, each with a quotation it was read from — deciding nothing yet.
- Agent Workflows work in your project
- SKILL.md covers Write .blueprint/facts.json and Done when
- Calls sh and node
What it does
Blueprint Verify Extract is an agent skill from receptron/mulmoterminal. Extract every dated event, time and amount from the named documents into .blueprint/facts.json, each with a quotation it was read from — deciding nothing yet.
Its SKILL.md is about 1.1k 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.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/blueprint-verify-extract”
What it can do on your machine
Read from SKILL.md and the folder at commit b3f6ff0. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
shnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Blueprint Verify Extract loads about 1.1k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 573 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from receptron/mulmoterminal at commit b3f6ff0, republished under its MIT licence (© receptron). 573 words, ~1,133 tokens.
Download SKILL.mdSave it as
.claude/skills/blueprint-verify-extract/SKILL.md (or your agent's skills folder).- name
- blueprint-verify-extract
- description
- Extract every dated event, time and amount from the named documents into .blueprint/facts.json, each with a quotation it was read from — deciding nothing yet.
Extract the dates, times and amounts
.blueprint/answers.json names the documents (documents, one path per line), what kind they are (kind),
the year to use for dates written without one (year, may be empty) and what the person is worried about
(focus). Read every document in full, starting with focus.
This step only reads and copies values out. It does not judge whether anything is wrong. That is decided by
machine in the next step, so do not skip an entry because it looks wrong. A wrong weekday or a wrong total is
exactly what must be extracted as written. Change nothing in the repository: the documents stay exactly as
they are. Write only under .blueprint/. A person reads the table you write before the machine judges it, so a
missed event is theirs to catch.
Write .blueprint/facts.json
{
"events": [
{
"id": "day1-depart",
"date": "2026-10-01",
"weekday": "木",
"start": "09:00",
"end": "11:30",
"title": "東京駅から新大阪駅（のぞみ）",
"citation": { "source": "itinerary.md", "address": "h2.1", "quote": "10月1日（木）9:00 東京駅発 → 11:30 新大阪駅着" }
}
],
"amounts": [
{ "id": "hotel", "label": "宿泊費", "value": 24000, "unit": "円", "citation": { "source": "estimate.md", "address": "h2.2", "quote": "宿泊費 24,000円" } }
],
"totals": [
{ "id": "grand-total", "label": "合計", "value": 36000, "unit": "円", "parts": ["hotel", "train"], "citation": { "source": "estimate.md", "address": "h2.2", "quote": "合計 36,000円" } }
],
"products": [
{ "id": "hotel-line", "label": "宿泊費", "value": 24000, "unit": "円", "of": ["hotel-rate", "hotel-nights"], "citation": { "source": "estimate.md", "address": "h2.2", "quote": "宿泊費 12,000円 × 2泊 = 24,000円" } }
]
}- One event per thing that happens at a time: a departure, a check-in, a meeting. Keep them in the order the document gives them, because the next step reads that order as the intended sequence.
dateisYYYY-MM-DD. When the document omits the year, useyearfrom the answers. If that is empty too, write the date asMM-DD("10-01") and give it noweekday: a weekday without a year cannot be checked, and the check refuses one.weekdayis copied as written (「木」「(木)」「Thu」). Leave it out when the document gives none. Never add one the document does not have, and never correct one.start/endareHH:MM, 24-hour. Leave out what the document does not say. A range that writes AM/PM once covers both times:1:00–5:00 PMis 13:00–17:00,午後1時〜5時is 13:00–17:00.amountsare the lines that add up;totalsare the lines that claim to be their sum (合計, 小計, Total), withpartsnaming the amount ids they add up. A subtotal that is itself part of a grand total is both: list it as an amount too, under another id, and name that id in the grand total'sparts.productsare the lines that claim to be a product: a line's amount that is its unit price times its quantity (単価 × 数量), a tax that is a subtotal times a rate.ofnames the amount ids multiplied, two or more: the price and the quantity (unit台, 泊, 個, pcs — as written), or the subtotal and the rate (value10,unit%). Like a subtotal, a line that is also added into a total is listed as an amount too, under another id. Extract a product only where the document gives every factor; a line with no quantity written is not one.valueis a plain number (24000, not"24,000円");unitis the currency or unit as written (円, USD).id: lower-case letters, digits and-, unique across the whole file.citation.quoteis copied character for character from the document and must contain every value of its entry: the month and day, the weekday, each time, the amount. A quote may run over a line break (for a date in a heading above the times, quote from the heading through the line).addressuseschaff tree's addresses (sh <base pack>/checks/chaff.sh tree <document>).
Show full SKILL.md (53 more words)Show less
Done when
node <usecase pack>/checks/extract.mjs (with BLUEPRINT_BASE and BLUEPRINT_USECASE set to the pack folders
from your prompt) passes. It fails on a value that is not in its own quotation (a misread), on a quotation
chaff cite cannot find in the document, and on a malformed entry. Fix the extraction, not the check.
© receptron, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in blueprints/verify/skills/extract of receptron/mulmoterminal.
Open the folder on GitHubat commit b3f6ff0
Compare with similar skills
Blueprint Verify Extract 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 Verify Extract this skillreceptron/mulmoterminal | 237 | — | ~1.1k | 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 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
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.
Using Superpowers
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
Executing Plans Inline
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.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Claude Code Agent Development
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.
More from receptron/mulmoterminal
All 31 skills in this repoMulmoterminal Bug Report
receptron/mulmoterminal
Help desk for "MulmoTerminal is broken". An agent skill from receptron/mulmoterminal.
Mulmoterminal Decisions
receptron/mulmoterminal
Check what this project's humans have already been asked, and how they answered, before asking them something similar.
Mulmoterminal Help
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.
Mulmoterminal Notify
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…
Mulmoterminal Theme
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.
Blueprint Ask Answer
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.
Related
Categories
Questions about Blueprint Verify Extract
What does Blueprint Verify Extract do?
Extract every dated event, time and amount from the named documents into .blueprint/facts.json, each with a quotation it was read from — deciding nothing yet. Blueprint Verify Extract is an agent skill from receptron/mulmoterminal.json, each with a quotation it was read from — deciding nothing yet.
When should I use Blueprint Verify Extract?
Blueprint Verify Extract fits situations like: agent Workflows work in your project.
How do I install Blueprint Verify Extract in Claude Code?
Run `npx skills add receptron/mulmoterminal --skill blueprint-verify-extract -a claude-code`. Or copy the skill folder (blueprints/verify/skills/extract in receptron/mulmoterminal) into .claude/skills/blueprint-verify-extract in your project. Claude Code loads it when a task matches its description.
How do I install Blueprint Verify Extract in Codex?
Run `npx skills add receptron/mulmoterminal --skill blueprint-verify-extract -a codex`. Or copy the skill folder (blueprints/verify/skills/extract in receptron/mulmoterminal) into .agents/skills/blueprint-verify-extract in your project. Codex loads it when a task matches its description.
Can I use Blueprint Verify Extract in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add receptron/mulmoterminal --skill blueprint-verify-extract -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-verify-extract, .gemini/skills/blueprint-verify-extract, .github/skills/blueprint-verify-extract and .opencode/skills/blueprint-verify-extract in your project.
What does Blueprint Verify Extract need to run?
Going by SKILL.md and its folder, Blueprint Verify Extract needs the command-line tools its instructions call (sh and node).
Does Blueprint Verify Extract access the network?
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.
Is Blueprint Verify Extract safe to install?
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.
What licence does Blueprint Verify Extract use?
Blueprint Verify Extract is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Blueprint Verify Extract use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Blueprint Verify Extract?
Skills that share tags, products or a category with Blueprint Verify Extract: 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.
Who maintains Blueprint Verify Extract?
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.