Agent skill

Crossing The Chasm

by getagentseal in getagentseal/founder-playbook

Applies Geoffrey Moore's chasm-crossing strategy for B2B tech products moving from visionary early adopters to pragmatist mainstream.

MITAuto-check passedMarketing & SEO

Install Crossing The Chasm

skills CLI
$ npx skills add getagentseal/founder-playbook --skill crossing-the-chasm -a claude-code

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

GitHub CLI
$ gh skill install getagentseal/founder-playbook crossing-the-chasm --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/crossing-the-chasm .claude/skills/crossing-the-chasm && 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
crossing-the-chasm
GitHub stars
729
Token cost
~5.5k tokens
SKILL.md length
2,136 words
Files
5
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Applies Geoffrey Moore's chasm-crossing strategy for B2B tech products moving from visionary early adopters to pragmatist mainstream.

  • Works in 2 steps: Market Alternative → Product Alternative
  • A product has early traction but stalls before mainstream adoption
  • SKILL.md covers Should You Use This Skill?, The Core Insight, The Technology Adoption Life… and Why Visionaries Don't…, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • A product has early traction but stalls before mainstream adoption
  • Planning a beachhead/niche strategy
  • Designing whole-product offerings
  • Positioning against established competitors

Example prompts

  • “stuck between early adopters and mainstream”
  • “we need a beachhead”
  • “pragmatist customers won”
  • “/crossing-the-chasm”

Workflow steps

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

  1. Market Alternative
  2. Product Alternative

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

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.

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

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). 2,136 words, ~5,497 tokens.

Download SKILL.mdSave it as .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.
name
crossing-the-chasm
description
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 buy', 'how do we go from 10 to 1000 customers'. NOT for PLG/freemium SaaS (Slack, Notion, Cursor), pure consumer apps, two-sided marketplaces, or AI-native products with bottoms-up viral adoption - their dynamics break the visionary-to-pragmatist sequence.

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.

Crossing the Chasm

"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

Should You Use This Skill?

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 choreography

The Core Insight

Most 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:

  • Early adopters (visionaries) buy a CHANGE AGENT - they want revolution
  • Early majority (pragmatists) buy a PRODUCTIVITY IMPROVEMENT - they want evolution
  • These motivations are fundamentally incompatible
  • Visionaries are TERRIBLE references for pragmatists (different psychographic)

The Technology Adoption Life Cycle (TALC)

SegmentApprox %Buying BehaviorReference Source
Innovators (Tech Enthusiasts)"very onset, ~3σ from norm"Pursue tech aggressivelyThemselves
Early Adopters (Visionaries)~13.5%Buy strategic vision, not productsTheir own intuition
Early Majority (Pragmatists)~34%Buy productivity improvements; want referencesOther pragmatists in same industry
Late Majority (Conservatives)~34%Buy established standards; want bundlesEstablished market leaders
Laggards (Skeptics)~16%Don't want tech; only buy when invisibleCannot be sold to
There Are 3 Gaps, Not 1 (Including the Chasm)
GapBetweenCauseSeverity
First crackInnovators ↔ Early AdoptersTech is cool but no compelling applicationMedium
THE CHASMEarly Adopters ↔ Early MajorityVisionaries can't reference for pragmatistsCATASTROPHIC
Late crackEarly Majority ↔ Late MajorityProduct remains too hard for non-competent usersMedium

Detailed segment profiles: see frameworks.md.


Why Visionaries Don't Reference Pragmatists

Four characteristics of visionaries that ALIENATE pragmatists:

Visionary TraitWhy Pragmatists Hate It
Lack of respect for colleagues' experiencePragmatists deeply value peer references
More interest in tech than in their own industryPragmatists want industry-specific expertise
Failing to recognize importance of existing infrastructurePragmatists' careers are based on those connections
Overall disruptivenessVisionaries get out before disasters; pragmatists clean up the mess

The catch-22:

  • The only suitable reference for an early-majority customer is another early-majority member
  • No early-majority member will buy without first consulting several references

The D-Day Strategy

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

