customer-journey-map

Create a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow.

Quality

81%

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

62%

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

The body is well-structured with a clear, validated workflow and concrete stage templates, but it is verbose for an instruction skill and leans on bundle files that are not actually present. Tightening the prose and providing the referenced assets would raise the weaker dimensions.

Suggestions

Trim concept re-explanation (stage definitions, "Not a user story map" disclaimers) and remove the verbatim duplication of the frontmatter intent in the Purpose section to improve conciseness.

Create the referenced bundle files (template.md, examples/sample.md, examples/meta-product-manager-skills.md) or remove the dangling references so progressive disclosure and actionability are not undermined.

Move the full per-stage markdown templates and the large worked-example table into template.md/examples, keeping SKILL.md as a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The ~340-line body re-explains concepts Claude already knows (definitions of Awareness/Consideration stages, "Not a user story map") and duplicates the frontmatter intent verbatim; it is structured but could be tightened.	2 / 3
Actionability	Stage templates and a worked example table give concrete guidance, but entries are largely placeholder examples ([Action 1: e.g., ...]) and the referenced executable assets (template.md, examples/sample.md) do not exist, leaving it incomplete.	2 / 3
Workflow Clarity	A clear 7-step sequence (Prepare → Objectives → Persona → Map → Visualize → Analyze → Refine) with per-step quality checks and an explicit validate-with-data feedback loop in Step 7.	3 / 3
Progressive Disclosure	Sections are organized and references are one level deep, but the bulk content is inline rather than split out and the referenced files (template.md, examples/.md, sibling skills//SKILL.md) do not exist in the bundle.	2 / 3
	Total	9 / 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, uses third-person imperative voice, and clearly states both the artifact produced and the triggering situations. It earns full marks across all dimensions with no vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Enumerates concrete dimensions of the artifact — "across stages, touchpoints, actions, emotions, and metrics" — listing multiple specific actions rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("Create a customer journey map across stages, touchpoints, actions, emotions, and metrics") and when ("Use when diagnosing a broken experience or aligning a team on the full customer flow").	3 / 3
Trigger Term Quality	Includes natural phrases a user would say ("diagnosing a broken experience," "aligning a team on the full customer flow," "customer journey map") with good coverage of natural trigger language.	3 / 3
Distinctiveness Conflict Risk	Has a clear niche (customer journey mapping) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/customer-journey-map/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.