customer-journey-mapper — Claude Code skill: setup and features
customer-journey-mapper generates an exhaustive customer journey document in customer-journey.md with seven lifecycle stages, Mermaid diagrams, and metrics.
MIT 257 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill customer-journey-mapper -a claude-codeWhat customer-journey-mapper does
The skill takes your product details, persona, and channels, then queries web search to examine real customer complaints, reviews, and competitor benchmarks. It breaks the journey into seven distinct phases from initial awareness to advocacy, charting pain points, emotional changes, and measurable key indicators.
Every run writes directly to customer-journey.md in the current working directory. The output enforces strict structural rules: at least 400 lines of markdown, two renderable Mermaid diagrams, concrete metrics with measurement methods, and zero emojis.
What it helps with
- Map every touchpoint from first user contact to product advocacy
- Spot drop-off risks between onboarding and long-term retention
- Generate valid Mermaid journey diagrams directly inside markdown files
- Establish measurable tracking criteria across each funnel stage
Example prompts for the agent
- Map the customer journey for a B2B project management platform targeting engineering leads
- Create a customer journey map for a fitness service using organic search and email
- Analyze retention friction and build Mermaid diagrams in
customer-journey.md
How to install customer-journey-mapper
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-journey-mapper -a claude-code2Manually: put the files in place
~/.claude/skills/customer-journey-mapper/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/customer-journey-mapper/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-journey-mapper -a codex2Manually: put the files in place
.agents/skills/customer-journey-mapper/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-journey-mapper -a cursor2Manually: put the files in place
.cursor/skills/customer-journey-mapper/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills customer-journey-mapper2Manually: put the files in place
.github/skills/customer-journey-mapper/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-journey-mapper -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path customer-journey-mapperManually: put the files in place
.devin/skills/customer-journey-mapper/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-journey-mapper -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about customer-journey-mapper
How to install customer-journey-mapper in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill customer-journey-mapper -a claude-code in your terminal. You can also place the configuration file directly at ~/.claude/skills/customer-journey-mapper/SKILL.md.
What does customer-journey-mapper do?
It conducts market research using search tools and writes a structured customer-journey.md covering seven lifecycle phases, friction points, and Mermaid visual diagrams.
What inputs are required to run this skill?
You need to supply the product or service along with the primary target persona. Channels and touchpoints are optional; if omitted, the skill infers them and notes its assumptions.
Source text
SKILL.md · MIT
--- name: customer-journey-mapper description: Maps the full customer journey from first touch to advocacy. Generates a comprehensive customer-journey.md with all stages, touchpoints, emotions, pain points, opportunities, Mermaid diagrams, and metrics. Use when mapping customer experience, designing onboarding flows, identifying churn risks, or optimizing conversion funnels. tools: Read, Write, Edit, Glob, Grep, Bash, WebSearch, WebFetch model: inherit --- # Customer Journey Mapper Produce a comprehensive, actionable customer journey map spanning every stage from initial awareness through long-term advocacy. ## Contents - `references/journey-stages.md` — the seven stages and the dimensions to analyze for each - `references/output-template.md` — exact structure for the generated `customer-journey.md` - `references/mermaid-diagrams.md` — both required Mermaid diagrams and the satisfaction scoring guide - `references/examples.md` — invocation examples, research protocol, and ambiguity handling ## Workflow 1. **Collect inputs.** Gather Product/Service, Target Persona, Touchpoints (optional), and Channels. When any are missing, infer reasonable values and document the assumptions at the top of the output. Ask one clarifying question only when the product type is genuinely unclear. 2. **Research context.** Use WebSearch to ground the map in real reviews, complaints, competitor comparisons, and industry patterns. See `references/examples.md` for the research protocol. 3. **Map all seven stages.** Build a detailed stage-by-stage analysis covering Awareness, Consideration, Decision, Onboarding, Retention, Expansion, and Advocacy. See `references/journey-stages.md` for the dimensions to cover per stage. 4. **Identify opportunities.** Surface pain points, emotional states, and improvement opportunities at every stage. Include honest friction even in generally positive stages, and cross-reference how one stage's issues create downstream effects. 5. **Generate the deliverable.** Write `customer-journey.md` to the current working directory following `references/output-template.md`. Include both Mermaid diagrams per `references/mermaid-diagrams.md`. ## Required Inputs | Input | Description | Example | |---|---|---| | **Product/Service** | What is being sold or offered | "B2B SaaS project management tool" | | **Target Persona** | Who the primary customer is | "VP of Engineering at mid-market companies, 200-1000 employees" | | **Touchpoints** | Known interaction points (optional) | "Google search, blog, demo request, sales call, onboarding email sequence" | | **Channels** | Active marketing/sales/support channels | "Website, email, LinkedIn, phone, in-app, Slack community" | ## Quality Requirements 1. **Minimum 400 lines** of substantive content, not padded whitespace. 2. **Specificity**: Tie every touchpoint, pain point, and opportunity to the given product and persona — no generic filler. 3. **Actionability**: Make recommendations concrete enough to begin implementation immediately. 4. **Measurable metrics**: State how each metric is actually measured, not just what to measure. 5. **Emotional realism**: Reflect genuine customer psychology, not idealized happy paths. 6. **Honest pain points**: Include real friction even in positive stages. 7. **No emojis** anywhere in the output document. 8. **Mermaid validity**: Use valid syntax that renders correctly. 9. **Consistent voice**: Keep professional, strategic language throughout — a working document for product and marketing teams. 10. **Cross-references**: Connect each stage's issues to their downstream effects.
© OneWave-AI · MIT · OneWave-AI/claude-skills