The Metaphor
D-DayBusiness
Eisenhower's EuropeLong-term goal: enter mainstream market
The AxisEntrenched competitor
The AlliesOther products and companies needed as invasion force
EnglandEarly market base
Beaches at NormandyStrategic target market segment
The English ChannelThe chasm
D-DayThe crossing itself
Securing the beachheadForcing competitor out of niche
Districts of FranceAdjacent segments to take next
Liberation of EuropeOverall market domination
The 3 Reasons Sales-Driven Strategy Is FATAL
ReasonMechanism
Whole product leverageWhole-product commitments are expensive; only viable if focused on 1-2 niches
Word-of-mouthPragmatists communicate vertically; 4-5 wins in ONE segment > 1-2 wins in 5 segments
Market leadershipPragmatists buy from leaders. Need ≥50% share to be the leader. Pick on somebody your own size.
The Bowling Pin Strategy

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 swaps

Knock over the head pin first. Size doesn't matter; pain does. Biggest mistake: choosing a beachhead with no follow-on niches.


Targeting the Beachhead - The 9-Factor Checklist

Show-stoppers (low score = eliminate):

FactorQuestion
Target customerSingle identifiable economic buyer, accessible, well-funded?
Compelling reason to buyAre economic consequences sufficient to mandate fixing this NOW?
Whole productCan we field complete solution within 3 months?
CompetitionHas someone else already crossed here? Don't attack a fortified hill.

Nice-to-haves (rank order):

FactorQuestion
Partners and alliesWhole-product partner relationships started?
DistributionSales channel reaches this customer?
PricingWhole-product price within budget? Channel rewarded?
PositioningCredible as a provider to this niche?
Next target customerDoes this niche enable adjacent niches (bowling pin)?

Critical: Pick ONE beachhead. "You cannot cross the chasm in two places."

Size Math (Heuristic, Not Formula)

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.


