CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

user-journeys

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

54

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/user-journeys/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-5

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

The content is highly actionable — real Playwright tests, a usable template, concrete tooling, and thoughtful anti-patterns — but it pays for that with significant length: two full example journeys duplicate the template, and much of the UX checklist restates knowledge Claude already has. The execution workflow is implicit in the section order rather than explicitly sequenced, and nothing is split into reference files despite the skill bundle having none at all.

Suggestions

Cut one of the two full journey examples (checkout adds little beyond signup) and trim the UX checklist to skill-specific criteria, dropping generic best practices Claude already knows — this is the largest token saving.

Add an explicit numbered workflow near the top (e.g., 1. Identify critical journeys, 2. Create docs from the template, 3. Write Playwright journey tests, 4. Wire metrics, 5. Validate against the documentation checklist) so the sequence and checkpoints are explicit rather than implied by section order.

Move the journey template and the full worked example into references/ files (e.g., references/journey-template.md, references/example-signup.md) and keep SKILL.md as a lean overview that links to them.

DimensionReasoningScore

Conciseness

At ~630 lines the body is noticeably verbose: two full worked journey examples (signup and checkout) that largely re-enact the already-given template, plus generic UX best practice Claude already knows ("Primary CTA is immediately visible", "Touch targets >= 44px", "Card validation inline, not after submit"), matching the anchor 'noticeably verbose; several unnecessary explanations or padded sections'. Not a 3 because the duplication and known-concept padding is more than incidental; not a 1 because there is no introductory library/tutorial filler and much of the material is skill-specific scaffolding.

2 / 5

Actionability

The body provides near copy-paste-ready artifacts: a concrete directory layout, a complete journey template, executable Playwright test code (frameLocator Stripe decline/retry flow, CLS and page-load validators), package.json scripts, and a metrics tracking snippet, matching 'mostly executable guidance; concrete code or commands with minor gaps'. Not a 5 because two tests contain placeholder ellipses ('// ... login as new user ...', '// ... complete full journey ...') and the metrics example calls an undefined `analytics` object; not a 3 because the gaps are minor and the common cases are covered with real code rather than pseudocode.

4 / 5

Workflow Clarity

The process is conveyed through section ordering (philosophy → structure → template → examples → testing → validation → metrics) and a closing 'Journey Documentation Checklist', but there is no explicitly numbered end-to-end sequence for executing the skill, so checkpoints remain implicit — matching 'steps listed but validation gaps; sequence present but checkpoints missing or implicit'. Not a 4 because a first-time invocation ('identify journeys → write docs from template → write E2E tests → wire metrics → verify') is never laid out; not a 2 because the material is well-ordered and does include explicit validation artifacts (success criteria checkboxes, error-scenario tests, the final checklist).

3 / 5

Progressive Disclosure

The file is well-sectioned with clear headers and a quick reference, but no references/, scripts/, or assets/ bundle files exist — everything, including a full journey template and two complete example journeys that would naturally live in reference files, is inlined in one 630-line document, matching 'some structure but could be better organized; content that should be separate is inline'. Not a 4 because there are no external references at all and the template/examples are prime candidates for splitting; not a 2 because the section structure is substantial and navigable, not minimal.

3 / 5

Total

12

/

20

Passed

Description

75%Weight 40%Scale 1-5

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 concise, third-person, and covers a coherent niche with both a clear 'what' and an explicit 'when' (via the when-to-use frontmatter field). It sits solidly at the 'good' level across dimensions, falling short of excellent mainly because the trigger terms restate the capability list rather than adding user-natural synonyms, and the description undersells the testing/metrics capabilities documented in the body.

Suggestions

Add user-natural trigger synonyms to the when-to-use clause (e.g., 'when the user mentions user journeys, onboarding funnels, usability flows, or E2E journey testing') so trigger coverage goes beyond restating the capability list.

Mention the testing dimension (e.g., 'writing Playwright E2E journey tests' or 'tracking journey metrics') in the description so the declared capabilities match what the skill body actually delivers.

DimensionReasoningScore

Specificity

"User experience flows - journey mapping, UX validation, error recovery" names the domain and three concrete activities (journey mapping, UX validation, error recovery), matching the 'several specific actions; minor gaps' anchor. Not a 5 because the actions are terse noun phrases that omit capabilities the body actually covers (E2E journey testing with Playwright, journey metrics tracking); not a 3 because three distinct concrete actions exceeds '1-2 concrete actions'.

4 / 5

Completeness

The 'what' is clear ("User experience flows - journey mapping, UX validation, error recovery") and the frontmatter's explicit when-to-use clause ("When mapping user flows, validating UX, or designing error recovery") provides the 'when', matching the anchor 'has both what and when; when could be more explicit'. Not a 5 because the when-to-use clause merely mirrors the description's own terms rather than adding distinct concrete trigger phrases; not a 3 because explicit trigger guidance is present, not merely implied.

4 / 5

Trigger Term Quality

Both fields supply natural phrases users would say — "journey mapping", "user flows", "UX validation", "error recovery", "mapping user flows" — giving good keyword coverage per the anchor 'good keyword coverage; a few natural terms missing'. Not a 5 because common variations like "user journeys", "usability", "onboarding funnel", or "E2E flows" are absent; not a 3 because coverage goes well beyond a single generic keyword with several relevant synonyms present.

4 / 5

Distinctiveness Conflict Risk

The journey-mapping/UX-validation niche is mostly distinct with a clear specialty framing, matching 'mostly distinct; minor overlap risk'. Not a 5 because "error recovery" and "UX validation" overlap with generic testing and E2E-testing skills; not a 3 because the journey-centric framing is more specific than the 'somewhat specific but could still overlap' anchor.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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/maggy

Path

skills/user-journeys/SKILL.md

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.