customer-journey-map
Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.
66
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./pm-market-research/skills/customer-journey-map/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly defines what the skill produces (end-to-end customer journey maps with specific components) and when to use it (with explicit trigger scenarios). It uses third person voice, includes natural user-facing keywords, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating journey maps with stages, touchpoints, emotions, pain points, and opportunities. These are well-defined deliverables. | 3 / 3 |
Completeness | Clearly answers both what ('Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities') and when ('Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'customer journey map', 'customer experience', 'friction points', 'onboarding', 'user journey', 'touchpoints', 'pain points'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around customer journey mapping specifically, with distinct triggers like 'journey map', 'touchpoints', 'friction points' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent but template-heavy journey mapping skill. Its main strengths are clear organization and logical sequencing of steps. Its weaknesses are the lack of a concrete worked example showing what a completed journey map looks like, some verbosity in explaining concepts Claude already knows, and missing validation/feedback checkpoints in the workflow.
Suggestions
Add a concrete example of a completed journey map row (e.g., for a SaaS product) so Claude has a clear output model to follow rather than just abstract column headers.
Remove or condense the stage description table — Claude already understands what 'Awareness' and 'Retention' mean; instead, just list the stages and focus on what makes this skill's approach distinctive.
Add a validation step after persona definition (e.g., 'Confirm the persona with the user before proceeding') and after the initial map draft (e.g., 'Review for completeness: are all stages covered? Are there gaps in touchpoints?').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but includes some unnecessary verbosity. The stage descriptions table explains concepts Claude already understands (e.g., what 'Awareness' or 'Retention' mean). The 'Thoughts & questions' examples and some framing could be tightened. However, it's not egregiously padded. | 2 / 3 |
Actionability | The skill provides a clear framework and table structure, but it's more of a descriptive template than executable guidance. There are no concrete examples of a completed journey map (e.g., a sample row filled in for a specific product), no example output, and no specific commands or code. It tells Claude what to document but doesn't show a concrete worked example. | 2 / 3 |
Workflow Clarity | The steps are numbered and sequenced logically (define persona → map stages → document details → identify moments → create table → recommend improvements). However, there are no validation checkpoints — no step to verify the map's completeness, no feedback loop to check with the user if the persona is correct before proceeding, and no explicit verification that all stages are covered before finalizing. | 2 / 3 |
Progressive Disclosure | The skill is well-organized with clear sections (Context, Instructions with numbered steps, Further Reading). The Further Reading section provides one-level-deep references that are clearly signaled. For a skill with no bundle files, the structure is appropriate and easy to navigate. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- phuryn/pm-skills
- Commit
d384f0c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.