journey-mapping

Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the user experience, or visualize touchpoints and pain points. Triggers on customer journey, journey map, service blueprint, user journey, experience map, touchpoint analysis, friction map, journey audit, end-to-end experience, customer experience map. Also triggers when the team has departmental views of users but no shared map of what the experience actually feels like.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-structured, actionable methodology skill with a clear workflow, validation checkpoint, and a properly externalized template reference. The main weakness is conciseness: the inline phase-by-product-type catalog and output template add length that could be trimmed or delegated to the reference file.

Suggestions

Move the five "Common phases by product type" industry progressions (SaaS, Ecommerce, Service, Healthcare) into references/journey-map-template.md, keeping one representative example inline, to reduce body length.

The inline markdown "Output format" template overlaps with the separate references/journey-map-template.md; consolidate them into the reference file and keep only a compact inline example to avoid redundancy.

Tighten "How to gather the inputs" subsections, which restate fairly obvious source categories (interviews, surveys, operational data) and could be compressed without losing guidance value.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of patronizing concept explanations, but the five industry "Common phases by product type" code blocks and the full inline markdown output template are content that could be tightened or moved to the reference file, so not every token earns its place.	2 / 3
Actionability	Concrete, executable guidance throughout: a 10-step workflow, explicit lane/layer definitions for the three deliverables, and a copy-paste-ready markdown output template — fully actionable for an instruction-only skill.	3 / 3
Workflow Clarity	The workflow is a clearly numbered sequence with an explicit validation checkpoint (step 7 "Validate with users... Refine") and a failure-patterns checklist; this is a research/design task, not a destructive or batch operation, so the missing-feedback-loop cap does not apply.	3 / 3
Progressive Disclosure	Well-organized sections with a single clearly-signaled, one-level-deep reference ("references/journey-map-template.md - Fillable journey map and service blueprint template") that exists as a real file; the methodology-vs-fillable-template split is appropriate and navigation is easy.	3 / 3
	Total	11 / 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.

A strong description: third-person voice, concrete deliverables, an explicit "Use when" trigger clause, and a rich set of natural trigger terms with a clear, non-conflicting niche. Minor redundancy between the "Use this skill whenever..." clause and the "Triggers on..." list, but no dimension drops a full point for it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and deliverables — "Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems" — matching the anchor for listing several specific concrete actions rather than vague domain naming.	3 / 3
Completeness	It explicitly answers both what (build journey maps and service blueprints that visualize the experience) and when ("Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction...") with explicit trigger guidance, so it is not capped at 2.	3 / 3
Trigger Term Quality	The "Triggers on customer journey, journey map, service blueprint, user journey, experience map, touchpoint analysis, friction map, journey audit, end-to-end experience, customer experience map" list gives broad coverage of natural terms a user would actually say, beyond a single keyword.	3 / 3
Distinctiveness Conflict Risk	The niche is clear — journey maps and service blueprints with distinct triggers — and unlikely to fire for adjacent skills; the body further disambiguates usability-testing, ux-research, and cro-optimization, reinforcing distinctiveness.	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: rampstackco/claude-skills
Commit: f1bc195

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