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.
78
Quality
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/competitor-alternatives/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and completeness. The explicit 'Use when' clause with multiple natural trigger phrases makes it highly discoverable. The main weakness is that the capabilities could be more concrete—it describes the scope and formats but doesn't enumerate specific actions Claude will perform.
Suggestions
Add 2-3 concrete action verbs describing what the skill does, e.g., 'Creates feature comparison tables, writes competitive positioning copy, generates SEO-optimized alternative pages'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (competitor comparison/alternative pages) and mentions some actions like 'deep research, modular content architecture, and varied section types,' but doesn't list concrete specific actions like 'create feature tables,' 'generate comparison matrices,' or 'write competitive positioning copy.' | 2 / 3 |
Completeness | Clearly answers both what (create competitor comparison/alternative pages for SEO and sales enablement, covering four formats) AND when (explicit 'Use when' clause with specific trigger phrases). The 'Also use when' provides explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages.' These are exactly what users would naturally type. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with distinct triggers specific to competitor comparison content. The explicit format types (singular alternative, plural alternatives, you vs competitor, competitor vs competitor) and specific trigger terms like 'vs page' make it unlikely to conflict with general content or SEO skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of competitor page formats and strategy, with good structural organization and appropriate progressive disclosure. However, it lacks concrete, copy-paste-ready examples and explicit validation steps in the workflow. The content explains concepts well but could be more actionable with specific templates and verification checkpoints.
Suggestions
Add a concrete example of actual page copy (e.g., a sample TL;DR summary or comparison paragraph) rather than just describing what should be included
Include validation checkpoints in the research and creation workflow, such as 'Verify competitor pricing on their website before publishing' or 'Have sales team review accuracy'
Provide an inline example of the YAML competitor data structure mentioned in the Output Format section rather than only referencing external files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., 'Why this works' explanations, verbose principle descriptions). Some sections could be tightened without losing clarity. | 2 / 3 |
Actionability | Provides good structural guidance and page formats, but lacks concrete examples of actual copy, specific templates, or executable content. References templates.md and content-architecture.md but doesn't include actionable samples inline. | 2 / 3 |
Workflow Clarity | The research process and page creation steps are outlined but lack explicit validation checkpoints. No clear feedback loops for verifying competitor data accuracy or content quality before publishing. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate use of references to external files (templates.md, content-architecture.md), and logical organization. Navigation is straightforward with one-level-deep references. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
355d067
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.