- name
SKILL.md
Файл навыка остаётся в репозитории издателя.
Вставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add coreyhaines31/makerskills --skill business-brainstorm -a cursor -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add coreyhaines31/makerskills --skill business-brainstorm -a claude-code -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add coreyhaines31/makerskills --skill business-brainstorm -a codex -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add coreyhaines31/makerskills --skill business-brainstorm -a grok -yОтправьте скопированное сообщение в чат Grok Bot. Бот загрузит этот SKILL.md с GitHub и добавит его к навыкам, общим для всех ваших ботов.
Install this skill: https://github.com/coreyhaines31/makerskills/tree/HEAD/skills/business-brainstormОт издателя
Takes a vague idea, runs it through the user's filter, and outputs a structured viability brief. Composes with deep-research (for market) and /domain (for naming).
Get from the user:
Resume first. Look in the archive dir (Step 7) for files whose first line starts with `
Leave the later brief sections out until Step 7, so an unfinished file never looks finished. As each dimension settles, fill its row and update the marker. If the session dies, the next one resumes from the file. Don't touch `INDEX.md` until Step 7.
Where a dimension depends on something only the user knows (their audience access, energy, what this displaces), ask — one dimension at a time — rather than guessing. Then **hold the bar** on what they say:
- **Hopes don't score.** "People want it," "we'll figure out distribution," "should be easy to build" — stay on it, offer 1–2 sharper candidate answers or ask for one piece of evidence (a waitlist, a request, a competitor's revenue). Still mush after two pushes → ❓, or ❌ where `framework.md` names that exact cop-out as weak ("we'll do SEO," "we'll figure out monetization later"). Never 🟡. Quote the mush in the Take. A half-sharp answer (real price, hoped-for retention) scores on its weaker half.
- **Opposite Test for differentiation claims** — wherever they show up (usually the Wedge offer or Moat). Flip the claim. If the opposite is nonsense ("worse UX," "not AI-powered," "bad support"), the claim is fluff — demand the real choice underneath (e.g., "opinionated single workflow vs. flexible everything") before it can score ✅.
- **Threats are present tense.** "A big player *could* enter" is filler. "X launched this feature in March" is a threat. Only present-tense or clearly-likely threats count against Moat.
Warm framing, unmoved bar — attack the claim, never the person.
## Step 4 — Trigger research where needed (optional)
If 2+ dimensions are ❓ unknown, offer the user: *"Want me to run `/deep-research` on [topic] before scoring?"* At 3+ ❓ the framework says research first; if the user declines, write the brief with the ❓s visible — the verdict can't be Build.
Useful research targets:
- Market size / who pays signal → `last30days` skill (if installed) + web search
- Competitive landscape → search for "alternatives to X", "X vs Y" pages
- ICP signal → forums / Reddit / X where the audience hangs out
- Pricing benchmarks → look at competitor pricing pages
If the user says yes, run the `deep-research` skill on the topic and incorporate the brief.
## Step 5 — Check the .com
Always run `/domain` on the working name(s). A perfect idea with a $50k domain is a worse idea than a B+ idea with a free .com.
If naming is wide open, brainstorm 5–10 candidate names through `/domain` and report which are available.
## Step 6 — Output the brief
Use this template:
```markdown
# Business brainstorm: <name or idea slug>
**Date:** <YYYY-MM-DD>
**Idea:** <1–2 sentences>
**Why now:** <1 sentence>
## Verdict
**Build** / **Sleep on it** / **Pass** / **Steal an angle for [existing property]**
<2–3 sentence rationale>
## Score
| Dimension | Take | Verdict |
|---|---|---|
| 1. Problem | … | ✅ |
| 2. Audience | … | 🟡 |
| 3. Wedge | … | ❓ |
| 4. Monetization | … | ✅ |
| 5. Moat | … | ❌ |
| 6. Portfolio fit | … | ✅ |
| 7. Distribution | … | ✅ |
| 8. Energy fit | … | 🟡 |
| 9. Opportunity cost | … | ❌ |
## Domain
- <name>.com — available / taken / aftermarket $<price>
- (other candidates if relevant)
## Research applied
- <link to deep-research brief in ~/.config/makerskills/deep-research/archive/, if run>
## Open questions
- <what would change the verdict>
## If you build it (sketch)
- **First 100 customers:** <how>
- **Wedge offer:** <what>
- **Price:** <range>
- **MVP scope:** <1–3 features>
## If you don't build it
- **Angle to steal for existing properties:**
- Property A: …
- Property B: …
- Property C: …
- (etc., only where relevant)
Archives live in ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/business-brainstorm/archive/ (create the directory if missing). Never write archives inside the skill's own folder — skill installs and upgrades re-sync from source and wipe anything saved there. Migration: if this skill's folder contains an old references/ideas-archive/ with user entries, move those files into the archive directory first.
Finalize the working file at <archive dir>/<YYYY-MM-DD>-<slug>.md (created in Step 3): fill every remaining section and delete the `` line. Then append to <archive dir>/INDEX.md (create if missing):
- 2026-06-16 — [<idea>](./<filename>.md) — **<verdict>** — <one-line rationale>
Show the brief in chat. Tell the user the archive path. Offer:
deep-research — for market validation when dimensions are ❓/domain — for .com availability and naming brainstorm/last30days — for audience/market recency signal (via deep-research)project_*.md) — for portfolio context (don't pitch an idea that already exists)When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not \"marketing ideas for a product\" (that's marketing-skills:marketing-ideas) — t
---name: business-brainstormdescription: When you want to pressure-test a potential new business, product, or side project against the serial-founder…---# skills/business-brainstorm/SKILL.mdОбзор
When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not \"marketing ideas for a product\" (that's marketing-skills:marketing-ideas) — this is \"should this business exist + can you win it.\" Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on \"/business-brainstorm,\" \"/brainstorm,\" \"new business idea,\" \"should I build X,\" \"pressure test this idea,\" \"validate this idea,\" \"is X a good business,\" \"what about a [type] for [audience].\"
FAQ
Скачайте skills/business-brainstorm/SKILL.md у издателя или скопируйте путь и откройте репозиторий. PlugMCP только показывает навык в каталоге и не хранит файл.
Издатель хранит его в https://github.com/coreyhaines31/makerskills.
Claude, Cursor, Codex и Grok Build могут читать SKILL.md, который вы добавляете из репозитория издателя. Grok Bot устанавливает его, когда вы отправляете в чат ссылку на папку навыка на GitHub.