by emotixco
Claude Code skills for startup founders — product briefs, competitor analysis, pricing strategy, pitch decks, and GTM plans from your terminal
# Add to your Claude Code skills
git clone https://github.com/emotixco/claude-skills-founderGuides for using cli tools skills like claude-skills-founder.
Last scanned: 10/8/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-10-08T11:09:20.741Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how claude-skills-founder compares with popular alternatives.
claude-skills-founder is an open-source cli tools skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by emotixco. Claude Code skills for startup founders — product briefs, competitor analysis, pricing strategy, pitch decks, and GTM plans from your terminal. It has 905 GitHub stars.
Yes. claude-skills-founder passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/emotixco/claude-skills-founder" and add it to your Claude Code skills directory (see the Installation section above).
claude-skills-founder is primarily written in Markdown. It is open-source under emotixco on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other CLI Tools skills you can browse and compare side by side. Open the CLI Tools category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh claude-skills-founder against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
See comparison
Startup strategy from your terminal. Not another dev tool.
Skills · Install · Usage · Examples · Philosophy · Contributing
[!NOTE] Most Claude Code skill packs are developer tools: code review, git workflows, security audits. This one is for the founder sitting in a repo at 2am, trying to figure out if their idea is worth building.
We built these at Emotix while running our own startup. They encode the frameworks, questions, and patterns we wish we had on day one.
See it work before you install anything. examples/ holds five ideas run end to end, with every file the runs produced and nothing edited, including the one the skills told us to kill. evals/ measures the skills against plain Claude and publishes where they make no difference.
| Command | What it does |
|---|---|
/validate-idea |
Stress-test with 7-dimension scorecard |
/product-brief |
Structured brief from one sentence |
/competitor-matrix |
Feature comparison + positioning gaps |
/persona-gen |
3 personas with priority matrix |
/user-interviews |
Mom Test script + analysis framework |
| Command | What it does |
|---|---|
/mvp-scope |
Ruthless feature triage |
/pricing-strategy |
Tiers, unit economics, psychology |
/go-to-market |
Pre-launch to 90-day growth plan |
/landing-page |
Conversion copy, section by section |
/email-sequence |
Onboarding emails, ready to send |
| Command | What it does |
|---|---|
/pitch-deck |
12-slide outline with per-slide content |
/fundraise-prep |
Readiness assessment + investor targeting + 12-week timeline |
/metrics-dashboard |
The 5 metrics that actually matter at your stage |
/status |
Where the company stands, read back from the founder/ folder |
Every skill takes plain-language input and returns scorecards, tables, and checklists you can act on.
Each skill saves its output to a founder/ folder in your project and reads what earlier skills saved. Run /founder:competitor-matrix once, and /founder:pricing-strategy and /founder:pitch-deck reuse its sourced competitor prices instead of starting over.
founder/
├── facts.md # what you told the skills: stage, metrics, team, the raise
├── validate-idea.md
├── competitor-matrix.md
├── pricing-strategy.md
└── ...
Commit the folder to keep a history of how your thinking changed, or add it to .gitignore to keep it private.
Facts about the outside world, such as competitor prices, funding rounds, market sizes, and benchmarks, come with a source link. When a skill can't find one, it says "Estimate" or "Not found" instead of guessing. Your own metrics, customer quotes, and testimonials are never invented: missing ones show up as [placeholders] for you to fill in.
Inside Claude Code:
/plugin marketplace add emotixco/claude-skills-founder
/plugin install founder@emotix
Skills become available as /founder:validate-idea, /founder:pricing-strategy, and so on. Update later with /plugin marketplace update emotix. The skill descriptions add about 1,100 tokens to each session. A skill's full instructions load only when you run it.
git clone https://github.com/emotixco/claude-skills-founder.git ~/.claude/skills/founder
Claude Code loads the folder as a plugin on the next session, with the same /founder: names. To update:
git -C ~/.claude/skills/founder pull
v1 installed flat files into .claude/commands/founder/. Delete that folder (or the symlink, if you used the v1 symlink option) before installing v2, or you will see every skill twice. It is either ~/.claude/commands/founder or .claude/commands/founder inside the project where you installed it.
Open Claude Code and type any skill with your context:
> /founder:validate-idea An AI tool that analyzes pitch decks and gives investor-perspective feedback
> /founder:competitor-matrix Project management tools for solo founders (not teams)
> /founder:pricing-strategy B2B SaaS for restaurant inventory, targeting independent restaurants with 1-3 locations
> /founder:pitch-deck Pre-seed raise, $500K, AI competitor analysis for founders, 200 beta users, $2K MRR
Later, when the folder has something in it:
> /founder:status
Run a skill with no input and it asks for what it needs.
[!IMPORTANT] If an install step fails or a skill invents a number, that's a bug and we want to hear it. Open an issue with your
claude --versionand what you ran. A broken install is silent otherwise: people try it once and leave.
[!TIP] Be as specific as possible. Include your stage, metrics, constraints, and what you've already tried. Facts you give once are saved to
founder/facts.md, so you don't have to repeat them.
examples/ has five ideas run end to end, with every file the runs produced and nothing edited: a UK physiotherapy SaaS, an office coffee subscription in Baku, a solo developer's puzzle game, a restaurant inventory tool, and one idea the skills told us to kill. Each one lists what it cost and which of its cited links are dead. Read it before installing to see what you get.
evals/ tests the plugin against plain Claude with claude plugin eval, and evals/benchmark.md carries the scheduled re-runs, including the cases where the plugin loses. The honest summary, measured on 2026-10-07 across the 10 cases the suite held then: on Opus 5, 8 of those 10 scored the same with and without the plugin, because the model already keeps the placeholders and reads the saved files on its own. The exception is what happens when a new number contradicts a saved one: only the plugin updates founder/facts.md, so the next session doesn't inherit the stale figure. On Haiku 4.5 the plugin scored higher on 3 of the 10, the skills often need calling by name, and the shared rules file goes unread, so most of these rules never reach a Haiku session. Full numbers, including per-run cost, are in evals/README.md.
Scores your idea on 7 dimensions (problem severity, market size, willingness to pay, competition gap, distribution, timing, founder fit) and gives a verdict: build, pivot, or kill.
Includes 3 specific validation experiments you can run in under 2 weeks for under $200.
Turns a one-sentence idea into a structured brief: problem statement, target audience with personas, value proposition, MVP features (exactly 5-7), success metrics with 90-day targets, risk assessment, and GTM snapshot.
Researches 5-8 competitors on the web and builds a feature comparison table, with a source link for every price and funding round. Finds positioning gaps no one is filling, ranks threats, and recommends a niche to own.
Creates 3 distinct personas with a day in the life, pain points written the way they would say them, current workarounds, and buying behavior. Includes a priority matrix showing which persona to build for first. Personas are marked as hypotheses until interviews confirm them.
Takes your feature wishlist and triages into Must Have / Should Have / Wo