user-journey-mapper
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill user-journey-mapperUser Journey Mapper - Auto-activating skill for Visual Content. Triggers on: user journey mapper, user journey mapper Part of the Visual Content skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a placeholder than a useful skill description. It provides no information about what actions the skill performs, what outputs it creates, or meaningful scenarios for when Claude should select it. The redundant trigger term and generic category reference offer almost no value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates visual diagrams of customer touchpoints, maps user flows across channels, identifies pain points and opportunities in the user experience'
Include a proper 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to visualize customer journeys, map user experiences, diagram touchpoints, or create flow charts of user interactions'
Expand trigger terms to include natural variations users would say: 'customer journey', 'user flow', 'experience map', 'touchpoint diagram', 'UX flow', 'customer experience visualization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'User Journey Mapper' is just a name, and 'Auto-activating skill for Visual Content' is vague meta-description that doesn't explain what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use cases or scenarios). The 'Triggers on' line is not a proper 'Use when...' clause with meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'user journey mapper' repeated twice, which is extremely limited. Missing natural variations users might say like 'customer journey', 'user flow', 'experience map', 'touchpoints', or 'journey visualization'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'user journey mapper' is somewhat specific terminology, the lack of detail about what distinguishes this from other visual content or diagramming skills creates potential overlap. The category 'Visual Content' is broad and could conflict with many skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no substantive content. It describes capabilities in abstract terms but provides zero actionable guidance on how to create user journey maps. There are no code examples, no Mermaid syntax, no diagram structures, and no actual instructions despite claiming to be about visual content and diagrams.
Suggestions
Add concrete Mermaid or diagram syntax examples showing how to create user journey maps with stages, touchpoints, and emotions
Include a step-by-step workflow: 1) Define personas, 2) Map stages, 3) Add touchpoints, 4) Visualize with specific diagram code
Provide at least one complete, executable example of a user journey map output
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable 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, examples, or specific instructions are provided. The entire skill describes what it does abstractly without showing how to actually create user journey maps. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains zero actual steps. No process for creating journey maps, no validation, no sequence of actions. | 1 / 3 |
Progressive Disclosure | No references to detailed materials, no examples, no linked resources. The content is a shallow placeholder with no depth or navigation to actual instructional content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.