AC business-model-canvas
想把一个商业想法梳理清楚?9模块画布+单元经济模型+竞争护城河分析,帮你验证生意能不能跑通。覆盖SaaS/平台/AI/API经济/内容付费等8种模式,附对标案例和MVP验证方案。适合创业者、产品经理、商业分析师快速验证商业逻辑。 触发词:商业模式、商业画布、Business Model Canvas、BMC、商业模式设计、商业逻辑、盈利模式、怎么赚钱、变现模式、商业模式分析、价值主张、商业模式图、创业计划、商业验证、单元经济、单位经济、护城河、竞争壁垒、LTV、CAC、MRR 排除:详细财务预测(用Excel)、融资BP(用prd-generator)、市场调研报告
想把一个商业想法梳理清楚?9模块画布+单元经济模型+竞争护城河分析,帮你验证生意能不能跑通。覆盖SaaS/平台/AI/API经济/内容付费等8种模式,附对标案例和MVP验证方案。适合创业者、产品经理、商业分析师快速验证商业逻辑。 触发词:商业模式、商业画布、Business Model…
As a process C 54/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
The same skill appears in 1 more place: ClawHub
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 54/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (business-model-canvas) differs from the folder (mimo-business-model-canvas)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 38 steps
- 100Execution cost. Instruction body is 758 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 286: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 38 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.