The Whole Product (4 Layers - Theodore Levitt's Model)

LayerWhat It IsPC Example
GenericWhat ships in the boxThe PC itself
ExpectedWhat customer thought they were buyingMonitor included
AugmentedMaximum chance of buying objectiveSoftware, hard drive, printer, training, service
PotentialRoom for growthEmerging ancillary products
The Key Rule

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.

Why Pragmatists Pick "Inferior" Products

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.


Define the Battle (Competitive Positioning)

The Counter-Intuitive Truth

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.

The Two Reference Competitors

You need exactly TWO competitors to triangulate your position:

1. Market Alternative
  • Company customer has bought from FOR YEARS
  • Same problem you address
  • The budget you intend to preempt
  • Helps customer identify: target customer (common) + compelling reason to buy (different)
2. Product Alternative
  • Company that's also harnessed a discontinuous innovation
  • Positions itself like you (technology leader)
  • Helps customer appreciate: technology leverage (common) + niche commitment (different)
The Two-Sentence Positioning Formula
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.

The Elevator Test

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


Launch the Invasion (Distribution & Pricing)

The Prime Directive

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

The Critical Rule

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.

Customer Pricing by Segment
SegmentSensitivityPricing Strategy
VisionariesLowValue-based (premium for special service)
Pragmatists (target)MediumCompetition-based (~30% premium tolerance for leader)*
ConservativesHighCost-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.


Decision Trees

"Is my product in the chasm?"
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.
"Which beachhead segment?"
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.
"What channel?"
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

Critical Numbers & Rules of Thumb

NumberRule
~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
2xMaximum 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-50Number of customer scenarios to develop
8-10Distinct alternatives that emerge from those scenarios
3 monthsTime-to-deliver whole product cutoff for beachhead viability
15-20%Max price ratio of partner product to yours (selling partnerships)

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

Common Failure Patterns

PatternDescriptionCure
High-tech marketing illusionBelieving TALC is smoothRecognize the gaps, especially the chasm
Sales-driven during chasmSpreading thin across segmentsPick ONE niche. Win it.
Hockey stick forecastMortgaging future on miracle growthUse staircase model
Spreading whole product thinTrying to satisfy multiple segmentsOne segment, complete whole product
Wrong reference basePitching visionaries to pragmatistsPragmatist references only
Pretending market leadershipClaims without evidenceReal partner ecosystem proves it
OEM / Internet for chasmWrong channels for demand creationDirect sales for chasm-crossing
Pricing for visionary echoCharging what visionaries paidMarket leader price + channel premium
Not committing to one beachhead"We're going after multiple segments"One. Beachhead. Period.

Modern Relevance (1991 → 2026)

The framework's core ideas are durable. Specific tactics, channels, and case studies are not.

When Crossing the Chasm STILL Applies
  • Enterprise software with committee buying ($50K+ deals)
  • Infrastructure plays where IT must approve
  • Categories with high switching costs and risk
  • Disruptive innovations requiring behavior change in conservative industries
  • Hardware and physical products
Where the Framework BREAKS in 2026
  • PLG (Slack, Figma, Notion, Cursor, Linear) - cross the chasm WITHOUT visionary executive sponsorship. Bottoms-up adoption. Breaks Moore's visionary→pragmatist sequence entirely.
  • Open Source as a chasm-crossing tactic (MongoDB, HashiCorp, Hugging Face) - Free distribution gets you into Fortune 500s before any sales conversation. Chasm becomes monetization, not adoption.
  • Network effects products (Slack, Zoom, Discord) - leap chasms via virality. Network effects substitute for whole product.
  • Marketplaces (Airbnb, Uber, DoorDash) - two-sided dynamics don't map to TALC.
  • AI / Foundation models (Cursor, Claude, ChatGPT) - mass adoption preceded enterprise sales. Unprecedented.
  • Pure consumer apps (TikTok, Instagram) - no buyer/payer/user separation; no "early adopter to majority" gap.
What Moore Got Wrong (Now Visible)
  • Internet as "not a chasm-crossing channel" - it now IS the channel for many products
  • Software-only deals at <$10K - now standard SaaS pricing, no longer No-Man's Land
  • Sales cycle assumptions don't match modern velocity (PLG can compress months to days)
  • VARs are largely obsolete; replaced by partners, MSPs, integrators, cloud marketplaces
  • Direct sales force always preferred for chasm - now often a worse choice than self-serve PLG
  • TALC bell curve assumes single market - modern products cross multiple sub-chasms simultaneously

Full modern-relevance breakdown: see integration.md.


Quick Reference Checklist

Diagnosing if you're in the chasm:

  • Visionary customers signed up
  • Pragmatists rejecting / not buying
  • Sales cycles dragging
  • Cash flow reversing after early success
  • Competitors started counterattacking

Picking your beachhead:

  • Single identifiable economic buyer
  • Compelling reason to buy NOW (not "someday")
  • Whole product deliverable in 3 months
  • No fortified competitor already there
  • Bowling pin potential to adjacent segments

Building the whole product:

  • Generic product covers core need
  • Expected product matches what customer assumes
  • Augmented product gives maximum success chance
  • Tactical alliances assembled for missing pieces
  • 100% whole product (not 80-90%)

Defining the battle:

  • Market alternative identified (the budget you preempt)
  • Product alternative identified (the tech leader you triangulate against)
  • Two-sentence positioning written
  • Elevator test passed
  • One attribute owned in customer's mind

Launching the invasion:

  • Direct sales force ready (or transitional channel)
  • Pricing at market-leader level + channel premium
  • "Look at this hot new market" message (not "new product")
  • Financial analyst + vertical media in motion
  • Whole product partners visible

The Big Idea

"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:

  1. Pick ONE beachhead
  2. Build the COMPLETE whole product for it
  3. Position to triangulate market alternative + product alternative
  4. Sell direct to start the fire
  5. Win with discipline, not speed

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


Supporting Files

  • frameworks.md - Detailed segment profiles, application vs platform distinction, target-customer characterization (Day in the Life), sub-segmentation, whole-product layers and management (8 tips), positioning lifecycle (4 stages), distribution channels (8), pricing detail
  • cases.md - Documentum (regulatory affairs beachhead), Lotus Notes (Sheldon Laube/Price Waterhouse 10,000-seat commitment), Microsoft Exception ("Evel Knievel"), Silicon Graphics (Hollywood post-production), Quicken (paper checks/Tobias), Channelpoint (insurance agents), Wang/Lotus/Macintosh/Silicon Graphics death-by-tornado, Steve Jobs/Xerox PARC
  • examples.md - Two-sentence positioning template, 9-factor target selection scoring sheet, doughnut diagram, target-customer characterization (5+3 elements), staircase vs hockey stick model
  • integration.md - Beyond the Chasm (Inside the Tornado: bowling alley, tornado, Main Street), Pioneers vs Settlers org transition, Modern Relevance details, conflicts with Mom Test/Monetizing Innovation/$100M Offers/SPIN Selling

Honest Scope of the Book

  • Published: 1991, revised 1998
  • Examples: Mostly 1990s tech (Lotus 1-2-3, Oracle, AutoCAD, Documentum). Many no longer relevant
  • Empirical base: Anecdotes and case studies. No statistical validation - this is a strategy framework, not a research study
  • Where it shines: B2B enterprise software, infrastructure, complex platforms
  • Where it's weak: Pure consumer apps, low-friction SaaS (PLG works differently), free/freemium products
  • Author's commercial interest: Moore founded The Chasm Group consulting firm

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

Files

SKILL.md and 4 other files in skills/crossing-the-chasm of getagentseal/founder-playbook.

  • SKILL.md
  • cases.md
  • examples.md
  • frameworks.md
  • integration.md

Open the folder on GitHubat commit e811e63

Compare with similar skills

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.

Crossing The Chasm compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Crossing The Chasm this skillgetagentseal/founder-playbook729—~5.5kAutomated safety check: PassMIT
AirweaveCraftOS-dev/CraftBot392—~1.1kAutomated safety check: PassMIT
Omh Appsrlaope/oh-my-hermes3.2k—~1.9kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
ComposioComposioHQ/composio30k1 repos~1.7kAutomated safety check: PassMIT
Marketing PlanNexus-JPF/note-companion8705 repos~5.2kAutomated safety check: PassMIT

Similar skills

  • Airweave

    CraftOS-dev/CraftBot

    Context retrieval layer for AI agents across users' applications.

    392 GitHub stars~1.1k tokensUpdated today
    Sales & SupportAuto-check passed
  • Omh Apps

    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…

    3.2k GitHub stars~1.9k tokensUpdated today
    Sales & SupportAuto-check passed
  • Official

    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.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Composio

    ComposioHQ/composio

    Route and complete Composio work across Composio For You and Composio Platform.

    30k GitHub starsUsed in 1 repo~1.7k tokens
    Productivity & AutomationAuto-check passed
  • Marketing Plan

    Nexus-JPF/note-companion

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

    870 GitHub starsUsed in 5 repos~5.2k tokens
    Marketing & SEOAuto-check passed
  • Remove bracketed NemoClaw tags from GitHub issue and PR titles.

    23k GitHub stars~693 tokensUpdated today
    Marketing & SEOAuto-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.

    729 GitHub stars~2.3k tokensUpdated 2 days ago
    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.

    729 GitHub stars~2.7k tokensUpdated 2 days ago
    Auto-check passed
  • Blue Ocean Strategy

    getagentseal/founder-playbook

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

    729 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed
  • Diagnose

    getagentseal/founder-playbook

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

    729 GitHub stars~2.6k tokensUpdated 2 days ago
    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.

    729 GitHub stars~3.8k tokensUpdated 2 days ago
    Auto-check passed
  • Lean Startup

    getagentseal/founder-playbook

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

    729 GitHub stars~4.6k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Crossing The Chasm

What does Crossing The Chasm do?

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.

When should I use Crossing The Chasm?

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.

How do I install Crossing The Chasm in Claude Code?

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.

How do I install Crossing The Chasm in Codex?

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.

Can I use Crossing The Chasm 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 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.

What does Crossing The Chasm need to run?

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

Does Crossing The Chasm 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 Crossing The Chasm 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 Crossing The Chasm use?

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.

How many tokens does Crossing The Chasm use?

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.

What are the alternatives to Crossing The Chasm?

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.

Who maintains Crossing The Chasm?

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.