Startup diagnostic router. An agent skill from getagentseal/founder-playbook.

MITAuto-check passed

Install Diagnose

skills CLI
$ npx skills add getagentseal/founder-playbook --skill diagnose -a claude-code

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

GitHub CLI
$ gh skill install getagentseal/founder-playbook diagnose --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/getagentseal/founder-playbook.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/diagnose .claude/skills/diagnose && 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
diagnose
GitHub stars
724
Token cost
~2.6k tokens
SKILL.md length
872 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Startup diagnostic router. An agent skill from getagentseal/founder-playbook.

  • Works in 5 steps: Do people want this? → Can people understand what you do? → Are the right people finding you? → …
  • SKILL.md covers When to Use This Skill, The Five Failure Modes, The Diagnostic and The One-Skill Rule, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Diagnose is an agent skill from getagentseal/founder-playbook. Startup diagnostic router. Use FIRST when a founder doesn't know where to start, has multiple overlapping problems, or asks a vague question like 'what's wrong with my startup', 'why aren't people buying', 'what should I focus on', 'where do I even begin', 'nothing is working'. Routes to the right framework from the 15 available skills — or tells you when no framework fits and you just need to go talk to people. This is the entry point. Use it before reaching for any specific skill.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 15 proven business books distilled into AI-native skills. Works with Claude Code, ChatGPT, Gemini, Cursor. The licence is MIT.

Example prompts

  • “s wrong with my startup”
  • “why aren”
  • “what should I focus on”
  • “/diagnose”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Do people want this?
  2. Can people understand what you do?
  3. Are the right people finding you?
  4. Are they buying?
  5. Is the sales process working?

What it can do on your machine

Read from SKILL.md and the folder at commit e811e63. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Diagnose loads about 2.6k tokens when it runs. Until then it costs about 124 tokens; SKILL.md has 872 words of instructions outside code blocks.

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

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 getagentseal/founder-playbook at commit e811e63, republished under its MIT licence (© getagentseal). 872 words, ~2,581 tokens.

