BF competitor-alternatives
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
As a process F 45/100 · Will not run — References files that are not bundled: /alternatives/notion, /alternatives/airtable, /alternatives/monday
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: /alternatives/notion - warning
missing-refreference to a missing file: /alternatives/airtable - warning
missing-refreference to a missing file: /alternatives/monday - warning
missing-refreference to a missing file: /alternatives/notion-alternatives - warning
missing-refreference to a missing file: /alternatives/airtable-alternatives - warning
missing-refreference to a missing file: /alternatives/monday-alternatives - warning
missing-refreference to a missing file: /compare/notion-vs-airtable - warning
missing-refreference to a missing file: /compare/notion-vs-monday - warning
missing-refreference to a missing file: /compare/airtable-vs-monday
Process rating: all ten parameters 45/100
- 0Tools and files. 9 referenced file(s) missing: /alternatives/notion, /alternatives/airtable, /alternatives/monday
- 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. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4923 tokens
- 100Steps. 174 steps
- 100Consistency. Name and required fields are in place
- low 12 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)
- -218 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 509: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 174 items
- +3Output format is stated explicitly
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.