CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lean-canvas

Generate a Lean Canvas with problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue. Use when exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pm-product-strategy/skills/lean-canvas/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body delivers a well-structured, actionable Lean Canvas template with a genuinely useful Domain Context section on the framework's limitations and alternatives. Its main weakness is token efficiency: redundant Metadata and Notes sections, plus generic template prompts, could be trimmed or consolidated without losing value.

Suggestions

Remove the 'Metadata' section — it duplicates the YAML frontmatter (name, description, triggers) already available to the skill loader.

Merge the 'Notes' section into 'Domain Context' and cut restated points like 'designed for rapid hypothesis testing' that repeat 'Quick hypothesis testing... Best as a brainstorming tool'.

Tighten template prompts by replacing generic questions ('How do you make money?', 'How do you reach customers?') with the specific deliverable criteria, and reconcile '2-3 solution approaches' with the template's 'Top 3 features'.

DimensionReasoningScore

Conciseness

The 'Metadata' section duplicates the frontmatter verbatim and 'Notes' restates the Domain Context ('rapid hypothesis testing' vs. 'Quick hypothesis testing'), while template prompts like 'How do you make money?' are generic padding. Mostly efficient, but the redundancy goes beyond the minor trimming of the anchor-4 example.

3 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: 'Top 3 customer problems', 'Target 1-2 customer segments', '3-5 critical metrics', and 'validation experiments (landing page, interviews, MVP)'. Minor gap: the Output Process says '2-3 solution approaches' while the template specifies 'Top 3 features'.

4 / 5

Workflow Clarity

The 11-step Output Process is clearly sequenced from problem definition through validation experiments, and the task is generative so no destructive-operation validation cap applies. Checkpoints are implicit (steps 10-11 surface assumptions) rather than explicit, keeping it below the top anchor.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and one appropriately placed external link. Minor gaps: the redundant Metadata section and Notes/Domain Context could be merged, and the body exceeds the under-50-lines simple-skill threshold.

4 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description that clearly states what the skill produces and when to use it, with an explicit 'Use when...' clause and concrete trigger phrases. Its only weaknesses are a single action verb for specificity and slightly incomplete synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Enumerates all nine canvas components concretely ('problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue') but relies on a single action verb ('Generate'), leaving minor gaps versus the comprehensive multi-action anchor.

4 / 5

Completeness

Explicitly answers both what ('Generate a Lean Canvas with problem, solution, metrics...') and when ('Use when exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture') with concrete trigger phrases, matching the top anchor's example structure.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture') but misses common variations such as 'business model' or 'startup pitch', so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Lean Canvas' is a distinct niche with specific triggers, but 'modeling a new venture' is broad enough to create minor overlap with general business-model or strategy skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-product-strategy/skills/lean-canvas/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.