Airweave
CraftOS-dev/CraftBot
Context retrieval layer for AI agents across users' applications.
Applies Geoffrey Moore's chasm-crossing strategy for B2B tech products moving from visionary early adopters to pragmatist mainstream.
$ npx skills add getagentseal/founder-playbook --skill crossing-the-chasm -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getagentseal/founder-playbook crossing-the-chasm --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/crossing-the-chasm .claude/skills/crossing-the-chasm && 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 "crossing-the-chasm" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/crossing-the-chasm into .claude/skills/crossing-the-chasm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crossing-the-chasm", 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/crossing-the-chasmType 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 crossing-the-chasm -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getagentseal/founder-playbook crossing-the-chasm --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/crossing-the-chasm .agents/skills/crossing-the-chasm && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "crossing-the-chasm" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/crossing-the-chasm into .agents/skills/crossing-the-chasm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crossing-the-chasm", 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 crossing-the-chasm -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getagentseal/founder-playbook crossing-the-chasm --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/crossing-the-chasm .cursor/skills/crossing-the-chasm && 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 "crossing-the-chasm" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/crossing-the-chasm into .cursor/skills/crossing-the-chasm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crossing-the-chasm", 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/crossing-the-chasm--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 crossing-the-chasm -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getagentseal/founder-playbook crossing-the-chasm --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/crossing-the-chasm .gemini/skills/crossing-the-chasm && 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 "crossing-the-chasm" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/crossing-the-chasm into .gemini/skills/crossing-the-chasm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crossing-the-chasm", 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 crossing-the-chasmInstalls 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 crossing-the-chasm -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/crossing-the-chasm .github/skills/crossing-the-chasm && 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 "crossing-the-chasm" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/crossing-the-chasm into .github/skills/crossing-the-chasm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crossing-the-chasm", 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 crossing-the-chasm -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 crossing-the-chasm --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/crossing-the-chasm .opencode/skills/crossing-the-chasm && 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 "crossing-the-chasm" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/crossing-the-chasm into .opencode/skills/crossing-the-chasm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crossing-the-chasm", 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.
crossing-the-chasmApplies Geoffrey Moore's chasm-crossing strategy for B2B tech products moving from visionary early adopters to pragmatist mainstream.
Crossing The Chasm is an agent skill from getagentseal/founder-playbook. Applies Geoffrey Moore's chasm-crossing strategy for B2B tech products moving from visionary early adopters to pragmatist mainstream. Use when a product has early traction but stalls before mainstream adoption, when planning a beachhead/niche strategy, when designing whole-product offerings, when positioning against established competitors, or when scaling from innovator usage to industry standard. Triggers include 'stuck between early adopters and mainstream', 'we need a beachhead', 'pragmatist customers won't…
Its SKILL.md is about 5.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `cases.md`, `examples.md` and `frameworks.md`).
It sits in Marketing & SEO. It works with Notion and Slack. 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.
2 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.
Crossing The Chasm loads about 5.5k tokens when it runs. Until then it costs about 198 tokens; SKILL.md has 2,136 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). 2,136 words, ~5,497 tokens.
.claude/skills/crossing-the-chasm/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Note: This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.
"The point of greatest peril in the development of a high-tech market lies in making the transition from an early market dominated by a few visionary customers to a mainstream market dominated by a large block of customers who are predominantly pragmatists in orientation." - Geoffrey Moore
Is your product targeting enterprise buyers (>$10K deals, multi-stakeholder)?
├─ YES → Continue to next question
└─ NO → Pure consumer / PLG / marketplace?
├─ Pure consumer (TikTok, gaming) → SKIP this skill entirely
├─ PLG SaaS (Slack, Notion, Figma) → Use positioning + whole product concepts only; for adoption strategy, see **$100M Leads**
├─ Marketplace (Airbnb-like) → Two-sided dynamics don't map to TALC; use **Blue Ocean Strategy** for market creation
└─ AI-native (Cursor, Claude) → Adoption patterns unprecedented; use **Four Steps to Epiphany** for customer discovery, this skill for enterprise positioning only
Do you have at least 10 paying customers or repeatable early-adopter revenue?
├─ YES → Continue
└─ NO → You're still in Customer Discovery/Validation. Use **four-steps** and **mom-test** first. Come back when you have real traction.
Are you currently in early market (visionaries buying)?
├─ YES → This skill is for you
└─ NO, you're already mainstream → You're past the chasm. Use Inside the Tornado concepts (bowling alley, tornado, main street)
Do you have months/years for strategy execution?
├─ YES → Full framework applies
└─ NO (<6 months runway) → Apply tactical bits (positioning, beachhead) without multi-year choreographyMost tech adoption models show a smooth bell curve. It's a lie. The reality:
EARLY MAINSTREAM
MARKET [ THE CHASM ] MARKET
┌─────────────┐ ┌─────────────────┐
│ Innovators │ ░░░░░░ │ Early Majority │
│ + │ ░ THE ░ │ + │
│ Early │ ░ CHASM░ │ Late Majority │
│ Adopters │ ░░░░░░ │ │
│ ~16% │ │ ~68% │
└─────────────┘ └─────────────────┘The chasm exists because:
| Segment | Approx % | Buying Behavior | Reference Source |
|---|---|---|---|
| Innovators (Tech Enthusiasts) | "very onset, ~3σ from norm" | Pursue tech aggressively | Themselves |
| Early Adopters (Visionaries) | ~13.5% | Buy strategic vision, not products | Their own intuition |
| Early Majority (Pragmatists) | ~34% | Buy productivity improvements; want references | Other pragmatists in same industry |
| Late Majority (Conservatives) | ~34% | Buy established standards; want bundles | Established market leaders |
| Laggards (Skeptics) | ~16% | Don't want tech; only buy when invisible | Cannot be sold to |
| Gap | Between | Cause | Severity |
|---|---|---|---|
| First crack | Innovators ↔ Early Adopters | Tech is cool but no compelling application | Medium |
| THE CHASM | Early Adopters ↔ Early Majority | Visionaries can't reference for pragmatists | CATASTROPHIC |
| Late crack | Early Majority ↔ Late Majority | Product remains too hard for non-competent users | Medium |
Detailed segment profiles: see frameworks.md.
Four characteristics of visionaries that ALIENATE pragmatists:
| Visionary Trait | Why Pragmatists Hate It |
|---|---|
| Lack of respect for colleagues' experience | Pragmatists deeply value peer references |
| More interest in tech than in their own industry | Pragmatists want industry-specific expertise |
| Failing to recognize importance of existing infrastructure | Pragmatists' careers are based on those connections |
| Overall disruptiveness | Visionaries get out before disasters; pragmatists clean up the mess |
The catch-22:
"Cross the chasm by targeting a very specific niche market where you can dominate from the outset, force your competitors out of that market niche, and then use it as a base for broader operations. Concentrate an overwhelmingly superior force on a highly focused target."
| D-Day | Business |
|---|---|
| Eisenhower's Europe | Long-term goal: enter mainstream market |
| The Axis | Entrenched competitor |
| The Allies | Other products and companies needed as invasion force |
| England | Early market base |
| Beaches at Normandy | Strategic target market segment |
| The English Channel | The chasm |
| D-Day | The crossing itself |
| Securing the beachhead | Forcing competitor out of niche |
| Districts of France | Adjacent segments to take next |
| Liberation of Europe | Overall market domination |
| Reason | Mechanism |
|---|---|
| Whole product leverage | Whole-product commitments are expensive; only viable if focused on 1-2 niches |
| Word-of-mouth | Pragmatists communicate vertically; 4-5 wins in ONE segment > 1-2 wins in 5 segments |
| Market leadership | Pragmatists buy from leaders. Need ≥50% share to be the leader. Pick on somebody your own size. |
Pick a beachhead whose adjacent connections create entry into the next segment.
Documentum: Pharma regulatory affairs (40 depts, ~1000 people)
↓
Researchers
↓
Manufacturing floor
↓
Plant construction & maintenance
↓
Regulated chemicals
↓
Oil refineries → Wall Street swapsKnock over the head pin first. Size doesn't matter; pain does. Biggest mistake: choosing a beachhead with no follow-on niches.
Show-stoppers (low score = eliminate):
| Factor | Question |
|---|---|
| Target customer | Single identifiable economic buyer, accessible, well-funded? |
| Compelling reason to buy | Are economic consequences sufficient to mandate fixing this NOW? |
| Whole product | Can we field complete solution within 3 months? |
| Competition | Has someone else already crossed here? Don't attack a fortified hill. |
Nice-to-haves (rank order):
| Factor | Question |
|---|---|
| Partners and allies | Whole-product partner relationships started? |
| Distribution | Sales channel reaches this customer? |
| Pricing | Whole-product price within budget? Channel rewarded? |
| Positioning | Credible as a provider to this niche? |
| Next target customer | Does this niche enable adjacent niches (bowling pin)? |
Critical: Pick ONE beachhead. "You cannot cross the chasm in two places."
Dominate a segment ≤ 2× your annual revenue target. Need to win ≥50% of new orders → de facto standard.
Caveat: This is Moore's heuristic, not a measured rule. Compounds two 50% assumptions. Treat as a sanity check, not a precise calculation.
| Layer | What It Is | PC Example |
|---|---|---|
| Generic | What ships in the box | The PC itself |
| Expected | What customer thought they were buying | Monitor included |
| Augmented | Maximum chance of buying objective | Software, hard drive, printer, training, service |
| Potential | Room for growth | Emerging ancillary products |
80-90% of a whole product is typical in high tech. Pragmatists demand effectively 100%.
This is rhetorical - Moore's actual claim is a gradient, not a hard threshold. But the principle is real: anything significantly less than 100% means customers either supply the rest themselves (visionaries do this; pragmatists don't) or feel cheated, and the market stalls.
In every case, the "winner" had inferior generic product but superior whole product. See frameworks.md for the full Intel/Oracle/Word/HP table.
Full whole-product framework, doughnut diagram, partner management: see frameworks.md.
Pragmatists need to see strong competition. It validates the market.
If you came from visionary success, that competition doesn't exist in pragmatist-recognizable form. You must create it.
You need exactly TWO competitors to triangulate your position:
For (target customer)
Who is dissatisfied with (current market alternative)
Our product is a (new product category)
That provides (key problem-solving capability).
Unlike (the product alternative),
We have assembled (key whole product features for your specific application).6 fill-in-the-blanks producing exactly 2 sentences. That's your positioning statement.
"Can you explain your product in the time it takes to ride up in an elevator?"
If you fail: word-of-mouth can't transmit; marketing scatters; R&D drifts; can't recruit partners; can't get experienced financing.
Examples and the 4 stages of positioning through the lifecycle: see frameworks.md.
"The number-one corporate objective when crossing the chasm is to secure a channel into the mainstream market with which the pragmatist customer will be comfortable. This comes BEFORE revenues, before profits, before press, even before customer satisfaction."
Mantra: Customer-oriented distribution + Distribution-oriented pricing.
Direct sales is the best channel for crossing the chasm. You start the fire - no one else has a vested interest in your sales yet. Only channel responsive to your needs is your own.
After dominating the niche, transition to a more efficient fulfillment channel.
| Segment | Sensitivity | Pricing Strategy |
|---|---|---|
| Visionaries | Low | Value-based (premium for special service) |
| Pragmatists (target) | Medium | Competition-based (~30% premium tolerance for leader)* |
| Conservatives | High | Cost-based (low margin above cost) |
*Moore's heuristic from consulting practice, not measured.
Full distribution channel table (8 channels) and pricing detail: see frameworks.md.
Have you sold to early adopters / visionaries?
├─ NO → You're in early market. Focus there first.
└─ YES → Are pragmatist customers buying?
├─ YES → You've crossed. Focus on bowling alley expansion.
└─ NO → Are you reaching pragmatists at all?
├─ NO → You're in the chasm. Pick a beachhead.
└─ YES, but they reject → Whole product gap. Build it.For each candidate segment, score 1-5 on showstoppers:
- Target customer: identifiable economic buyer?
- Compelling reason to buy: economic consequences mandate action NOW?
- Whole product: deliverable in 3 months?
- Competition: not already fortified?
Any score ≤2 on a showstopper → eliminate
For survivors, rank on nice-to-haves
Pick the WINNER (singular). Pick hard.Is this chasm-crossing or post-chasm?
├─ Chasm-crossing → Direct sales (you start the fire)
└─ Post-chasm → What price point?
├─ <$10K consumer → Retail / Internet
├─ $10K-$75K → No-Man's Land - need niche VARs or transition
└─ >$75K → Direct sales remains| Number | Rule |
|---|---|
| ~16% | Combined % of innovators + early adopters (the early market) |
| ~68% | Combined % of early + late majority (the mainstream) |
| ≥50% | Share of new orders needed in segment to be de facto standard |
| 2x | Maximum segment size relative to your revenue target |
| 30% | Premium pragmatists will pay for the market leader (Moore's heuristic) |
| 80-90% | Typical whole product completeness (inadequate) |
| 100% | Required whole product completeness |
| 20-50 | Number of customer scenarios to develop |
| 8-10 | Distinct alternatives that emerge from those scenarios |
| 3 months | Time-to-deliver whole product cutoff for beachhead viability |
| 15-20% | Max price ratio of partner product to yours (selling partnerships) |
| Pattern | Description | Cure |
|---|---|---|
| High-tech marketing illusion | Believing TALC is smooth | Recognize the gaps, especially the chasm |
| Sales-driven during chasm | Spreading thin across segments | Pick ONE niche. Win it. |
| Hockey stick forecast | Mortgaging future on miracle growth | Use staircase model |
| Spreading whole product thin | Trying to satisfy multiple segments | One segment, complete whole product |
| Wrong reference base | Pitching visionaries to pragmatists | Pragmatist references only |
| Pretending market leadership | Claims without evidence | Real partner ecosystem proves it |
| OEM / Internet for chasm | Wrong channels for demand creation | Direct sales for chasm-crossing |
| Pricing for visionary echo | Charging what visionaries paid | Market leader price + channel premium |
| Not committing to one beachhead | "We're going after multiple segments" | One. Beachhead. Period. |
The framework's core ideas are durable. Specific tactics, channels, and case studies are not.
Full modern-relevance breakdown: see integration.md.
Diagnosing if you're in the chasm:
Picking your beachhead:
Building the whole product:
Defining the battle:
Launching the invasion:
"You start the fire. You spread the fire."
Crossing the chasm is the most dangerous moment in a product's life. Most products die there. The ones that survive don't do it through brilliance - they do it through discipline:
"Cross the chasm by targeting a very specific niche market where you can dominate from the outset."
The opposite of crossing the chasm isn't "moving fast." It's focus.
The framework is durable. The specific examples are dated. Adapt accordingly.
© getagentseal, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files in skills/crossing-the-chasm of getagentseal/founder-playbook.
Open the folder on GitHubat commit e811e63
Crossing The Chasm 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 |
|---|---|---|---|---|---|---|
| Crossing The Chasm this skillgetagentseal/founder-playbook | 729 | — | ~5.5k | Automated safety check: Pass | MIT | |
| AirweaveCraftOS-dev/CraftBot | 392 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Omh Appsrlaope/oh-my-hermes | 3.2k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| ComposioComposioHQ/composio | 30k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Marketing PlanNexus-JPF/note-companion | 870 | 5 repos | ~5.2k | Automated safety check: Pass | MIT |
CraftOS-dev/CraftBot
Context retrieval layer for AI agents across users' applications.
rlaope/oh-my-hermes
[omh] Email, Slack, or Jira action to perform: external app actions - email, Slack, Discord, Notion, Linear, Jira, CRM, and similar providers, scoped with auth, payload, confirmation, and…
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
NVIDIA/NemoClaw
Remove bracketed NemoClaw tags from GitHub issue and PR titles.
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
Startup diagnostic router. An agent skill from getagentseal/founder-playbook.
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.
Categories
Applies Geoffrey Moore's chasm-crossing strategy for B2B tech products moving from visionary early adopters to pragmatist mainstream. Crossing The Chasm is an agent skill from getagentseal/founder-playbook. Applies Geoffrey Moore's chasm-crossing strategy for B2B tech products moving from visionary early adopters to pragmatist mainstream.
Crossing The Chasm fits situations like: A product has early traction but stalls before mainstream adoption; planning a beachhead/niche strategy; designing whole-product offerings; positioning against established competitors.
Run `npx skills add getagentseal/founder-playbook --skill crossing-the-chasm -a claude-code`. Or copy the skill folder (skills/crossing-the-chasm in getagentseal/founder-playbook) into .claude/skills/crossing-the-chasm in your project. Claude Code loads it when a task matches its description.
Run `npx skills add getagentseal/founder-playbook --skill crossing-the-chasm -a codex`. Or copy the skill folder (skills/crossing-the-chasm in getagentseal/founder-playbook) into .agents/skills/crossing-the-chasm 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 crossing-the-chasm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/crossing-the-chasm, .gemini/skills/crossing-the-chasm, .github/skills/crossing-the-chasm and .opencode/skills/crossing-the-chasm in your project.
SKILL.md names no scripts, command-line tools or credentials: Crossing The Chasm 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.
Crossing The Chasm is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.5k tokens (SKILL.md is roughly 22k 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 Crossing The Chasm: Airweave (CraftOS-dev/CraftBot, 392 stars), Omh Apps (rlaope/oh-my-hermes, 3.2k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars) and Composio (ComposioHQ/composio, 30k 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 729 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.