user-journey-mapper
User Journey Mapper - Auto-activating skill for Visual Content. Triggers on: user journey mapper, user journey mapper Part of the Visual Content skill category.
33
0%
Does it follow best practices?
Impact
97%
1.29xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/user-journey-mapper/SKILL.mdQuality
Discovery
0%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 description is essentially a placeholder with no substantive content. It names the skill and its category but provides zero information about what it does, when to use it, or how it differs from other skills. It would be nearly impossible for Claude to correctly select this skill from a pool of available options.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates visual user journey maps showing touchpoints, pain points, and emotional states across customer interactions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to map a user journey, create a customer experience flow, visualize touchpoints, or diagram a UX flow.'
Include natural keyword variations users might say, such as 'customer journey', 'experience map', 'user flow', 'touchpoint diagram', 'journey visualization', and 'UX mapping'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the skill ('User Journey Mapper') and a category ('Visual Content') but provides no concrete actions. There is no mention of what the skill actually does—no verbs describing capabilities like 'maps user flows', 'creates journey diagrams', or 'visualizes touchpoints'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'user journey mapper' repeated twice. There are no natural variations a user might say, such as 'customer journey', 'user flow', 'touchpoint map', 'experience map', 'journey diagram', or 'UX flow'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Visual Content skill category' could overlap with many other visual/diagramming skills. Without specific actions or distinct triggers, it would be very difficult to distinguish this from other visual or UX-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no substantive content. It contains only generic boilerplate text that describes what the skill would do without actually providing any instructions, code, examples, or actionable guidance for creating user journey maps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples of user journey maps (e.g., Mermaid journey diagram syntax with a complete, copy-paste-ready example)
Define a clear workflow: gather stages → define touchpoints → map emotions → generate diagram → validate output
Include specific tool guidance (e.g., Mermaid journey syntax, PlantUML, or SVG generation) with actual code blocks
Remove all boilerplate sections (When to Use, Example Triggers, Capabilities) and replace with actionable content that teaches Claude how to produce journey maps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'user journey mapper' excessively, and provides zero actual technical content or instructions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no examples of journey map formats, no tool usage, no specific steps. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to detailed files, no structured navigation, and no meaningful content organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
b8a3b3e
- 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.