Token导航 LogoToken导航TokenDH.com
运维和基础设施需要联网github未标认证来源可访问许可证需确认审计通过

crossing-the-chasm跨越鸿沟

Agent Skill

crossing-the-chasm 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

29,664

周安装

1,207

GitHub Stars

779

下载量

9,312
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:crossing-the-chasm(跨越鸿沟)
来源仓库:https://github.com/wondelai/skills
仓库路径:skills/crossing-the-chasm
安装命令:
npx skills add https://github.com/wondelai/skills --skill crossing-the-chasm
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/wondelai/skills --skill crossing-the-chasm

简介

crossing-the-chasm 提供从早期采用者过渡到主流市场的战略框架与落地执行指引。

  • 适用于颠覆性技术产品商业化阶段,解决愿景型客户向实用主义客户转化的断层问题。
  • 核心在于重构价值主张以匹配主流市场需求,建立可信赖、易集成的解决方案形象。
  • 实施时应分阶段验证假设,优先打造“灯塔客户”案例以驱动口碑传播与市场渗透。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Crossing the Chasm Framework

Strategic framework for marketing and selling disruptive technology products, particularly for transitioning 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 foundation: Early adopters and mainstream customers want fundamentally different things. What wins over innovators actively repels the early majority. You must change your strategy—and your whole product—to cross the chasm.

Scoring

Goal: 10/10. When evaluating go-to-market strategy for tech products, rate 0-10 based on alignment with chasm-crossing principles. A 10/10 means proper beachhead selection, whole product strategy, and positioning for pragmatist buyers; lower scores indicate early-market tactics applied to mainstream market. Always provide current score and improvements needed to reach 10/10.

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%). This is where most tech products die.

The Five Buyer Groups

Segment% MarketPsychologyWhat They BuyWhat They Need
Innovators2.5%Technology enthusiastsThe newest, coolest techProduct exists, technical specs
Early Adopters13.5%Visionaries seeking advantageChange, revolution, competitive edgeVision, big potential, strategic value
[THE CHASM]
Early Majority34%PragmatistsProductivity improvementsWhole product, references, de-risked
Late Majority34%ConservativesAvoid being left behindCommodity, support, low risk
Laggards16%SkepticsOnly when forcedCheap, simple, necessary

Critical insight: Early adopters and early majority look similar but want completely opposite things.

Early Adopters (Visionaries):

  • Want to be first
  • Willing to work around bugs
  • Buy the future vision
  • Don't need references
  • Want custom solutions
  • High risk tolerance

Early Majority (Pragmatists):

  • Want proven solutions
  • Need it to "just work"
  • Buy present value
  • Need references from peers
  • Want standards
  • Low risk tolerance

Why this matters: You can't market to both simultaneously. Visionary testimonials scare off pragmatists. "Revolutionary" positioning is a red flag to the early majority.

See: references/buyer-segments.md for detailed buyer psychographics.

Why the Chasm Exists

The reference gap:

  • Early majority won't buy without references from other early majority companies
  • But no early majority companies exist until someone crosses first
  • Classic catch-22

The whole product gap:

  • Early adopters tolerate incomplete products
  • Early majority demands complete, integrated solutions
  • Your MVP that wowed visionaries is unshippable to pragmatists

The positioning gap:

  • "Revolutionary" excites early adopters, terrifies early majority
  • "Disruptive" = risky, expensive, unproven
  • Pragmatists want evolution, not revolution

The D-Day Strategy: Crossing the Chasm

Bad approach: Try to be everything to everyone (stall in chasm)

Good approach: Target a single beachhead, dominate it, expand from position of strength.

Step 1: Target the Point of Attack

Choose a single, narrowly defined market segment.

Beachhead characteristics:

  • Specific: Not "healthcare" but "orthopedic surgical centers with 5-10 surgeons"
  • Urgent pain: Problem is costing them real money/time
  • Accessible: You can reach them (conferences, publications, channels)
  • Compelling reason to buy: Your solution is 10x better for their specific problem
  • Whole product potential: You can assemble partners to deliver complete solution
  • Reference potential: They'll be vocal advocates

Target segment criteria:

CriteriaGood BeachheadBad Beachhead
SizeBig enough to matter, small enough to dominateToo small (can't build on) or too big (can't own)
PainUrgent, expensive problemNice-to-have
AccessClear channels to reachScattered, hard to reach
CompetitionWeak or non-existentEntrenched incumbents
Word-of-mouthThey talk to each otherSiloed, isolated

Example: Salesforce

  • Bad: "CRM for all businesses"
  • Good: "Sales force automation for inside sales teams at B2B SaaS startups"

Process:

  1. Brainstorm 20+ possible segments
  2. Score each on criteria above
  3. Choose ONE (resist temptation to keep options open)
  4. Commit to dominating it

See: references/beachhead-selection.md for segment evaluation frameworks.

Step 2: Assemble the Invasion Force

Create the "whole product" for your beachhead segment.

Whole product layers:

Generic Product (what you ship)
    ↓
Expected Product (minimum to be viable)
    ↓
Augmented Product (what pragmatists actually need)
    ↓
Potential Product (what it could become)

Example: Marketing automation software

LayerWhat It Includes
GenericEmail sending, list management
ExpectedTemplates, analytics, API
AugmentedCRM integration, training, support, professional services, best practices playbooks
PotentialAI optimization, advanced personalization, account-based marketing

Critical: Early majority buys the augmented product. If you only deliver generic product, they won't buy.

