⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
business-brainstorm
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].\
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
makerskills
AI agent skills for the personal operator's craft. Decisions, research, second-brain workflows, content rotation, scenario modeling, CFO cadence, domain hunts, and the meta-skills to author more.
Built for founders and indie operators. Works with Claude Code, Codex, Cursor, and other Agent Skills hosts.
Site: maker-skills.com
Install
# In Claude Code
/plugin marketplace add coreyhaines31/makerskills
/plugin install makerskills@makerskills
Or symlink for local dev:
git clone https://github.com/coreyhaines31/makerskills ~/code/makerskills
ln -s ~/code/makerskills ~/.claude/plugins/makerskills
See INSTALL.md for env vars, personal-config setup, and runtime dependencies.
Getting started — 5-minute path
New to the plugin? Do these in order. Everything else can wait until you need it.
1. Install the plugin (above), then set the base env var in ~/.zshenv:
export MAKERSKILLS_CONFIG="$HOME/.config/makerskills"
Reload your shell.
2. Run your first skill — start with decide. No config required:
/decide
It'll ask what decision you're facing, pick the right questions from the 37signals framework, and archive the result with a revisit date. That's the first-touch experience: any skill in this plugin. Structured input → structured output → written to disk.
3. Read one SKILL.md to see the pattern:
open ~/code/makerskills/skills/decide/SKILL.md
Each skill is a workflow doc — you can invoke via /decide OR read the SKILL.md and run the steps by hand. The plugin is documentation-first; the automation is a side effect.
4. Try one more skill that involves personal config, so you understand the pattern:
/paste twitter
It'll read your clipboard, strip formatting, warn if over 280 chars, and copy back the cleaned output. First invocation may prompt you to install pbcopy-adjacent deps if missing. No config file needed — this is a pure utility.
5. Now branch out. Skim The 25 skills below and pick one that maps to a workflow you're already doing manually. That's the highest-leverage adoption path.
Which skill do I invoke when?
Routing table for common operator jobs. Match your intent → skill.
| I want to... | Skill |
|---|---|
| Think through a decision with a real fork | decide |
| Break through a wall ("this seems impossible") | unstuck |
| Get a board of famous founders to weigh in | maker-council |
| Pressure-test a new business or product idea | business-brainstorm |
| Research a topic with citations | deep-research |
Find an available .com for a new project | domain |
| Watch known sources daily and feed the good stuff into my brain | radar |
| Capture / query / lint my personal knowledge base | second-brain |
| Same but for a team-shared knowledge base | company-brain |
| Extract notes / highlights / summaries from a book | read-book |
| Extract a transcript or key moments from a video | watch-video |
| Turn a call transcript or client message into issues + reply | ingest |
| Hand a task to Codex / Gemini / another model, or get second opinions from several | castmate |
| Fetch any social post by URL as structured data | social-fetch |
| Plan / draft social content rotation across a portfolio | jab-hook |
| Draft, update, convert, or export a slide deck | slide-deck |
| Clean terminal output for Slack / LinkedIn / X / Notion etc. | paste |
| Manage projects across businesses (kanban) | project-manager |
| Model personal financial scenarios (house, cash flow, etc.) | personal-cfo |
| Run monthly / weekly CFO for a company or agency | company-cfo |
| Plan, build, check, or audit an app (incl. after a new model ships) | product-manager |
| Cut GitHub Actions minutes and CI wait time | ci-audit |
| Create, adapt, or update a skill | skillify |
| Wire up an integration / API / MCP into a project | toolify |
| Set up an agent loop or scheduled task | loopify |
Not sure between two? The skill's SKILL.md description always includes trigger phrases and disambiguation from adjacent skills.
The 25 skills
Meta — extend Claude Code (the -ify trifecta)
| Skill | What |
|---|---|
skillify | Create, adapt, or update a skill in any sibling repo. Three modes: CREATE (from-chat / from-video / from-dump / from-scratch), ADAPT (port external skill with license check + attribution), UPDATE (improve existing skills with cross-skill propagation + semver discipline), TEST (role-play users through a skill and judge transcripts against a rubric). |
toolify | Wire up an integration, API, MCP server, or third-party service into a Next.js or Rails project. Interactive wizard for auth, env vars, client wrapper, webhook handling, and smoke-test. |
loopify | Set up an agent loop, cron-scheduled task, or recurring workflow. Judgment layer on top of ScheduleWakeup / CronCreate / /loop — picks pattern (dynamic / cron / one-shot), tunes delay for cache windows, enforces idempotency + bail-out conditions. |
Decision & strategy
| Skill | What |
|---|---|
decide | 37signals decision framework (38 questions + house additions like Q39 opportunity cost, triaged to 6–8 per decision). Archives with revisit dates. |
business-brainstorm | Pressure-test a new business or product on 9 dimensions. Composes with deep-research + domain. |
domain | 11-step .com domain hunt on Laura Roeder's "availability-first, never fall in love with a name" methodology. Multi-tool ensemble: Vercel CLI + whois (per-TLD) + Domainr API + Namecheap API + rdap.org (modern TLDs) + agent-browser for USPTO trademark screening + aftermarket click-throughs (HugeDomains / Afternic / Sedo / Dan). Handles bare-word + prefix/suffix brainstorming, budget filtering, negotiation guidance, and social handle checks. |
deep-research | Multi-source research with citations + archive. WebSearch, WebFetch, agent-browser, /last30days, memory. |
unstuck | The roadblock antidote. Classifies what kind of "no" you hit (assumption / framing / gatekeeper / tool / resource / physics), runs targeted lateral-thinking techniques from a 10-technique inventory, 10-angle minimum before evaluating. Agents run it on themselves before reporting any dead end. Upstream of decide. |
maker-council | Simulated personal boa |
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/business-brainstorm/SKILL.md6.9 KBupstream ↗
--- name: business-brainstorm description: "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].\"" metadata: version: 0.2.0 --- # /business-brainstorm — Pressure-test a business idea 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). ## Step 1 — Capture the idea Get from the user: - The idea in 1–2 sentences (the *what*) - The reason it's on their mind (the *why now*) - Any starting context (a chat where this came up, a tweet that inspired it, a problem they've hit) If they point at a past chat / doc, load it first. Memory has `project_*.md` files for in-flight projects — check there before assuming the idea is brand-new. If the idea is too vague to score, ask 1–2 clarifying questions and stop. Don't pad the brief with assumptions. ## Step 2 — Load the framework + personal overlay Read `references/framework.md` — the user's filter. Apply each dimension in order. Also try to load `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/business-brainstorm/portfolio.local.md` if it exists — this is where the user lists their real in-flight businesses, properties, audiences, and partners. When present, use it for the "portfolio fit," "distribution," and "opportunity cost" dimensions instead of asking the user to name each one. ## Step 3 — Score each dimension For each of the 9 dimensions in `framework.md`, give a 1-line take + a verdict (✅ strong / 🟡 OK / ❌ weak / ❓ unknown — needs research). Don't BS the unknowns. Mark them ❓ and route to deep-research in Step 4. ## 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?"* Useful research targets: - Market size / who pays signal → `/last30days <space>` + `WebSearch` - 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 `Skill({skill: "deep-research", args: "<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) ``` ## Step 7 — Archive 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. Write to `<archive dir>/<YYYY-MM-DD>-<slug>.md`. Append to `<archive dir>/INDEX.md` (create if missing): ```markdown - 2026-06-16 — [<idea>](./<filename>.md) — **<verdict>** — <one-line rationale> ``` ## Step 8 — Surface Show the brief in chat. Tell the user the archive path. Offer: - *"Want to push to Notion as a positioning canvas?"* - *"Want me to scaffold a project repo / landing page?"* (if verdict = Build) - *"Want me to revisit in 30 days?"* (if verdict = Sleep on it) ## Composes with - `deep-research` — for market validation when dimensions are ❓ - `/domain` — for .com availability and naming brainstorm - `/last30days` — for audience/market recency signal (via deep-research) - Memory (`project_*.md`) — for portfolio context (don't pitch an idea that already exists) ## Notes on quality - **Nine dimensions, not one hero metric.** Ideas fail because one dimension quietly rots even when the rest score high. Force each dimension to be scored — no "we'll figure that out later" cop-outs. - **Verdict discipline: Ship / Sleep on it / Kill.** Not "maybe." Ambiguity in the verdict compounds into ambiguity in the commit; the brief exists to prevent that. - **Portfolio-context check is non-negotiable.** Before writing, grep memory + wiki for existing property overlap. If the new idea is 80% one of your existing properties, propose extending the existing property instead of forking a new one — 4x cheaper to compound. - **Archive every brief, even Kills.** Killed ideas resurface — the brief with rationale prevents re-litigating. The archive dir + INDEX.md makes revisit trivial. - **"Angle to steal" section forces value from Kills.** Even ideas you won't build often have an angle that improves an existing property. Don't skip this section — it's the highest-leverage output of a Kill verdict. - **30-day revisit for "Sleep on it."** Set the calendar reminder. Sleep-on-it ideas that never get revisited become dead weight in the archive; ideas that get revisited resurface with better context.README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/coreyhaines31-makerskills-skills-business-brainstorm.md