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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill user-journey-mapper36
Quality
3%
Does it follow best practices?
Impact
97%
1.29xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/user-journey-mapper/SKILL.mdDiscovery
7%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 that provides almost no useful information for skill selection. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use it. The repeated trigger term and generic category reference suggest this was auto-generated without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Creates visual user journey maps showing customer touchpoints, pain points, and emotional states across service interactions'
Include a proper 'Use when...' clause with natural trigger terms like 'Use when the user asks to map customer journeys, visualize user flows, create experience maps, or analyze touchpoints'
Add varied trigger terms users would naturally say: 'customer journey', 'user flow', 'experience map', 'touchpoint diagram', 'service blueprint'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('User Journey Mapper') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating, analyzing, visualizing, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' line is not a proper 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'user journey mapper' repeated twice, which is redundant and lacks natural variations users might say like 'customer journey', 'user flow', 'journey map', 'touchpoints', or 'experience mapping'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'user journey mapper' is a somewhat specific domain, the lack of detail about what distinguishes this from other visual content or UX-related skills creates potential overlap. The category mention 'Visual Content' is too broad to differentiate. | 2 / 3 |
Total | 5 / 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 essentially an empty placeholder that describes itself rather than providing any actual guidance on user journey mapping. It contains no executable code, no concrete examples, no workflow steps, and no references to tools like Mermaid for creating journey maps. The entire content is self-referential boilerplate with zero actionable information.
Suggestions
Add concrete Mermaid syntax examples for creating user journey maps (e.g., `journey` diagram type with sections, tasks, and actors)
Include a step-by-step workflow: 1) Define personas, 2) Map touchpoints, 3) Generate Mermaid code, 4) Validate output
Provide at least one complete, executable example showing input (user scenario) and output (Mermaid journey diagram code)
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual instructional content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples are provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, steps, or executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for creating user journey maps. There are no processes, validation checkpoints, or sequences. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual content to disclose. There are no references to detailed materials, examples, or related documentation that would help with user journey mapping. | 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 | |
- 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.