Download SKILL.mdSave it as .claude/skills/diagnose/SKILL.md (or your agent's skills folder).
name
diagnose
description
Startup diagnostic router. Use FIRST when a founder doesn't know where to start, has multiple overlapping problems, or asks a vague question like 'what's wrong with my startup', 'why aren't people buying', 'what should I focus on', 'where do I even begin', 'nothing is working'. Routes to the right framework from the 15 available skills — or tells you when no framework fits and you just need to go talk to people. This is the entry point. Use it before reaching for any specific skill.

Note: This skill is independent analysis and commentary, not a reproduction of any original text. It synthesizes frameworks from multiple books with modern startup practice and routes founders to the right tool for their situation.

Diagnose

"The dangerous moment is when you apply the right framework to the wrong problem."

When to Use This Skill

Do you know exactly what's broken?
|-- YES --> Do you know which framework to use?
|   |-- YES --> Go use that skill directly. You don't need this.
|   +-- NO  --> THIS SKILL. You know the problem, need the tool.
+-- NO  --> THIS SKILL. Start here.

This skill exists because frameworks are tools, not answers. A hammer doesn't help when the problem is a screw. The first job is diagnosis — figuring out what's actually broken before reaching for any specific framework.


The Five Failure Modes

Every startup problem maps to one of five root causes. Most founders misdiagnose which one they have.

Failure ModeWhat It Looks LikeCommon Misdiagnosis
ProductPeople try it and stop using it"We need better marketing"
MarketCan't find anyone who cares enough to pay"We need to build more features"
MessagingGood product, people don't understand what it does"The product must be wrong"
DistributionPeople would buy it but never hear about it"We need a better website"
PricingPeople want it but won't pay what you charge"We need more features to justify the price"
The Misdiagnosis Problem

Founders almost always misdiagnose their problem by one layer. The pattern:

ACTUAL PROBLEM:        WHAT FOUNDERS THINK:        WHAT THEY DO:
Product problem    →   "Marketing isn't working"   →   Spend on ads (waste)
Market problem     →   "Need more features"        →   Build for months (waste)
Messaging problem  →   "Product must be wrong"     →   Pivot prematurely (waste)
Distribution       →   "Need better website"       →   Redesign 5 times (waste)
Pricing problem    →   "Need more value"            →   Add features nobody asked for (waste)

The Diagnostic

Answer these honestly. Not what you hope is true — what the evidence says.

Step 1: Do people want this?
Have at least 5 people given you real money (or signed a binding LOI)?
|-- YES --> Go to Step 2.
|-- NO  --> Have you talked to 10+ potential customers about their problem
|           (not your solution)?
|   |-- YES --> Did they describe the problem with emotion and specifics?
|   |   |-- YES --> You probably have a messaging, pricing, or distribution
|   |   |           problem. Go to Step 2.
|   |   +-- NO  --> You might have a MARKET problem. The problem you're
|   |               solving may not be painful enough to pay for.
|   |               → Use mom-test to validate the problem exists.
|   |               → Use four-steps Customer Discovery process.
|   +-- NO  --> STOP. You are guessing. Nothing else matters until you
|               talk to real people. → Use mom-test.
Step 2: Can people understand what you do?
Show your website/pitch to a stranger for 5 seconds. Can they tell you:
  1. What you offer?
  2. How it makes their life better?
  3. What they should do next?

All 3 clear?
|-- YES --> Go to Step 3.
|-- NO  --> You have a MESSAGING problem.
|           → Use storybrand to restructure your message.
|           → Use made-to-stick to make individual messages land.
|           → Use obviously-awesome if the confusion is about
|             what category you belong in.
Step 3: Are the right people finding you?
Are potential customers discovering your product?
|-- YES, enough volume → Go to Step 4.
|-- YES, but wrong people → You have a POSITIONING problem.
|   → Use obviously-awesome to redefine your target segment.
|   → Use crossing-the-chasm if you're reaching innovators
|     but need pragmatists.
|-- NO → You have a DISTRIBUTION problem.
|   → Use traction to systematically test channels.
|   → Use 100m-leads for tactical execution in chosen channels.
|   → Use money-models if you can't AFFORD the channels that work (make acquisition self-funding first).
Step 4: Are they buying?
People find you, understand you, but don't buy. Why?
|-- "Too expensive" → PRICING problem.
|   → Use monetizing-innovation to redesign price+product together.
|   → Use 100m-offers to repackage the offer.
|-- "Not sure it'll work for me" → TRUST problem.
|   → Use influence (social proof, authority).
|   → Use storybrand (guide authority + testimonials).
|-- "I'll think about it" (then ghost) → URGENCY problem.
|   → Use 100m-offers (scarcity, urgency, bonuses, guarantees).
|   → Use influence (scarcity, commitment/consistency).
|-- "Went with competitor" → POSITIONING problem.
|   → Use obviously-awesome to find your unique value.
|   → Use blue-ocean-strategy if the market is commoditized.
|-- Signing up but churning → PRODUCT problem.
|   → Use lean-startup to measure and iterate.
|   → Use mom-test to understand why they leave.
|-- Buying once but never again / LTV too low to fund growth → MONEY MODEL problem.
|   → Use money-models (upsells, downsells, continuity).
Step 5: Is the sales process working?
For B2B / high-touch sales:
|-- Meetings happen but deals stall → SALES PROCESS problem.
|   → Use spin-selling for the conversation structure.
|   → Use influence for persuasion mechanics.
|-- Can't get meetings → Back to Step 3 (distribution).
|-- Deals close but take too long → Use spin-selling
|   (you're probably skipping Implication questions).

The One-Skill Rule

Every diagnosis should output: one primary skill, one secondary skill (optional), and one concrete next action the founder can do this week.

Do not stack 3-4 frameworks. Framework stacking creates the illusion of thoroughness while reducing usability. A founder drowning in problems doesn't need four life preservers thrown at once — they need one rope and clear instructions.

If two skills genuinely both apply, sequence them: "Do X first (skill A). Only after you have results, then apply skill B." Never in parallel.

The concrete next action must be something a solo founder can actually do — not "100 outreach attempts per day" but "send 10 DMs to people who posted about this problem on Reddit this week." Precision that sounds good but can't be executed is fake precision.


When No Framework Fits

Sometimes the answer is: none of these frameworks apply to your situation right now.

Signs you should stop using frameworks and just go observe reality:

  • You've been through 3+ frameworks and nothing improved. The problem might not be strategic — it might be execution, team, timing, or market conditions no book anticipated.
  • Your situation is genuinely novel. Frameworks are built from patterns of past companies. If you're doing something with no precedent, the frameworks become educated guesses at best.
  • You're using frameworks to avoid the uncomfortable thing. Usually that's talking to customers, firing someone, admitting the idea doesn't work, or making a decision with incomplete information.
  • The frameworks are contradicting each other and neither side is clearly right. Some tensions are real worldview differences (customer-centric vs product-centric, niche vs broad). You pick one and commit. No rubric resolves that for you.

The meta-rule: Frameworks help you think more clearly. They don't think for you. If you scored a 9/10 on a rubric but your gut says something is off, trust the gut and investigate. The rubric caught the easy problems. The hard ones are yours.


Show full SKILL.md (298 more words)Show less

Quick Reference: Which Skill for What

Your SituationStart WithThen
"Nobody's buying"This diagnostic (figure out WHY)Route to the right skill
"I have an idea but haven't talked to anyone"mom-testfour-steps
"People like it but won't pay"monetizing-innovation100m-offers
"Our website doesn't convert"storybrandmade-to-stick
"We can't find customers"traction100m-leads
"Competitors are eating our lunch"obviously-awesomeblue-ocean-strategy
"Sales calls go nowhere"spin-sellinginfluence
"We have early users but can't grow past them"crossing-the-chasm (only if 10+ paying customers)traction
"Should we pivot?"lean-startupfour-steps
"Everything feels broken"This diagnosticThen one skill at a time
"Customers buy once and disappear"money-models100m-offers
"Ads work but we can't afford to scale them"money-models100m-leads

Scope and Limitations

What This Diagnostic Does
  • Routes you to the right framework faster than guessing
  • Catches the most common misdiagnosis patterns
  • Tells you when to stop using frameworks entirely
What It Doesn't Do
  • It doesn't replace judgment. The diagnostic narrows the options. You still decide.
  • It assumes the 15 available skills cover your problem. Some problems (hiring, fundraising, legal, operations) aren't covered here.
  • It can't diagnose problems you're not honest about. If you skip the hard questions or answer with what you wish were true, the routing breaks.
  • It oversimplifies by design. Real startups have 3 problems at once. This makes you pick one to fix first, which is usually correct but sometimes the problems are entangled and need to be solved together.
The Honest Warning

A diagnostic that always gives an answer is more dangerous than one that sometimes says "I don't know." If your situation doesn't fit any of the decision paths above, that's a signal — not a bug. Go talk to customers, advisors, or anyone who'll give you an honest read on what's happening. Then come back.

© getagentseal, 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 skills/diagnose of getagentseal/founder-playbook.

Open the folder on GitHubat commit e811e63

Compare with similar skills

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

Diagnose compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Diagnose this skillgetagentseal/founder-playbook724—~2.6kAutomated safety check: PassMIT
Idea Refinementaddyosmani/agent-skills103k6 repos~2kAutomated safety check: PassMIT
HTML PPT Studiolewislulu/html-ppt-skill8.6k4 repos~4.7kAutomated safety check: PassMIT
Agent Browserquran/quran.com-frontend-next1.9k42 repos~3.3kAutomated safety check: PassNone
Process Inboxtelegramdesktop/tdesktop33k2 repos~4.5kAutomated safety check: PassGPL-3.0
Brag Launch Videolatent-spaces/brag14k1 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Idea Refinement

    addyosmani/agent-skills

    Guides a conversation that takes a vague idea through divergent and convergent thinking and ends in a markdown one-pager covering scope and assumptions.

    103k GitHub starsUsed in 6 repos~2k tokens
    Agent WorkflowsAuto-check passed
  • HTML PPT Studio

    lewislulu/html-ppt-skill

    Authors static HTML presentations from a library of themes, layouts and animations, with keyboard navigation, for talks, pitch decks and reports.

    8.6k GitHub starsUsed in 4 repos~4.7k tokens
    Documents & OfficeAuto-check passed
  • Agent Browser

    quran/quran.com-frontend-next

    Automates browser interactions for web testing, form filling, screenshots, and data extraction.

    1.9k GitHub starsUsed in 42 repos~3.3k tokens
    Productivity & AutomationAuto-check passed
  • Process Inbox

    telegramdesktop/tdesktop

    Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.

    33k GitHub starsUsed in 2 repos~4.5k tokens
    Productivity & AutomationAuto-check passed
  • Brag Launch Video

    latent-spaces/brag

    Turns the current project website or app into a short, shareable launch video with Hyperframes, planned from the project code with options for tone, format and voiceover.

    14k GitHub starsUsed in 1 repo~2.3k tokens
    Media & CreativeAuto-check passed
  • Perform Task

    telegramdesktop/tdesktop

    Resolve, start or resume, implement, review, test, and publish exactly one existing ai-tdesktop task by short slug or full dated id, including rare blocked retries and split-required results.

    33k GitHub starsUsed in 2 repos~3k tokens
    Productivity & AutomationAuto-check passed

More from getagentseal/founder-playbook

All 16 skills in this repo
  • 100m Leads

    getagentseal/founder-playbook

    Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100.

    724 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed
  • 100m Offers

    getagentseal/founder-playbook

    Designs irresistible Grand Slam Offers using Alex Hormozi's value equation, obstacle-solution mapping, value-cost trim/stack, and offer-naming patterns.

    724 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Blue Ocean Strategy

    getagentseal/founder-playbook

    Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant.

    724 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed
  • Influence

    getagentseal/founder-playbook

    Cialdini's seven principles of compliance (the classic six — reciprocation, commitment-consistency, social proof, liking, authority, scarcity — plus Unity, added 2016) and Pre-Suasion.

    724 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed
  • Lean Startup

    getagentseal/founder-playbook

    Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.

    724 GitHub stars~4.6k tokensUpdated yesterday
    Auto-check passed
  • Made To Stick

    getagentseal/founder-playbook

    Applies the SUCCESs Framework from Made to Stick by Chip Heath and Dan Heath.

    724 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Diagnose

What does Diagnose do?

Startup diagnostic router. An agent skill from getagentseal/founder-playbook. Diagnose is an agent skill from getagentseal/founder-playbook. Startup diagnostic router.

How do I install Diagnose in Claude Code?

Run `npx skills add getagentseal/founder-playbook --skill diagnose -a claude-code`. Or copy the skill folder (skills/diagnose in getagentseal/founder-playbook) into .claude/skills/diagnose in your project. Claude Code loads it when a task matches its description.

How do I install Diagnose in Codex?

Run `npx skills add getagentseal/founder-playbook --skill diagnose -a codex`. Or copy the skill folder (skills/diagnose in getagentseal/founder-playbook) into .agents/skills/diagnose in your project. Codex loads it when a task matches its description.

Can I use Diagnose 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 getagentseal/founder-playbook --skill diagnose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diagnose, .gemini/skills/diagnose, .github/skills/diagnose and .opencode/skills/diagnose in your project.

What does Diagnose need to run?

SKILL.md names no scripts, command-line tools or credentials: Diagnose is instructions for the agent only.

Does Diagnose 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 Diagnose 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 Diagnose use?

Diagnose 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 Diagnose use?

About 2.6k tokens (SKILL.md is roughly 10k 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 Diagnose?

Skills that share tags, products or a category with Diagnose: Idea Refinement (addyosmani/agent-skills, 103k stars), HTML PPT Studio (lewislulu/html-ppt-skill, 8.6k stars), Agent Browser (quran/quran.com-frontend-next, 1.9k stars) and Process Inbox (telegramdesktop/tdesktop, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Diagnose?

getagentseal (a GitHub organization) maintains it in getagentseal/founder-playbook, which has 724 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 6, 2026.

Source: getagentseal/founder-playbook on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.