Agent skill

Blueprint Write Brief

by receptron in receptron/mulmoterminal

Turn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources.

MITAuto-check passedAgent Workflows

Install Blueprint Write Brief

skills CLI
$ npx skills add receptron/mulmoterminal --skill blueprint-write-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install receptron/mulmoterminal blueprint-write-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
blueprint-write-brief
GitHub stars
237
Token cost
~507 tokens
SKILL.md length
282 words
Files
1
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

Turn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources.

  • Agent Workflows work in your project
  • SKILL.md covers Collect the sources (when…, Write .blueprint/brief.md, Which style and Done when
  • Calls node

What it does

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.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/blueprint-write-brief”

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:

    • node

    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 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.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~507

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). 282 words, ~507 tokens.

Download SKILL.mdSave it as .claude/skills/blueprint-write-brief/SKILL.md (or your agent's skills folder).
name
blueprint-write-brief
description
Turn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources.

The brief

.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.

Collect the sources (when 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.

Write .blueprint/brief.md

In 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.

Which style

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.

Done when

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

Files

Just SKILL.md in blueprints/write/skills/brief of receptron/mulmoterminal.

Open the folder on GitHubat commit b3f6ff0

Compare with similar skills

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.

Blueprint Write Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Blueprint Write Brief this skillreceptron/mulmoterminal237—~507Automated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • 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

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • 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.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    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.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from receptron/mulmoterminal

All 31 skills in this repo
  • Mulmoterminal Bug Report

    receptron/mulmoterminal

    Help desk for "MulmoTerminal is broken". An agent skill from receptron/mulmoterminal.

    237 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Mulmoterminal Decisions

    receptron/mulmoterminal

    Check what this project's humans have already been asked, and how they answered, before asking them something similar.

    237 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • 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.

    237 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • 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…

    237 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • 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.

    237 GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • 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.

    237 GitHub stars~780 tokensUpdated today
    Auto-check passed

Categories

Questions about Blueprint Write Brief

What does Blueprint Write Brief do?

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.

When should I use Blueprint Write Brief?

Blueprint Write Brief fits situations like: agent Workflows work in your project.

How do I install Blueprint Write Brief in Claude Code?

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.

How do I install Blueprint Write Brief in Codex?

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.

Can I use Blueprint Write Brief 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-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.

What does Blueprint Write Brief need to run?

Going by SKILL.md and its folder, Blueprint Write Brief needs the command-line tools its instructions call (node).

Does Blueprint Write Brief 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 Write Brief 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 Write Brief use?

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.

How many tokens does Blueprint Write Brief use?

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.

What are the alternatives to Blueprint Write Brief?

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.

Who maintains Blueprint Write Brief?

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.