CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

customer-journey-mapping-workshop

Run a customer journey mapping workshop with adaptive questions and outputs. Use when you need to map stages, actions, emotions, pain points, and opportunities for a persona and scenario.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/customer-journey-mapping-workshop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured and actionable with a clear question-by-question workflow, but it is token-heavy for an interactive skill and keeps material that belongs in separate reference files inlined. Adding bundle files and trimming full example outputs would meaningfully improve it.

Suggestions

Move the full example journey map, ranked opportunity list, and common pitfalls into a references/ file (e.g. examples.md) and link to it from SKILL.md to improve both conciseness and progressive disclosure.

Tighten the 'What is a Customer Journey Map' and 'Why This Works' sections, which restate concepts Claude already knows, keeping only the NNGroup five-component framing that drives the workflow.

Add an explicit validation/checkpoint step after Q4 (e.g., confirm emotions span highs and lows and every phase has at least one pain point) before generating opportunities, to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient but noticeably long, inlining full example outputs, a five-item ranked opportunity list with evidence, and five common-pitfall entries that could be trimmed or offloaded.

3 / 5

Actionability

Provides concrete agent prompts, four enumerated options per early question, and a complete output template; the later generative steps (Q3-Q5) are slightly less prescriptive, leaving minor gaps.

4 / 5

Workflow Clarity

A clear Step 0 -> Q1-Q5 -> Output sequence with 'Approve or modify' checkpoints at each question, though validation is implicit rather than explicit and the protocol is delegated to an external skill.

4 / 5

Progressive Disclosure

Sectioning is good and the workshop-facilitation reference is clearly signaled one level deep, but no bundle files exist and bulky examples, opportunity lists, and pitfalls are inlined monolithically rather than split into reference files.

3 / 5

Total

14

/

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 the skill's purpose and provides an explicit, concrete trigger clause with natural keywords. It is clearly distinguishable from neighboring discovery skills with only minor overlap risk.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('map stages, actions, emotions, pain points, and opportunities') in third-person voice, with only minor coverage gaps relative to a fully comprehensive action list.

4 / 5

Completeness

Explicitly states both what the skill does ('Run a customer journey mapping workshop with adaptive questions and outputs') and when to use it via a concrete 'Use when...' trigger clause.

5 / 5

Trigger Term Quality

Includes natural phrases a PM would say ('customer journey mapping workshop', 'pain points', 'persona and scenario'), though a few natural synonyms like 'user journey' or 'experience map' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'customer journey mapping workshop' niche is clearly distinct, with only minor overlap risk against related discovery skills such as proto-persona or problem-statement.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (538 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

deanpeters/Product-Manager-Skills

Path

skills/customer-journey-mapping-workshop/SKILL.md

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.