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.
Startup diagnostic router. An agent skill from getagentseal/founder-playbook.
$ npx skills add getagentseal/founder-playbook --skill diagnose -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getagentseal/founder-playbook diagnose --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "diagnose" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/diagnose into .claude/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/getagentseal/founder-playbook/tree/main/skills/diagnoseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add getagentseal/founder-playbook --skill diagnose -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getagentseal/founder-playbook diagnose --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/diagnose .agents/skills/diagnose && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "diagnose" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/diagnose into .agents/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getagentseal/founder-playbook --skill diagnose -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getagentseal/founder-playbook diagnose --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/diagnose .cursor/skills/diagnose && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "diagnose" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/diagnose into .cursor/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/getagentseal/founder-playbook.git --path skills/diagnose--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getagentseal/founder-playbook --skill diagnose -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getagentseal/founder-playbook diagnose --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/diagnose .gemini/skills/diagnose && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "diagnose" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/diagnose into .gemini/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install getagentseal/founder-playbook diagnoseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add getagentseal/founder-playbook --skill diagnose -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/diagnose .github/skills/diagnose && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "diagnose" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/diagnose into .github/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getagentseal/founder-playbook --skill diagnose -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getagentseal/founder-playbook diagnose --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/diagnose .opencode/skills/diagnose && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "diagnose" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/diagnose into .opencode/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
diagnoseStartup diagnostic router. An agent skill from getagentseal/founder-playbook.
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.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e811e63. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from getagentseal/founder-playbook at commit e811e63, republished under its MIT licence (© getagentseal). 872 words, ~2,581 tokens.
.claude/skills/diagnose/SKILL.md (or your agent's skills folder).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.
"The dangerous moment is when you apply the right framework to the wrong problem."
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.
Every startup problem maps to one of five root causes. Most founders misdiagnose which one they have.
| Failure Mode | What It Looks Like | Common Misdiagnosis |
|---|---|---|
| Product | People try it and stop using it | "We need better marketing" |
| Market | Can't find anyone who cares enough to pay | "We need to build more features" |
| Messaging | Good product, people don't understand what it does | "The product must be wrong" |
| Distribution | People would buy it but never hear about it | "We need a better website" |
| Pricing | People want it but won't pay what you charge | "We need more features to justify the price" |
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)Answer these honestly. Not what you hope is true — what the evidence says.
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.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.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).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).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).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.
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:
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.
| Your Situation | Start With | Then |
|---|---|---|
| "Nobody's buying" | This diagnostic (figure out WHY) | Route to the right skill |
| "I have an idea but haven't talked to anyone" | mom-test | four-steps |
| "People like it but won't pay" | monetizing-innovation | 100m-offers |
| "Our website doesn't convert" | storybrand | made-to-stick |
| "We can't find customers" | traction | 100m-leads |
| "Competitors are eating our lunch" | obviously-awesome | blue-ocean-strategy |
| "Sales calls go nowhere" | spin-selling | influence |
| "We have early users but can't grow past them" | crossing-the-chasm (only if 10+ paying customers) | traction |
| "Should we pivot?" | lean-startup | four-steps |
| "Everything feels broken" | This diagnostic | Then one skill at a time |
| "Customers buy once and disappear" | money-models | 100m-offers |
| "Ads work but we can't afford to scale them" | money-models | 100m-leads |
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
Just SKILL.md in skills/diagnose of getagentseal/founder-playbook.
Open the folder on GitHubat commit e811e63
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Diagnose this skillgetagentseal/founder-playbook | 724 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Idea Refinementaddyosmani/agent-skills | 103k | 6 repos | ~2k | Automated safety check: Pass | MIT | |
| HTML PPT Studiolewislulu/html-ppt-skill | 8.6k | 4 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Agent Browserquran/quran.com-frontend-next | 1.9k | 42 repos | ~3.3k | Automated safety check: Pass | None | |
| Process Inboxtelegramdesktop/tdesktop | 33k | 2 repos | ~4.5k | Automated safety check: Pass | GPL-3.0 | |
| Brag Launch Videolatent-spaces/brag | 14k | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
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.
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.
quran/quran.com-frontend-next
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
telegramdesktop/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
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.
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.
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.
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.
getagentseal/founder-playbook
Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant.
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.
getagentseal/founder-playbook
Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.
getagentseal/founder-playbook
Applies the SUCCESs Framework from Made to Stick by Chip Heath and Dan Heath.
Startup diagnostic router. An agent skill from getagentseal/founder-playbook. Diagnose is an agent skill from getagentseal/founder-playbook. Startup diagnostic router.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Diagnose is instructions for the agent only.
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.
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.
Diagnose is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
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.
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.
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.