Crossing the Chasm go-to-market framework
Score and fix a tech product's go-to-market with Moore's chasm framework — beachhead selection, whole product, bowling-pin expansion
- What
- Score and fix a tech product's go-to-market with Moore's chasm framework — beachhead selection, whole product, bowling-pin expansion
- Cost
- Free
- Needs
- a tech product with a go-to-market plan to evaluate; nothing else — strategy framework, no accounts or keys needed
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @wondelai's agent-operable version of Geoffrey Moore's Crossing the Chasm: the core principle that most tech companies die between early adopters (visionaries who buy the future) and the early majority (pragmatists who buy working solutions), so the strategy — and the whole product — must change to cross. It walks through the D-Day strategy step by step: target a single narrow beachhead segment (scored against size, pain urgency, access, competition, word-of-mouth), assemble the invasion force by building the whole product in layers (generic → expected → augmented → potential, with partners filling the gaps), then expand beachhead to beachhead in a bowling-pin sequence, backed by the tornado dynamics, D-Day analogies, positioning-against-incumbents guidance, and a 7-row quick diagnostic that scores any go-to-market 0–10 and prescribes the fix per failing row. Includes a remap for modern PLG/freemium B2B SaaS (self-serve trials, free tiers, the false-signal trap of 1,000 free users) and pointers to a companion `obviously-awesome` skill for positioning and a `blue-ocean-strategy` skill for market creation. Honest caveats: strategy framework, not execution tooling — it diagnoses and prescribes, it does not run campaigns or build the product; based on Moore's classic, adapt examples to your market. MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Crossing the Chasm go-to-market framework is a version of Geoffrey Moore's Crossing the Chasm. Its principle is that most tech companies die between early adopters visionaries and the early majority pragmatists, so strategy and the product must change to cross, walking through the D-Day strategy stepwise, starting with a beachhead segment scored against size, pain urgency, access, competition, and word-of-mouth.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit c172996Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a tech product with a go-to-market plan to evaluate; nothing else — strategy framework, no accounts or keys needed Install "Crossing the Chasm go-to-market framework" for me. It gives the agent @wondelai's agent-operable version of Geoffrey Moore's classic: the innovators → early adopters → [CHASM] → early majority lifecycle, the D-Day strategy (single beachhead selection with scoring criteria, whole-product layering via partners, bowling-pin expansion), tornado dynamics, positioning against incumbents, a 7-row diagnostic scoring any go-to-market 0–10 with per-row fixes, plus the PLG/freemium B2B SaaS remap. MIT-licensed. Repository: https://raw.githubusercontent.com/wondelai/skills/c172996495bed0fcd26896a9416b2093fd7073f0/crossing-the-chasm/SKILL.md Pinned version: install the code at commit c172996495bed0fcd26896a9416b2093fd7073f0 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "crossing-the-chasm". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — describe your product and its market, then ask the agent to score your go-to-market and prescribe fixes). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- c172996 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.