Whole product checklist:

  • Core technology (your product)
  • Complementary products/services (integrations, partner solutions)
  • Installation and setup (onboarding, migration)
  • Training and support
  • Documentation and best practices
  • Industry-specific adaptations
  • Risk mitigation (security, compliance, SLAs)

Partnerships:

  • Identify gaps between generic and augmented product
  • Partner with companies that fill gaps
  • Joint go-to-market for beachhead segment

See: references/whole-product.md for whole product planning.

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: Workday (early positioning)

  • For mid-market companies
  • Who need modern HR and finance systems
  • Workday is a cloud-based ERP
  • That provides consumer-grade UX and fast implementation
  • Unlike Oracle and SAP
  • Workday requires no IT infrastructure and deploys in months, not years

Competitive positioning:

Identify the market alternative:

  • What do customers use today?
  • Often it's NOT a direct competitor—it's manual processes, spreadsheets, or old systems

Frame the competition:

  • Don't pick fights you can't win
  • Differentiate on dimension you dominate
  • Make their strength irrelevant

Example: Salesforce vs. Siebel

  • Siebel strength: Feature-rich, enterprise-grade
  • Salesforce positioning: "No software" (cloud-based, fast setup)
  • Result: Made Siebel's strength (complexity) a weakness

See: references/positioning.md for competitive positioning frameworks.

Step 4: Launch the Invasion

Execute the go-to-market strategy.

Distribution strategy:

Customer TypeHow They BuySales Strategy
Early adoptersDirect, evangelical CEODirect sales, founder-led
Early majorityRisk-averse, need proofChannel partners, references, content marketing
Late majorityCommodity, low-touchSelf-service, inside sales

For crossing the chasm (early majority):

  • Lead with references: Case studies, testimonials, peer recommendations
  • Whole product messaging: Emphasize completeness, ease, low risk
  • Positioning: Evolutionary, not revolutionary ("Better X" not "New category")
  • Proof: ROI calculators, free trials, pilot programs
  • Channels: Where pragmatists go for advice (analysts, integrators, consultants)

Messaging shift:

Early Adopter MessagingEarly 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 for launch strategies.

Bowling Pin Strategy

After dominating beachhead, expand to adjacent segments.

Beachhead → Adjacent #1 → Adjacent #2 → Adjacent #3
   [Pin]      [Pin]         [Pin]         [Pin]

Adjacency criteria:

  • Similar needs (so whole product transfers)
  • Reference credibility (beachhead customers influence adjacent segment)
  • Incremental effort (don't start from scratch)

Example: Salesforce expansion

  • Beachhead: Inside sales teams at tech startups
  • Pin 2: Inside sales at all B2B companies
  • Pin 3: All sales teams (field sales too)
  • Pin 4: Customer service teams
  • Pin 5: Marketing teams
  • → Full CRM platform

Anti-pattern: Jumping to distant segments before dominating beachhead.

See: references/expansion.md for segment expansion strategies.

The Tornado: After the Chasm

Once you cross the chasm, demand accelerates (the "tornado").

Tornado characteristics:

  • Rapid mainstream adoption
  • Shift from solution selling to product selling
  • Commodity dynamics emerge
  • Market leaders consolidate

Strategic shift in tornado:

  • Before chasm: Whole product, customization, high-touch
  • During tornado: Standardization, scalability, distribution

Gorilla/chimp/monkey dynamics:

  • Gorilla: Market leader (80%+ market share)
  • Chimps: Strong #2 and #3 (niche players)
  • Monkeys: Everyone else (struggling)

Goal: Become the gorilla in your beachhead, then expand.

Common Mistakes

MistakeWhy It FailsFix
Selling to early majority like early adoptersWrong messaging, wrong productBuild whole product, emphasize proof
Multiple beachheadsSpread too thin, own nothingChoose ONE segment, dominate it
Incomplete whole productPragmatists won't buyPartner to fill gaps
"Revolutionary" positioningScares off early majorityFrame as evolution, proven solution
Skipping referencesNo social proof for pragmatistsInvest in case studies, testimonials

Quick Diagnostic

Audit any tech product go-to-market:

QuestionIf NoAction
Have we chosen a single beachhead segment?You're in the chasmDefine narrow target market
Do we have references from that segment?Pragmatists won't buyBuild lighthouse customers
Is the whole product complete?Product won't meet needsIdentify gaps, build partnerships
Does positioning emphasize proven value?Wrong message for early majorityReframe: evolution not revolution
Can we dominate this segment?Wrong beachheadChoose narrower or different segment

Chasm-Crossing Checklist

Before declaring victory:

  • Single, narrowly defined beachhead segment chosen
  • Segment has urgent, expensive problem
  • We can assemble whole product for segment
  • 10+ reference customers from beachhead segment
  • Positioning emphasizes proven value, not revolution
  • Distribution channel aligned with pragmatist buying behavior
  • Partnerships in place to deliver whole product
  • Metrics show adoption accelerating (moving into tornado)

Reference Files

Further Reading

This skill is based on Geoffrey Moore's Crossing the Chasm framework. For the complete methodology:

About the Author

Geoffrey A. Moore is a consultant, venture partner, and author focused on disruptive innovation and market development. His work at The Chasm Group and Chasm Institute has influenced go-to-market strategy for enterprise technology companies for over 30 years. *Crossing the Chasm* has sold over 1 million copies and is required reading at many business schools and tech companies. Moore serves on the boards of several technology companies and advises Fortune 500 firms on technology adoption.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.73%
按下载量换算3,234

Claude

30.51%
按下载量换算2,841

Cursor

20.5%
按下载量换算1,909

Gemini CLI

9.44%
按下载量换算879

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills