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.
68
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 uses proper third-person voice 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 components and deliverables of the skill. | 3 / 3 |
Completeness | Clearly answers both 'what' (create a customer journey map with stages, touchpoints, emotions, pain points, and opportunities) and 'when' (explicit 'Use when' clause covering mapping 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 phrase requests in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | The description targets a clear niche—customer journey mapping—with distinct trigger terms like 'journey map', 'touchpoints', 'friction points', and 'onboarding'. This is unlikely to conflict with other skills unless there's a very similar UX-focused skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured analytical skill with a clear multi-step workflow for creating customer journey maps. Its main weaknesses are the lack of a concrete output example (even a partial one showing one completed stage) and some verbosity in explaining concepts Claude already knows. The workflow sequencing is strong, but actionability would benefit significantly from a worked example.
Suggestions
Add a brief concrete example showing one fully completed journey stage (e.g., 'Onboarding' for a SaaS product) to demonstrate expected output quality and detail level.
Trim the stage description table — Claude understands what 'Awareness' and 'Retention' mean; replace with just the stage names and any non-obvious nuances specific to this skill's approach.
Consider adding a brief example of the final journey map table with 2-3 rows filled in to make the expected output format unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but includes some unnecessary elaboration. The stage descriptions table explains concepts Claude already understands (e.g., what 'Awareness' or 'Retention' mean). The 'Thoughts & questions' examples and some descriptive text could be trimmed. | 2 / 3 |
Actionability | The skill provides a clear framework and structured tables 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 | The six-step process is clearly sequenced from persona definition through stage mapping, documentation, critical moment identification, table creation, and prioritized recommendations. For a non-destructive analytical task like this, the workflow is well-ordered and unambiguous without needing validation checkpoints. | 3 / 3 |
Progressive Disclosure | The Further Reading section provides useful external references, but all content is inline in a single file. The stage descriptions table and the detailed 'for each stage' documentation criteria could potentially be split out for a cleaner overview. However, the content length is moderate enough that this is a minor issue. | 2 / 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
020ee82
- 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.