user-journeys

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/user-journeys/SKILL.md

Quality

Content

70%

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

The body is highly actionable with clear, well-sequenced workflows, but it is monolithic and verbose: a large amount of worked-example and code material that should be split into reference files lives inline in SKILL.md.

Suggestions

Move the two full worked journey examples (signup-to-first-value, checkout) and the Playwright/metrics/validator code blocks into separate reference files (e.g., references/journey-examples.md, references/journey-tests.md) and link them from a concise overview, raising progressive_disclosure.

Tighten the body by relying on the journey template once rather than duplicating its structure across two full examples, which would reduce token cost and lift conciseness toward 3.

Keep SKILL.md as a lean overview pointing one level deep to the template, examples, and test helpers, avoiding the deeply inline reference material.

Dimension	Reasoning	Score
Conciseness	The ~630-line body is mostly actionable rather than explaining concepts Claude already knows, but two fully worked journey examples heavily duplicate the template structure and inline complete Playwright/metrics code that could be tightened or offloaded, matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides fully executable Playwright tests with real selectors and test card numbers, concrete package.json scripts, a real directory structure, and copy-paste-ready TypeScript validators — matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	Journey steps are explicitly sequenced with success criteria checklists, error scenarios, recovery paths, and linked E2E tests, providing clear feedback loops matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	The skill is a single monolithic SKILL.md with all content inline — journey examples, test code, metrics, and validators that clearly belong in separate reference files — and no bundle files exist, matching the 'monolithic wall of text' anchor.	1 / 3
	Total	9 / 12 Passed

Description

72%

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 reasonably specific and distinctive with natural trigger terms, but lacks an explicit in-description 'Use when' trigger clause, capping completeness at 2.

Suggestions

Add an explicit 'Use when...' trigger clause directly inside the description (e.g., 'Use when mapping user flows, validating UX, or designing error recovery') so completeness is not capped.

Replace the high-level action categories with more concrete verbs (e.g., 'document, test, and validate user journeys') to lift specificity toward 3.

Dimension	Reasoning	Score
Specificity	The description names the domain ('user experience flows') and several actions ('journey mapping, UX validation, error recovery'), but these are high-level categories rather than a comprehensive list of concrete actions, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	The description states what the skill does but contains no explicit 'Use when...' trigger clause inside the description field; per the rubric, a missing explicit trigger caps completeness at 2 even though a separate when-to-use field exists.	2 / 3
Trigger Term Quality	Terms like 'user experience flows', 'UX validation', and 'error recovery' are natural phrases a user would say when needing this skill, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The UX-journey niche ('journey mapping, UX validation, error recovery') is a clear, specialized domain with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/user-journeys/SKILL.md
Commit: bb6195f

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