AC competitor-research
Research competitors systematically. Analyze positioning, pricing, features, marketing, and gaps. Generate competitive intelligence reports with actionable insights. Use when analyzing market competition, benchmarking products, or finding market opportunities. Triggers on "competitor", "competition", "benchmark", "market analysis", "competitive intelligence".
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 2. 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 52/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
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (competitor-research) differs from the folder (market-competitor-research)
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 119 steps
- 100Execution cost. Instruction body is 1803 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 361: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 119 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.