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

65%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/customer-journey-map/SKILL.md

Quality

Content

46%Weight 40%Scale 1-5

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 and actionable with a clear 7-step process and worked examples, but it is noticeably verbose and inlines template/example content that should live in the referenced (but missing) bundle files. The dangling references to nonexistent files hurt navigation.

Suggestions

Move the per-stage markdown templates and the full Step 5 visualization table into the referenced template.md and examples/sample.md files, keeping only the framework overview and step sequencing in SKILL.md — this fixes both conciseness and the dangling references.

Create the referenced bundle files (template.md, examples/sample.md, examples/meta-product-manager-skills.md) or remove the references so SKILL.md does not point to nonexistent paths.

Add an explicit validation/verification checkpoint (e.g., 'Verify every stage has actions, touchpoints, emotions, KPIs, and goals before finalizing; fix gaps and re-check') to turn the implicit quality checks into a real feedback loop and raise workflow clarity.

Remove the verbatim restatement of the frontmatter intent in the Purpose section and trim the repeated boilerplate quality-check bullets that explain concepts Claude already knows (e.g., what a KPI is).

Dimension	Reasoning	Score
Conciseness	The ~340-line body restates the frontmatter intent verbatim in Purpose, duplicates per-stage content between the Step 4 templates and the Step 5 table, and repeats boilerplate quality-checks across six fields — noticeably verbose with several padded sections (anchor 2), below the 'mostly efficient' anchor 3.	2 / 5
Actionability	Provides concrete fill-in markdown templates with worked examples (e.g., 'Manager Mike: 35-42...'), a full example table, and specific prioritization criteria — mostly executable guidance with minor gaps, fitting anchor 4 for an instruction-only skill.	4 / 5
Workflow Clarity	A clear 7-step sequence exists with quality checks, but validation is implicit (content-quality criteria) rather than explicit validate->fix->retry feedback loops, and there is no completeness verification before finalizing — anchor 3.	3 / 5
Progressive Disclosure	The body names template.md and examples/*.md but those files are absent from the bundle, and the template/example content that nominally belongs in those files is inlined in SKILL.md — content clearly belonging in separate files is inlined with dangling references (anchor 2).	2 / 5
	Total	11 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 strong: it concisely states what the skill does and gives an explicit 'Use when' trigger with natural phrasing. Its main weakness is keyword coverage, which lacks common synonyms and variations of 'journey map'.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete dimensions ('stages, touchpoints, actions, emotions, and metrics'), listing multiple specific elements rather than only 1-2, but not exhaustive on actions — fits anchor 4.	4 / 5
Completeness	Explicitly answers both what ('Create a customer journey map across stages, touchpoints, actions, emotions, and metrics') and when via a concrete 'Use when...' clause — matches anchor 5, above anchor 4 whose 'when' is only adequate.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a user would say ('diagnosing a broken experience', 'aligning a team on the full customer flow') plus 'customer journey map', but misses common synonyms like 'journey mapping' or 'CX map' — anchor 4.	4 / 5
Distinctiveness Conflict Risk	'Customer journey map' is a distinct niche with specific triggers, but minor overlap risk with closely related workshop skills (story mapping, service blueprint) keeps it at anchor 4 rather than 5.	4 / 5
	Total	17 / 20 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: 1b5a524

Reviewed: 5 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.