CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

business-model-canvas

아이디어를 9블록 BMC, 시장 규모, unit economics 초안으로 확장한다.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 is an exemplary instruction-only skill: it defines a sharp analytical persona, lists required inputs, provides a complete copy-paste output template covering all three deliverables, and enforces concrete quantitative rules (bottom-up sizing, [가정] marking, LTV/CAC threshold). It is token-efficient with zero padding, and its single-pass workflow is unambiguous with built-in confidence/evidence checkpoints. As a short self-contained skill it needs no external references and is well organized within one file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a two-sentence role stance ("VC Principal처럼 본다"), an input checklist, a fenced output template, and three terse rules. Nothing explains concepts Claude already knows and every token earns its place, matching anchor 5.

5 / 5

Actionability

The guidance is fully executable for an instruction-only skill: a copy-paste-ready output template with exact table schemas (BMC 9 blocks, TAM/SAM/SOM with 신뢰도, unit economics with 계산식/근거 상태), a concrete input list, and specific rules such as "LTV/CAC가 3 미만이면 위험 신호로 표시한다" and bottom-up sizing. Per the scoring notes, absence of code is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

This is a simple single-pass drafting skill whose single action is unambiguous — inputs are enumerated, the output format is fully templated in a fixed section order, and rules constrain the content. Embedded checkpoints (신뢰도 and 근거 상태 columns, the LTV/CAC < 3 risk flag, the "지금 당장 검증할 것" section) provide validation without needing error-recovery loops, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is self-contained with no bundle files (references/, scripts/, assets/ do not exist) and none are needed: the ~60-line body is organized into four clearly headed sections (역할, 입력, 출력 형식, 규칙) with nothing that clearly belongs in a separate file. Navigation is trivial, matching the well-organized-sections standard for a single-file skill.

5 / 5

Total

20

/

20

Passed

Description

66%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, specific, and third-person, naming the three concrete deliverables of the skill with natural domain keywords. Its main weakness is the complete absence of 'when to use' guidance within the description text — the trigger information lives in a separate frontmatter `triggers` field — and a few natural synonyms (비즈니스 모델 캔버스, TAM SAM SOM) are missing from the description itself. Distinctiveness is good, with only minor overlap risk against broader business-analysis skills.

Suggestions

Append an explicit trigger clause to the description, e.g. "사용자가 BMC, 비즈니스 모델 캔버스, TAM SAM SOM, unit economics를 언급하거나 아이디어의 사업 구조를 분석할 때 사용한다", so it answers both 'what' and 'when'.

Include the full Korean term "비즈니스 모델 캔버스" and "TAM SAM SOM" in the description to broaden natural trigger coverage beyond the acronym "BMC".

Mention the assumption-flagging behavior (e.g., "근거 없는 숫자는 [가정]으로 표시") in the description to sharpen both specificity and distinctiveness.

DimensionReasoningScore

Specificity

The description names several concrete deliverables — "9블록 BMC", "시장 규모", "unit economics 초안" — attached to a single expansion action, which goes beyond the 1-2 concrete actions of anchor 3. It falls short of anchor 5 because coverage is not comprehensive (e.g., no mention of assumption identification or validation guidance that the skill actually provides).

4 / 5

Completeness

The 'what' is clear ("아이디어를 9블록 BMC, 시장 규모, unit economics 초안으로 확장한다") but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is specific rather than vague, and not 4 because no 'when' is present at all.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "BMC", "시장 규모", "unit economics" — roughly the keyword density of anchor 4's example. It is not anchor 5 because common variations like the full Korean term "비즈니스 모델 캔버스" and "TAM SAM SOM" are absent from the description text itself.

4 / 5

Distinctiveness Conflict Risk

The BMC + market-sizing + unit-economics framing carves out a distinct niche with minimal conflict risk. It is not 5 because the description lacks explicit trigger phrases and "시장 규모" (market size) is broad enough to overlap with generic market-research or business-plan skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

retention-corp/road-to-founders

Path

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