Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
onewave-ai avatar

Customer Journey Mapper

  • 164 installs
  • 237 repo stars
  • Updated July 15, 2026
  • onewave-ai/claude-skills

Maps and visualizes customer journeys from awareness to purchase, identifying touchpoints, pain points, and opportunities.

About

The customer-journey-mapper skill creates detailed maps of customer experiences from initial awareness through purchase and retention. It identifies key touchpoints, pain points, emotional states, and opportunities for improvement across the customer lifecycle. Valuable for product managers, UX designers, and marketers improving customer experience.

  • Claude Code skill
  • Agent capability extension
  • Developer productivity
  • Workflow automation
  • Easy integration

Customer Journey Mapper by the numbers

  • 164 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #3,201 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/onewave-ai/claude-skills --skill customer-journey-mapper

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs164
repo stars237
Last updatedJuly 15, 2026
Repositoryonewave-ai/claude-skills

What it does

Maps and visualizes customer journeys from awareness to purchase, identifying touchpoints, pain points, and opportunities.

Who is it for?

Product managers and UX designers

Skip if: Non-customer-facing products

What you get

  • customer journey map with insights

Files

SKILL.mdMarkdownGitHub ↗

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

InputDescriptionExample
Product/ServiceWhat is being sold or offered"B2B SaaS project management tool"
Target PersonaWho the primary customer is"VP of Engineering at mid-market companies, 200-1000 employees"
TouchpointsKnown interaction points (optional)"Google search, blog, demo request, sales call, onboarding email sequence"
ChannelsActive 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.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.