CtrlK
BlogDocsLog inGet started
Tessl Logo

customer-journey-map

Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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, lean instruction set with concrete templates and a clear sequence. It is consistently solid across dimensions but lacks a worked example and explicit validation checkpoints that would push it to the top level.

Suggestions

Add a short filled-in journey-map table example to lift actionability toward a fully worked reference.

Remove the restated intro line and "Think step by step" to tighten conciseness.

Add a brief validation/review checkpoint (e.g., confirm the map covers all stages and ties each pain point to an opportunity) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean and directive without lecturing on concepts Claude already knows, but the opening line restates the description and "Think step by step" is slightly trimmable, fitting anchor 4 rather than 5.

4 / 5

Actionability

Concrete table templates, defined per-stage elements, and a journey-map table with explicit headers give mostly executable guidance; it stops short of anchor 5 by lacking a filled worked example.

4 / 5

Workflow Clarity

A clear six-step sequence (persona, stages, document, critical moments, table, recommendations) is present, but there are no explicit validation checkpoints, so it does not reach anchor 5.

4 / 5

Progressive Disclosure

Well-organized sections (Context, numbered Instructions, Further Reading) with clearly signaled one-level-deep external links; at roughly 60 lines it is just past the simple-skill 5 threshold, so anchor 4 fits best.

4 / 5

Total

16

/

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 clearly states what the skill produces and when to invoke it, with concrete trigger phrases and good keyword coverage. The only soft spot is specificity, where the deliverable components are listed under a single action verb.

DimensionReasoningScore

Specificity

Enumerates concrete deliverable components ("stages, touchpoints, emotions, pain points, and opportunities") but relies on a single verb ("Create"), fitting anchor 4 rather than the multiple-distinct-actions of anchor 5.

4 / 5

Completeness

Explicitly answers both what ("Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities") and when ("Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey") with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Natural trigger phrases like "mapping the customer experience", "identifying friction points", "improving onboarding", and "visualizing the user journey" give good keyword coverage with synonyms, just shy of the exhaustive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Customer journey mapping is a clear niche with distinct triggers, but there is minor overlap risk with broader user/UX research skills, keeping it at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
phuryn/pm-skills
Reviewed

Table of Contents

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.