BC guochuangsai-business-model
中国国际大学生创新大赛（国创赛）商业模式设计专家。当用户需要：(1)了解国创赛商业模式评分规则和评审要点 (2)设计或优化参赛项目的商业模式 (3)分析产业认知、市场定位、盈利模式 (4)撰写参赛PPT的商业模式板块 (5)准备商业模式答辩 (6)评估商业模式的可行性和创新性 (7)提供商业模式相关培训或讲座内容时使用此技能。触发词：商业模式、产业价值、盈利模式、市场定位、竞品分析、财务预测、商业模式画布、BMC、TAM SAM SOM、商业模式创新、国创赛备赛。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 5. 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 53/100
- 0Result and completion. Does not say what the result is
- 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
- 100Tools and files. No external tools needed
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 771 tokens
- 100Running it twice. No mutating operations
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 234: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 49 items
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: clean
This is a markdown-only coaching skill for 国创赛 business-model preparation, with no code execution or hidden data access found.
LLM: benign (high) · VirusTotal: · 29 May 2026