Install the "crossing-the-chasm" agent skill from https://github.com/wondelai/skills/tree/main/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.
Type 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.
skills CLI
$ npx skills add wondelai/skills --skill crossing-the-chasm -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "crossing-the-chasm" agent skill from https://github.com/wondelai/skills/tree/main/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.
skills CLI
$ npx skills add wondelai/skills --skill crossing-the-chasm -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "crossing-the-chasm" agent skill from https://github.com/wondelai/skills/tree/main/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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add wondelai/skills --skill crossing-the-chasm -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "crossing-the-chasm" agent skill from https://github.com/wondelai/skills/tree/main/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.
Installs 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).
skills CLI
$ npx skills add wondelai/skills --skill crossing-the-chasm -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "crossing-the-chasm" agent skill from https://github.com/wondelai/skills/tree/main/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.
skills CLI
$ npx skills add wondelai/skills --skill crossing-the-chasm -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "crossing-the-chasm" agent skill from https://github.com/wondelai/skills/tree/main/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.
Facts
Skill name
crossing-the-chasm
GitHub stars
2.4k
Token cost
~3.6k tokens
SKILL.md length
1,640 words
Files
9 (incl. references)
Skills in repo
62
Repo updated
First seen
Licence
MIT
At a glance
Navigate the technology adoption lifecycle from early adopters to mainstream market.
Works in 4 steps: Target the Point of Attack → Assemble the Invasion Force → Define the Battle → …
The user mentions crossing the chasm
SKILL.md covers Core Principle, Scoring, The Technology Adoption Life… and The D-Day Strategy: Crossing…, plus 6 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 wondelai/skills. Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning…
Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `references/b2b-saas.md`, `references/beachhead-selection.md` and `references/buyer-segments.md`).
It sits in Marketing & SEO, covering Go-to-market strategy and Positioning and messaging. The repository describes itself as: Wondel.ai Agent Skills — Business, Marketing, UX & Coding Frameworks from Bestselling Books. 50 skills + 12 guided journeys for Claude Code, Codex, Cursor & other agentskills.io… The licence is MIT.
When your agent uses it
The user mentions crossing the chasm
Beachhead segment
Early adopters vs mainstream
Tech go-to-market
Example prompts
“crossing the chasm”
“beachhead segment”
“whole product”
“/crossing-the-chasm”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c172996. 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
Links to these hosts (documentation or services it may open):
amazon.com
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 3.6k tokens when it runs, and up to ~34k if it reads all its reference files. Until then it costs about 162 tokens; SKILL.md has 1,640 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~162
When it runs· the whole SKILL.md, loaded when a task matches
~3.6k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~34k
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.
Download SKILL.mdSave it as .claude/skills/crossing-the-chasm/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
crossing-the-chasm
description
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.
license
MIT
metadata.author
wondelai
metadata.version
1.4.1
Crossing the Chasm Framework
Strategic framework for marketing and selling disruptive technology products, particularly the transition from early adopters to mainstream customers.
Core Principle
There is a chasm between early adopters and the mainstream market. Most tech companies fail not because they can't build great products, but because they can't cross from visionaries who love new technology to pragmatists who just want solutions that work. The two groups want fundamentally different things -- what wins over innovators actively repels the early majority -- so you must change your strategy, and your whole product, to cross.
If the product is modern PLG/freemium B2B SaaS, read references/b2b-saas.md first -- it remaps every step below (the chasm, beachhead, whole product, metrics) for self-serve trials, free tiers, and the false-signal trap where 1,000 free users looks like a crossing but isn't.
Scoring
Goal: 10/10. Score any tech go-to-market by the Quick Diagnostic at the end: count the rows answered "yes" and map the 7 rows onto a 0-10 scale (roughly 1.4 points per satisfied row).
9-10: single dominable beachhead chosen, 10+ in-segment references, whole product complete via partners, evolution-not-revolution positioning, pragmatist-aligned channel -- adoption is accelerating. You've crossed.
5-6: beachhead picked but whole product or references still thin, or positioning still reads "revolutionary." You're mid-chasm; ship the missing whole-product layers and case studies.
<=3: multiple beachheads (or none), visionary messaging, MVP-grade product. Classic early-market tactics aimed at the mainstream -- the most common reason to stall.
Report the score, name the failing diagnostic rows, and give the fix for each.
The Technology Adoption Life Cycle
Innovators → Early Adopters → [CHASM] → Early Majority → Late Majority → Laggards
2.5% 13.5% 34% 34% 16%
The Chasm: The gap between early adopters (13.5%) and early majority (34%) -- where most tech products die.
The Five Buyer Groups
Segment
% Market
Psychology
What They Buy
What They Need
Innovators
2.5%
Technology enthusiasts
The newest, coolest tech
Product exists, technical specs
Early Adopters
13.5%
Visionaries seeking advantage
Change, revolution, competitive edge
Vision, big potential, strategic value
[THE CHASM]
—
—
—
—
Early Majority
34%
Pragmatists
Productivity improvements
Whole product, references, de-risked
Late Majority
34%
Conservatives
Avoid being left behind
Commodity, support, low risk
Laggards
16%
Skeptics
Only when forced
Cheap, simple, necessary
Critical insight: Early adopters and early majority look similar but want opposite things:
Early Adopters (Visionaries)
Early Majority (Pragmatists)
Want to be first
Want proven solutions
Tolerate bugs and workarounds
Need it to "just work"
Buy the future vision
Buy present value
Need no references
Need references from peers
Want custom solutions, high risk tolerance
Want standards, low risk tolerance
Why this matters: You can't market to both simultaneously -- visionary testimonials scare off pragmatists.
See: references/buyer-segments.md when you need to identify which group a specific prospect belongs to, or to write segment-specific messaging -- it has full psychographics and buying triggers per group.
The reference catch-22: Pragmatists won't buy without references from other pragmatists -- but none exist until someone crosses first. This is why the chasm is a chasm and not a slope: the social proof the early majority requires cannot accumulate gradually. Breaking it is the whole game (Steps 1-2 below).
The D-Day Strategy: Crossing the Chasm
Bad approach: Try to be everything to everyone (stall in the chasm). Good approach: Target a single beachhead, dominate it, expand from a position of strength.
Step 1: Target the Point of Attack
Choose a single, narrowly defined market segment.
Beachhead characteristics: specific ("orthopedic surgical centers with 5-10 surgeons", not "healthcare"); urgent, expensive pain; accessible via known channels; a compelling reason to buy (you're 10x better for their problem); whole-product potential via partners; vocal reference potential.
Criteria
Good Beachhead
Bad Beachhead
Size
Big enough to matter, small enough to dominate
Too small to build on, or too big to own
Pain
Urgent, expensive problem
Nice-to-have
Access
Clear channels to reach
Scattered, hard to reach
Competition
Weak or non-existent
Entrenched incumbents
Word-of-mouth
They talk to each other
Siloed, isolated
Example (Salesforce): not "CRM for all businesses" but "sales force automation for inside sales teams at B2B SaaS startups."
Process: Brainstorm 20+ segments, score each against the criteria, choose ONE (resist keeping options open), commit to dominating it.
See: references/beachhead-selection.md when running the brainstorm-and-score step above -- it has the scoring matrix, weighting, and the target-customer characterization worksheet to pick the one segment.
Step 2: Assemble the Invasion Force
Create the "whole product" for your beachhead segment.
Whole product layers: Generic (what you ship) → Expected (minimum viable) → Augmented (what pragmatists actually need) → Potential (what it could become).
Partnerships: Identify gaps between generic and augmented, partner with companies that fill them, go to market jointly for the beachhead.
See: references/whole-product.md when mapping your gaps -- it extends the layers above with a 12-row gap-analysis matrix, the 80% rule, support-tier SLAs, and a planning canvas.
Step 3: Define the Battle
Position against the competition.
Positioning formula:
For [target customer]
Who [statement of need/opportunity]
Our product is a [product category]
That [statement of key benefit]
Unlike [primary competitive alternative]
Our product [statement of primary differentiation]
Example (early Workday): For mid-market companies who need modern HR and finance systems, Workday is a cloud-based ERP that delivers consumer-grade UX and fast implementation. Unlike Oracle and SAP, it requires no IT infrastructure and deploys in months, not years.
Competitive positioning: The market alternative is often NOT a direct competitor -- it's manual processes, spreadsheets, or legacy systems. Differentiate on a dimension you dominate and make the incumbent's strength irrelevant: Salesforce's "No software" positioning turned feature-rich Siebel's complexity into a weakness.
See: references/positioning.md when filling in the formula above or choosing the competitive alternative to displace -- it has the claim-and-evidence structure and the "make the incumbent's strength irrelevant" patterns.
Show full SKILL.md (644 more words)Show less
Step 4: Launch the Invasion
Execute the go-to-market strategy.
Customer Type
How They Buy
Sales Strategy
Early adopters
Direct, evangelical CEO
Direct sales, founder-led
Early majority
Risk-averse, need proof
Channel partners, references, content marketing
Late majority
Commodity, low-touch
Self-service, inside sales
For crossing (early majority): lead with references and case studies; message whole-product completeness, ease, and low risk; position as evolution ("Better X", not "new category"); prove with ROI calculators, free trials, pilots; sell through channels pragmatists trust (analysts, integrators, consultants).
Messaging shift:
Early Adopter Messaging
Early Majority Messaging
"Revolutionary new approach"
"Proven solution for [problem]"
"Be the first"
"Join 500 companies like yours"
"Change everything"
"Improve [specific metric] by X%"
"Visionary"
"Pragmatic"
See: references/go-to-market.md when building the launch plan -- it details channel selection by buyer type, the reference-and-case-study engine, and pricing/pilot tactics for pragmatists.
Bowling Pin Strategy
After dominating the beachhead, expand to adjacent segments -- each pin knocks down the next: Beachhead → Adjacent #1 → Adjacent #2 → Adjacent #3.
Adjacency criteria: similar needs (whole product transfers), reference credibility (beachhead customers influence the adjacent segment), incremental effort (don't start from scratch).
Example (Salesforce): inside sales at tech startups → inside sales at all B2B companies → all sales teams → customer service → marketing → full CRM platform.
Anti-pattern: Jumping to distant segments before dominating the beachhead.
See: references/expansion.md when sequencing your next 2-3 segments -- adjacency scoring and the bowling-pin ordering rules. For full worked arcs (Salesforce, VMware, Zoom, Atlassian) and stuck-in-the-chasm failures (Palm, Segway), see references/case-studies.md when you need a pattern-match for your own situation.
The Tornado: After the Chasm
Once you cross, demand accelerates (the "tornado"): rapid mainstream adoption, a shift from solution selling to product selling, commodity dynamics, and market-leader consolidation.
Strategic shift: before the chasm -- whole product, customization, high touch; during the tornado -- standardization, scalability, distribution.
Gorilla/chimp/monkey dynamics: the gorilla (market leader, 80%+ share) takes most of the profit; chimps (strong #2-#3) survive in niches; monkeys struggle. Become the gorilla in your beachhead, then expand.
Common Mistakes
Mistake
Why It Fails
Fix
Selling to early majority like early adopters
Wrong messaging, wrong product
Build whole product, emphasize proof
Multiple beachheads
Spread too thin, own nothing
Choose ONE segment, dominate it
Incomplete whole product
Pragmatists won't buy
Partner to fill gaps
"Revolutionary" positioning
Scares off early majority
Frame as evolution, proven solution
Skipping references
No social proof for pragmatists
Invest in case studies, testimonials
Quick Diagnostic
Audit any tech go-to-market, and re-run it as the completion gate before declaring the chasm crossed. Each "If No" is a chasm symptom; act on the failing rows first.
Question
If No
Action
Have we chosen a single, narrowly defined beachhead with an urgent, expensive problem?
You're in the chasm
Define one narrow target market; resist multiple beachheads
Can we plausibly dominate this segment?
Wrong beachhead
Choose a narrower or different segment
Do we have 10+ reference customers from that exact segment?
Pragmatists won't buy
Build lighthouse customers and case studies
Is the whole product complete -- partnerships in place to fill the gaps?
Product won't meet pragmatist needs
Identify generic-to-augmented gaps, partner to fill them
Does positioning emphasize proven value over revolution?
Wrong message for the early majority
Reframe: evolution, not revolution
Is the distribution channel aligned with pragmatist buying behavior?
You reach visionaries, not pragmatists
Sell through analysts, integrators, references, channel
Are adoption metrics accelerating (entering the tornado)?
Still stuck before the chasm
Re-check the rows above -- something is still early-market
Geoffrey A. Moore is a consultant, venture partner, and author whose work at The Chasm Group and Chasm Institute has shaped go-to-market strategy for enterprise technology companies for over 30 years. Crossing the Chasm has sold over a million copies and is required reading at business schools and tech companies worldwide.
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.
Builds or rewrites SaaS landing pages by researching the real product, positioning it against alternatives and writing buyer-focused copy, then implementing it in the codebase.
Builds a full marketing plan for a period, from objectives and segments to channel mix, budget, timeline, KPIs and risks, adapted to the US, EU, SEA or LATAM.
Navigate the technology adoption lifecycle from early adopters to mainstream market. Crossing The Chasm is an agent skill from wondelai/skills. Navigate the technology adoption lifecycle from early adopters to mainstream market.
When should I use Crossing The Chasm?
Crossing The Chasm fits situations like: the user mentions crossing the chasm; beachhead segment; early adopters vs mainstream; tech go-to-market.
How do I install Crossing The Chasm in Claude Code?
Run `npx skills add wondelai/skills --skill crossing-the-chasm -a claude-code`. Or copy the skill folder (crossing-the-chasm in wondelai/skills) 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 wondelai/skills --skill crossing-the-chasm -a codex`. Or copy the skill folder (crossing-the-chasm in wondelai/skills) 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 wondelai/skills --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 names 1 domain. As links in the text: amazon.com. 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 (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Crossing The Chasm use?
About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 31k tokens, read only when the agent opens those files.
What are the alternatives to Crossing The Chasm?
Skills that share tags, products or a category with Crossing The Chasm: Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Design (ferdinandobons/startup-skill, 1.2k stars), Landing Page GTM Copy (ooiyeefei/ccc, 495 stars) and Channel Strategy (TheCraigHewitt/skills, 159 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?
wondelai (a GitHub organization) maintains it in wondelai/skills, which has 2,371 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on September 10, 2026.
Source: wondelai/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.