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.
83
78%
Does it follow best practices?
Impact
Pending
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 specifies what the skill produces (an end-to-end customer journey map with enumerated components), includes a strong 'Use when' clause with natural trigger terms, and occupies a distinct niche. It follows the third-person voice convention and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities.' This clearly enumerates the specific components and 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'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around customer journey mapping specifically, with distinct trigger terms like 'journey map', 'touchpoints', 'friction points', and 'onboarding' 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 solid instructional skill that provides a comprehensive framework for customer journey mapping with clear stages and documentation requirements. Its main weaknesses are the lack of a concrete example output (even a partial one) and missing validation/feedback steps to ensure the map accurately reflects the user's product. Some explanatory content could be trimmed since Claude already understands concepts like touchpoints and emotions.
Suggestions
Add a brief concrete example showing one stage (e.g., Onboarding) fully filled out in the journey map table format to demonstrate expected output quality and detail level.
Add a validation checkpoint after step 2 (e.g., 'Confirm with the user that these stages match their product's actual customer lifecycle before proceeding to detailed mapping').
Trim the 'For each stage, document' bullet explanations — Claude knows what touchpoints and emotions are; just list the categories without parenthetical definitions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but includes some unnecessary verbosity — the stage description table and the detailed 'For each stage, document' section explain concepts Claude already understands well (what touchpoints are, what emotions mean). The 'Thoughts & questions' examples are helpful but could be trimmed. | 2 / 3 |
Actionability | The skill provides a clear framework and table structure for output, but it's entirely instructional with no concrete example of a completed journey map segment. A brief example showing one stage fully filled out would make this much more actionable and reduce ambiguity about expected output quality. | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically from persona definition through recommendations, but there are no validation checkpoints — no step to verify the journey map with the user, no feedback loop to check if stages are appropriate for the specific product type, and no explicit checkpoint before finalizing recommendations. | 2 / 3 |
Progressive Disclosure | The skill is well-organized with clear sections, appropriate length for a single SKILL.md file, and further reading links are clearly signaled at the end. The content doesn't need to be split across multiple files and the structure supports easy scanning. | 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
36ccefd
- 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.