customer-journey-mapping-workshop

Run a customer journey mapping workshop with adaptive questions and outputs. Use when you need to map stages, actions, emotions, pain points, and opportunities for a persona and scenario.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clearly sequenced workshop flow and concrete prompts, templates, and examples. Its weaknesses are verbosity from explaining journey-mapping fundamentals Claude already knows and a monolithic structure with no progressive disclosure into separate reference files.

Suggestions

Trim the "Key Concepts" section (the NNGroup definition, "Why This Works", "Anti-Patterns", and "When to Use / NOT to Use") to only the domain-specific facilitation logic — Claude already knows journey-mapping fundamentals, so this conceptual padding costs tokens without adding guidance.

Move the full output template, the worked examples, and "Common Pitfalls" into separate reference files (e.g. references/journey-map-template.md, references/examples.md) and link to them from SKILL.md so the body serves as a lean overview with one-level-deep references.

Verify the referenced sibling skills resolve at their documented paths (../workshop-facilitation/SKILL.md, customer-journey-map.md, proto-persona.md, discovery-interview-prep.md, opportunity-solution-tree.md, prioritization-advisor.md), since none of these ship as bundle files alongside this skill.

Dimension	Reasoning	Score
Conciseness	The "Key Concepts" block explains fundamentals Claude already knows ("A journey map (NNGroup) visualizes 'the process that a person goes through...'", "Why This Works", "Anti-Patterns", "When to Use This"), so while the facilitation steps are efficient, the body carries unnecessary conceptual padding that could be tightened, fitting the score-2 anchor rather than the lean score-3 case.	2 / 3
Actionability	It gives copy-paste-ready facilitation: exact prompts ("Who is the actor for this journey map?"), four enumerated options per question with concrete examples, a full markdown output template, and worked good/bad examples — concrete and specific rather than the abstract score-1/2 anchors.	3 / 3
Workflow Clarity	The flow is explicitly sequenced (Step 0 → Q1–Q5 → Output) with approve/modify feedback loops after each generation ("Does this capture the customer experience accurately? Should we adjust...?"); this is not a destructive/batch operation, so the missing-validation cap does not apply, meeting the score-3 clear-sequence-with-feedback anchor.	3 / 3
Progressive Disclosure	No bundle files ship in references/scripts/assets, and the body is one ~518-line file with the output template, full examples, and Common Pitfalls all inline; it is well-sectioned (so not the disorganized score-1 case) but content that should be separate is inline and the only references point to sibling skills rather than one-level-deep detail files, matching the score-2 anchor.	2 / 3
	Total	10 / 12 Passed

Description

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.

The description is concise, third-person, and cleanly answers both what the skill does and when to use it with natural trigger terms. It is a strong, low-conflict activation description.

Dimension	Reasoning	Score
Specificity	"Run a customer journey mapping workshop with adaptive questions and outputs" names a concrete action, and "map stages, actions, emotions, pain points, and opportunities for a persona and scenario" enumerates multiple specific elements, matching the anchor that lists several concrete actions rather than the score-2 partial coverage.	3 / 3
Completeness	It states what ("Run a customer journey mapping workshop with adaptive questions and outputs") and gives an explicit when ("Use when you need to map stages, actions, emotions, pain points, and opportunities for a persona and scenario"), satisfying the score-3 requirement of both an explicit what and an explicit trigger; a missing "Use when" clause would have capped this at 2.	3 / 3
Trigger Term Quality	Natural PM vocabulary appears throughout — "customer journey mapping workshop", "pain points", "persona", "scenario", "emotions" — giving good coverage of terms a user would actually say, not jargon, so it clears the score-2 "some relevant keywords" bar.	3 / 3
Distinctiveness Conflict Risk	The journey-mapping-workshop framing plus triggers like "map stages, actions, emotions, pain points" carve a clear niche unlikely to fire for unrelated skills, matching the score-3 distinct-triggers anchor rather than the score-2 "could still overlap" case.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (536 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/customer-journey-mapping-workshop/SKILL.md
Commit: 9971018

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.