user-journeys

User experience flows - journey mapping, UX validation, error recovery

Quality

37%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/user-journeys/SKILL.md

Quality

Content

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is highly actionable with excellent executable code examples and concrete templates, but suffers severely from verbosity and poor content organization. It reads more like a comprehensive UX handbook than a focused skill file - explaining concepts Claude already understands (journey mapping philosophy, UX anti-patterns, emotional states) while cramming everything into a single monolithic document that would benefit greatly from splitting into referenced files.

Suggestions

Cut the content by 60%+: remove the Philosophy section, Common Journey Patterns (general UX knowledge), Anti-Patterns list, and one of the two full journey examples. Keep only what Claude wouldn't already know.

Split into multiple files: move the journey template to _template.md, Playwright test patterns to a testing.md reference, UX validators to a validators.md reference, and keep SKILL.md as a concise overview with clear links.

Add an explicit workflow for creating a new journey: e.g., '1. Copy template → 2. Fill required fields → 3. Validate with checklist → 4. Create matching test file → 5. Verify test runs'.

Remove explanatory prose like 'Specs test features. Journeys test experiences' and 'A feature can pass all specs but still deliver a terrible experience' - Claude understands these concepts.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Explains concepts Claude already knows (what user journeys are, what emotional states are, what progressive disclosure means). The philosophy section, anti-patterns list, and common journey patterns are all general UX knowledge that doesn't need to be taught. Full example journeys (signup, checkout) are duplicative - one would suffice.	1 / 3
Actionability	Provides fully executable Playwright test code, complete journey templates with concrete examples, TypeScript utility functions for UX validation, and specific package.json scripts. The code examples are copy-paste ready and cover both happy paths and error recovery scenarios.	3 / 3
Workflow Clarity	The journey template provides a clear step-by-step structure with success criteria and error scenarios, and the testing workflow is well-sequenced. However, there's no explicit validation workflow for creating/maintaining journeys themselves - no feedback loop for verifying journey documentation is complete or that tests match documented steps.	2 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files despite the massive length. The journey examples, Playwright tests, UX validators, metrics code, and common patterns could all be split into separate referenced files. Everything is inlined in a single enormous document, making it hard to navigate.	1 / 3
	Total	7 / 12 Passed

Description

32%

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 provides a brief list of UX-related concepts but lacks concrete action verbs, explicit trigger guidance, and sufficient keyword coverage. It reads more like a topic tag list than a functional skill description, making it difficult for Claude to reliably select this skill over others in a large skill library.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about user journeys, UX flows, usability validation, or error handling in user interfaces.'

Expand with concrete actions using third-person voice, e.g., 'Creates user journey maps, validates UX flows against usability heuristics, designs error recovery patterns for user-facing applications.'

Include more natural keyword variations users might say, such as 'user flow', 'usability', 'user experience', 'UX audit', 'interaction design', or 'user path'.

Dimension	Reasoning	Score
Specificity	Names the domain (UX) and some actions (journey mapping, UX validation, error recovery), but these are still somewhat abstract and not fully concrete actions like 'create journey maps' or 'validate user flows against heuristics'.	2 / 3
Completeness	Describes a rough 'what' but completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, but the 'what' itself is also weak, warranting a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'journey mapping', 'UX validation', and 'error recovery' that users might say, but misses common variations like 'user flow', 'user journey', 'usability', 'wireframe review', or 'UX audit'.	2 / 3
Distinctiveness Conflict Risk	The UX domain provides some specificity, but terms like 'error recovery' could overlap with engineering/debugging skills, and 'validation' is generic enough to conflict with testing or QA skills.	2 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

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
skill_md_line_count	SKILL.md is long (637 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: 7c343ac

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.