AB competitor-analysis
Write the competitor-analysis section of research reports, strategy decks, and product/brand studies. Use when the user asks for 竞品分析、竞对拆解、对标分析、benchmarking、标杆案例分析、营销案例拆解、产品定位对比、上市节奏分析、品牌升级分析, especially when the goal is not to summarize features but to extract usable conclusions, recommendations, and strategic implications.
As a process B 69/100 · Nearly there — weak spots: inputs and preconditions, consistency, progress reporting
How to improve
- 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (competitor-analysis) differs from the folder (draco-competitor-analysis)
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 65 steps
- 100Execution cost. Instruction body is 1274 tokens
- 100Running it twice. Mutating operations check current state
- low 11 top-level sections: this looks like several domains in one skill
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 326: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 65 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.