CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

business-model

Generate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.

Quality

75%

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/business-model/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.

A well-structured, instruction-only framework skill with a clear 9-block template and a concrete output process including a viability test. Its weaknesses are padded background sections that restate knowledge Claude already has and the absence of any specified output format for the finished canvas.

Suggestions

Cut or trim the Notes section and the opening of Domain Context (e.g. "Business Model Canvas (Strategyzer, Alexander Osterwalder) is the most widely used canvas framework") — Claude already knows what the BMC is; keep only the when-to-use-vs-alternatives guidance.

Specify the output format explicitly, e.g. "Present the canvas as nine headed sections in the order: Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partners, Cost Structure."

Consider moving the BMC vs Lean Canvas vs Startup Canvas comparison into a references/ file (e.g. ALTERNATIVES.md) and linking to it, keeping SKILL.md leaner.

DimensionReasoningScore

Conciseness

The 9-block question template is legitimate skill content, but the Notes section ("Financial sustainability requires revenue to exceed costs at scale", "Strong business models have clear, defensible value propositions") and parts of the Domain Context restate business concepts Claude already knows. This is more than minor over-explanation (anchor 4) but not severely padded (anchor 2).

3 / 5

Actionability

Concrete per-block guiding questions, a 10-step output process with a specific viability test ("LTV > 3x CAC"), and explicit input requirements give mostly executable guidance. It falls short of anchor 5 because the output format — how the completed 9-block canvas should actually be presented (table, grid, headed sections) — is never specified.

4 / 5

Workflow Clarity

The Output Process gives a clear numbered 1–10 sequence with checkpoints (alignment check in step 8, economic viability test in step 9, assumptions and risks in step 10). This is a generative task, so the destructive/batch validation cap does not apply, but there are no feedback loops or error-recovery guidance that would justify anchor 5.

4 / 5

Progressive Disclosure

The single-file skill is well organized with clear section headers (Input Requirements, Template, Output Process, Domain Context, Further Reading) and one-level external links. It is not anchor 5 because at ~130 lines the Domain Context comparison (~20 lines of BMC vs Lean Canvas vs Startup Canvas) is inline content that could live in a reference file.

4 / 5

Total

15

/

20

Passed

Description

71%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 does and when to use it, with an explicit and well-formed "Use when" clause. The main gaps are limited action variety in the "what" statement and trigger terms that revolve around a single keyword rather than covering natural synonyms like "canvas", "BMC", or "monetization".

Suggestions

Broaden the "what" with one or two more concrete actions, e.g. "Generate a Business Model Canvas with all 9 building blocks, compare it against Lean Canvas alternatives, and flag key assumptions and risks."

Add trigger synonyms to the "Use when" clause — e.g. "Use when the user mentions a business model, BMC, business model canvas, monetization, or how the business makes money."

DimensionReasoningScore

Specificity

"Generate a Business Model Canvas with all 9 building blocks" names the domain and one concrete action with a scope detail, but does not list several distinct actions. It matches anchor 3 (domain plus 1-2 concrete actions), not anchor 4 (several specific actions).

3 / 5

Completeness

It clearly answers "what" ("Generate a Business Model Canvas with all 9 building blocks") and explicitly answers "when" with three concrete trigger phrases, matching the anchor-5 example structure exactly. It is not 4 because the when-clause is already explicit and specific.

5 / 5

Trigger Term Quality

The "Use when" clause offers three natural phrases ("creating a business model", "documenting how a business creates value", "analyzing an existing business model"), but they all orbit the single keyword "business model" and omit common variations such as "canvas", "BMC", "monetization", or "revenue model" — some of which the body's own Triggers line lists but the description does not.

3 / 5

Distinctiveness Conflict Risk

"Business Model Canvas" is a specific named framework with distinct triggers, giving a mostly-distinct niche with only minor overlap risk against closely related strategy or lean-canvas skills. It falls short of anchor 5 because "documenting how a business creates value" is a somewhat broad phrase that adjacent strategy skills could also claim.

4 / 5

Total

15

/

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/business-model/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.