Skip to content
SkillModel-led691 tokens in use

Customer Journey Map

Map a persona's path from awareness to advocacy, with touchpoints, emotions, pain points, critical moments and prioritized fixes.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-market-research/skills/customer-journey-map
claude plugin marketplace add phuryn/pm-skills claude plugin install pm-market-research@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Customer Journey Map costs

49tokens idle
691tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure25/25
  • Examples0/15
  • Output0/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

Customer Journey Map has an agent build an end-to-end view of the customer experience for a product. It defines a specific persona with jobs to be done, then walks seven stages from awareness to advocacy.

You can provide interview transcripts, survey data, analytics, support tickets or an existing map, and a product URL for the agent to look up. The result is a markdown document with a journey table and recommended improvements.

What You Get

  • A persona-based journey across seven stages
  • A table of touchpoint, action, emotion, pain point and opportunity per stage
  • The aha moment, decision points and churn triggers
  • Prioritized improvements split into quick wins and deeper investments
  • A markdown base for a visual map in Miro or FigJam

Common Use Cases

  • Finding friction in onboarding
  • Understanding where users drop off before conversion or retention
  • Aligning a team on the whole customer experience

What Makes It Unique

It ties every stage to emotions and to a ranked list of fixes, and names the critical moments in the journey. Persona and segmentation skills in the collection describe who customers are; this one describes what they go through over time.

Under The Hood

The skill is a single instruction file with no scripts. It tells the agent to read any files you supply and to use web search to understand the product when a URL is given. It saves the result as a markdown document. It runs no shell commands and calls no other services.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers