lean-ux-canvas

Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/lean-ux-canvas/SKILL.md

Quality

Content

35%

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

The content is thorough and well-structured for facilitation, but it is overly verbose for the context budget and relies on referenced files (template.md, examples/sample.md, workshop-facilitation, component skills) that are absent from the bundle. Tightening the inline explanation and supplying the missing references would materially improve it.

Suggestions

Trim the explanatory exposition (Purpose, Key Concepts origin, 'Why This Works') that restates Lean UX knowledge Claude already has; keep only the canvas structure, box definitions, and prompts.

Add the referenced bundle files (template.md, examples/sample.md, workshop-facilitation/SKILL.md) or remove the references so navigation points to real, one-level-deep resources.

Add explicit validation/feedback checkpoints at decision-committing steps (Box 5 solution commitment, Box 8 experiment selection) with a fix-and-retry loop rather than only soft 'Agent validates' prompts.

Dimension	Reasoning	Score
Conciseness	The 574-line body explains at length what the Lean UX Canvas is, its origin, 'why this works', and restates concepts across Purpose, Key Concepts, and per-box sections, padding context that Claude already knows.	1 / 3
Actionability	It offers concrete per-box prompts, examples, and a hypothesis template, but much of the guidance is facilitation scaffolding and bracketed placeholders rather than fully executable, copy-paste-ready instructions.	2 / 3
Workflow Clarity	The 8-box sequence is clearly ordered with per-step validation prompts, but there are no explicit validation/feedback checkpoints or recovery loops for the destructive decision-committing steps (e.g., committing to an experiment), capping clarity at 2.	2 / 3
Progressive Disclosure	It references template.md, examples/sample.md, and component skills, but those bundle files do not exist in the skill directory, and most detail lives inline in the body rather than split into separate well-signaled files.	2 / 3
	Total	7 / 12 Passed

Description

82%

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 strong: it explicitly states the capability, the domain, and a clear 'Use when' trigger clause with specific trigger phrases. It is concise and distinguishable from adjacent skills.

Dimension	Reasoning	Score
Specificity	The description names concrete actions ('framing a business problem', 'surfacing assumptions', 'defining what to learn next') tied to the Lean UX Canvas workflow, listing several specific capabilities.	3 / 3
Completeness	It answers both what (guide teams through Lean UX Canvas v2) and when ('Use when framing a business problem, surfacing assumptions, and defining what to learn next') with an explicit trigger clause.	3 / 3
Trigger Term Quality	It includes natural phrases like 'business problem' and 'assumptions', but the most common user phrasings ('workshop', 'Lean UX', 'hypotheses') are only partly present, missing some common variations.	2 / 3
Distinctiveness Conflict Risk	The specific reference to Lean UX Canvas v2 and its narrow problem-framing scope give it a clear niche unlikely to conflict with other skills.	3 / 3
	Total	11 / 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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (574 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 7 missing, 7 deeper-than-1-level, 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/lean-ux-canvas/SKILL.md
Commit: 9971018

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