user-journeys

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

Quality

37%

Does it follow best practices?

Impact

Pending

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

Discovery

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 identifies a UX-focused domain with a few relevant topic areas but reads more like a tag list than a functional skill description. It lacks concrete actions explaining what the skill does, has no 'Use when...' clause to guide selection, and could benefit from more natural trigger terms and explicit scope boundaries.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about user journeys, flow diagrams, UX audits, usability issues, or error handling patterns.'

Replace topic labels with concrete actions, e.g., 'Creates user journey maps, validates UX flows against usability heuristics, and designs error recovery strategies.'

Include common keyword variations users might say, such as 'user flow', 'usability', 'user experience', 'UX review', or 'interaction design'.

Dimension	Reasoning	Score
Specificity	Names the UX domain and lists some actions (journey mapping, UX validation, error recovery), but these are more like topic areas than concrete, specific actions. It doesn't describe what the skill actually does with these concepts (e.g., 'creates journey maps', 'validates user flows against heuristics').	2 / 3
Completeness	Provides a partial 'what' (topic areas) but completely lacks a 'when' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'journey mapping', 'UX validation', and 'error recovery' that users might mention, but misses common variations like 'user flow', 'user journey', 'usability', 'wireframe review', 'user testing', or 'UX audit'.	2 / 3
Distinctiveness Conflict Risk	The UX-specific terms like 'journey mapping' and 'error recovery' provide some distinctiveness, but 'UX validation' is broad enough to overlap with general design review or testing skills. The lack of explicit scope boundaries increases conflict risk.	2 / 3
	Total	7 / 12 Passed

Implementation

42%

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

The skill provides highly actionable, executable content with real Playwright code and detailed journey templates, which is its strongest quality. However, it is severely over-long and monolithic - cramming complete journey examples, test utilities, metrics tracking code, UX checklists, and pattern descriptions into a single file that should serve as an overview. The verbosity is compounded by explaining UX concepts Claude already knows (philosophy section, anti-patterns that are self-evident).

Suggestions

Extract the full journey examples (signup-to-value, checkout) into separate referenced files like `journeys/examples/signup-to-value.md` and keep only a brief example snippet inline.

Move the UX validator utilities and metrics tracking code into referenced files (e.g., `UX_VALIDATORS.md`, `METRICS.md`) and link to them from a concise overview section.

Remove the Philosophy section and Anti-Patterns explanations - these describe UX concepts Claude already understands. Replace with a brief 1-2 line principle statement.

Add an explicit workflow for creating a new journey: steps to follow, how to validate the journey doc is complete, and how to verify the corresponding E2E test covers all documented steps.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Includes extensive example journeys (signup, checkout) that are illustrative but not necessary at this length. Much of the content explains UX concepts Claude already understands (what emotional states are, why error recovery matters, what progressive disclosure is). The philosophy section and anti-patterns section explain obvious concepts.	1 / 3
Actionability	Provides fully executable Playwright test code, complete journey templates with markdown structure, TypeScript utility functions for UX validation, and concrete package.json scripts. Code examples are copy-paste ready with real Stripe test card numbers and specific Playwright APIs.	3 / 3
Workflow Clarity	The journey template provides a clear step-by-step structure with success criteria and error scenarios, and the testing section shows serial test execution. 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 journey specs.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with everything inline. The complete signup journey example, checkout journey example, all Playwright tests, UX validators, metrics code, and patterns are all in one massive file. Much of this content (especially the full journey examples and utility functions) should be split into referenced files like JOURNEY_TEMPLATE.md, EXAMPLES.md, or UX_VALIDATORS.md.	1 / 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 (638 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: d4ddb03

Reviewed: 4 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.