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.mdMermaid-based visual journey diagram
Mermaid diagram present
0%
100%
Touchpoints documented
100%
100%
User actions included
100%
100%
Emotional states or pain points
100%
100%
Channels identified
80%
100%
Persona defined
0%
100%
Valid Mermaid syntax
0%
100%
Production-ready output
100%
100%
Written to file
100%
100%
Multiple journey stages
100%
100%
Without context: $0.2142 · 1m 18s · 11 turns · 12 in / 3,662 out tokens
With context: $0.4148 · 1m 56s · 22 turns · 278 in / 6,086 out tokens
Best practices: personas, stages, pain points
Persona definition
40%
70%
Distinct journey stages
100%
100%
Pain points per stage
100%
100%
Emotional arc present
100%
100%
User actions per stage
100%
100%
Channels or touchpoints named
100%
100%
Visual representation
100%
80%
Opportunities or recommendations
100%
100%
Saved to file
100%
100%
No placeholder content
40%
100%
Without context: $0.3871 · 2m 25s · 18 turns · 18 in / 6,540 out tokens
With context: $0.4748 · 2m 47s · 22 turns · 55 in / 7,815 out tokens
Production-ready charts and multi-file visual output
Mermaid chart used
0%
100%
Valid diagram type
0%
100%
Multiple output files
100%
100%
Stages with actions
100%
100%
Emotional states documented
100%
100%
Channels listed
100%
100%
No TODO placeholders
100%
100%
Persona or user type
20%
80%
Pain points identified
100%
100%
Opportunities for improvement
100%
100%
Without context: $0.3989 · 2m 4s · 18 turns · 19 in / 6,666 out tokens
With context: $0.5036 · 2m 40s · 23 turns · 55 in / 8,431 out tokens
Table of Contents
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.