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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%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 content is a well-structured, actionable instruction skill with a clear sequenced workflow, concrete deliverable templates, and a properly signaled single reference file. It is efficient and mostly lean, with only minor trimming and organization opportunities.

Suggestions

Consider moving the full markdown output-format template into the existing reference file and keeping only a compact skeleton inline, to tighten conciseness and reinforce progressive disclosure.

Add a short validation/maintenance checklist (e.g., what to confirm during the stakeholder workshop and the annual review) to push workflow clarity from a clear sequence to explicit checkpoints.

Trim the five product-type phase code blocks to the two or three most common, referencing the others in the template, to reduce inline reference bulk.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence — no basic-concept lectures, compact lists, and a 'Stack-agnostic. Tool-agnostic.' opener — though the inline output-format markdown template and five product-type phase blocks are slightly more material than strictly necessary inline.	4 / 5
Actionability	Concrete, specific guidance throughout: named journey-map lanes (Phase, Steps, Touchpoints, Goals, Thoughts, Emotions, Pain points, Opportunities), blueprint layers, a copy-paste-ready markdown output template, and a 10-step workflow — minor gaps in execution detail only.	4 / 5
Workflow Clarity	A clearly sequenced 10-step workflow with an explicit validation/refinement loop ('Validate with users. Does this match their actual experience? Refine.'); non-destructive research process so no hard validation cap applies, but it lacks a checklist for the stakeholder workshop and translation-to-action steps.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with a single well-signaled one-level-deep reference ([`references/journey-map-template.md`](references/journey-map-template.md)) confirmed to exist; the bulk of overview content lives inline in SKILL.md, which is appropriate but leaves minor organization room.	4 / 5
	Total	16 / 20 Passed

Description

100%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.

This is a strong, third-person description that clearly states capabilities, provides comprehensive natural trigger terms, and explicitly separates 'what' from 'when'. It carves a distinct niche with minimal overlap risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete deliverables and actions — 'Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems' — covering the full capability surface comprehensively.	5 / 5
Completeness	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...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage with synonyms: 'customer journey, journey map, service blueprint, user journey, experience map, touchpoint analysis, friction map, journey audit, end-to-end experience, customer experience map' — phrases users would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (journey mapping / service blueprinting) with distinct, specialized triggers; the departmental-views clause further narrows the fit, leaving minimal conflict risk with adjacent research skills.	5 / 5
	Total	20 / 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: rampstackco/claude-skills
Path: skills/journey-mapping/SKILL.md
Commit: 0479242

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