user-journeys
User experience flows - journey mapping, UX validation, error recovery
38
37%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/user-journeys/SKILL.mdQuality
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 is a terse list of UX-related concepts without explaining what the skill concretely does or when it should be selected. It lacks a 'Use when...' clause, making it difficult for Claude to reliably choose this skill from a large set. The terms used are relevant but insufficiently specific and lack common user-facing variations.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about user journeys, UX flows, usability validation, or error recovery patterns.'
Replace category labels with concrete actions, e.g., 'Creates user journey maps, validates UX flows against usability heuristics, designs error recovery strategies for user-facing applications.'
Include additional natural trigger terms users might say, such as 'user flow', 'usability', 'user journey', 'UX audit', 'interaction design'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UX) and lists some actions like 'journey mapping', 'UX validation', and 'error recovery', but these are more like category labels than concrete, specific actions. It doesn't describe what the skill actually does with these (e.g., 'creates journey maps', 'validates user flows against heuristics'). | 2 / 3 |
Completeness | The description only partially addresses 'what' (and even that is vague), and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, but since the 'what' is also weak, a score of 1 is appropriate. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'journey mapping', 'UX validation', and 'error recovery' that users might mention, but misses common variations like 'user flow', 'usability', 'wireframe review', 'user journey', or 'UX audit'. Coverage is partial. | 2 / 3 |
Distinctiveness Conflict Risk | The UX domain provides some specificity, but terms like 'error recovery' could overlap with error handling skills in other domains. 'User experience flows' is somewhat distinctive but could conflict with general design or product management skills. | 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 concrete Playwright tests, journey templates, and UX validation utilities. However, it is severely over-long and monolithic — much of the content explains general UX concepts Claude already knows, and the entire document should be restructured with a concise overview pointing to separate reference files. The two full journey examples are largely redundant with the template and each other.
Suggestions
Reduce the main SKILL.md to ~100 lines: keep the directory structure, template, and quick reference table, then move the full journey examples, Playwright test code, and UX validators into separate referenced files (e.g., EXAMPLES.md, TESTING.md, UX-VALIDATORS.md).
Remove the Philosophy section, anti-patterns list, and common journey patterns — these are general UX knowledge Claude already possesses and waste token budget.
Keep only one journey example (signup) as a brief illustration of the template in use, rather than two fully expanded examples that repeat the same structure.
Add an explicit workflow for creating and validating journey documentation (e.g., 'create from template → fill all sections → verify error scenarios covered → link E2E test → review checklist').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ 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. The two full journey examples (signup, checkout) are largely redundant with each other and the template. | 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 journey specs. The process of going from journey documentation to implemented tests lacks explicit checkpoints. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files despite being extremely long. The journey examples, Playwright test code, UX validators, metrics tracking, and common patterns could all be split into separate referenced files. Everything is inlined in a single massive document, making it hard to navigate and consuming excessive context window. | 1 / 3 |
Total | 7 / 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 |
|---|---|---|
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
65efb33
- 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.