What is customer-journey-map?

A customer journey map shows how a specific type of customer experiences a product, from first awareness to recommending it. It records their actions, contact points, feelings, problems, and possible improvements.

Use it to improve onboarding, understand customer experience, identify problems, and plan product improvements from research such as interviews, surveys, analytics, or support tickets.

It makes friction and drop-off points visible across the whole experience instead of examining each step separately.

customer-journey-map — Skill for Claude Code by unixcrh

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add unixcrh/phuryn-pm-skills --skill customer-journey-map

Clone the repo

git clone --depth 1 https://github.com/unixcrh/phuryn-pm-skills

Made for: Claude Code.

Or install pm-market-research, the plugin that ships this one along with the rest of its 7 skills, 3 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-skills/customer-journey-map/github.svg)](https://agentmods.dev/skills/unixcrh/phuryn-pm-skills/customer-journey-map)

Your own site

<a href="https://agentmods.dev/skills/unixcrh/phuryn-pm-skills/customer-journey-map"><img src="https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-skills/customer-journey-map/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/unixcrh/phuryn-pm-skills/customer-journey-map"><img src="https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-skills/customer-journey-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 753 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00049	$0.00753
Opus 5.5	$0.00020	$0.00301
Sonnet 5.5	$0.00010	$0.00151
Haiku 4.5	$0.00005	$0.00075

Measured 2mo ago against content hash 656c0e16318b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

customer-journey-map scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to customer-journey-map — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

pm-market-research/skills/customer-journey-map/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Customer Journey Map

Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.

Context

You are creating a customer journey map for $ARGUMENTS.

If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.

Instructions

Define the persona: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.

Map the journey stages (adapt to the product):

Stage	Description
Awareness	How do they first learn about the product?
Consideration	What do they evaluate? What alternatives do they compare?
Acquisition	How do they sign up or purchase?
Onboarding	First experience with the product — time to value
Engagement	Regular usage — building habits
Retention	What keeps them coming back? What might cause churn?
Advocacy	When and why do they recommend the product to others?

For each stage, document:
- Touchpoints: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
- User actions: What they do at this stage
- Thoughts & questions: What's on their mind ("Is this worth my time?" "How do I...?")
- Emotions: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
- Pain points: Friction, confusion, drop-off risks
- Opportunities: How to improve the experience at this point
Identify critical moments:
- Aha moment: When the user first experiences core value
- Moments of truth: Decision points where they commit or abandon
- Churn triggers: Where users most commonly drop off
Create the journey map table:

Stage Touchpoint User Action Emotion Pain Point Opportunity

Read the full file on GitHub · 66 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 66 lines · 49 tokens per session scan A 656c0e16318b

Subscribe to this mod's changes

customer-journey-map is a skill published in the GitHub repository unixcrh/phuryn-pm-skills (2 stars, last pushed 8mo ago), licensed MIT. It adds 49 tokens to every session and 753 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to customer-journey-map, differing in 0 lines, and is treated as a copy.

Marketing and SEO

customer-journey-map next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
customer-journey-mapunixcrh/phuryn-pm-skills	Skill	2	8mo ago	MIT	A	49	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code