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.
82
78%
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
100%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 that clearly defines its purpose, provides comprehensive trigger terms, and distinguishes itself from general content creation skills. It effectively communicates both the scope (four specific page formats) and the methodology (deep research, modular architecture). The description uses proper third-person voice and avoids vague language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor pages. Also mentions specific approaches like deep research, modular content architecture, and varied section types beyond feature tables. | 3 / 3 |
Completeness | Clearly answers both 'what' (create competitor comparison/alternative pages covering four formats with modular content architecture) and 'when' (explicit 'Use when' triggers with specific phrases and scenarios). The 'when' clause is thorough with multiple trigger terms. | 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,' and 'SEO and sales enablement.' These are highly natural phrases users would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on competitor comparison and alternative pages for SEO/sales enablement. The four specific formats and the enumerated trigger terms make it very unlikely to conflict with general content creation or other marketing skills. | 3 / 3 |
Total | 12 / 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 is a well-structured skill that covers four distinct competitor page formats with clear URL patterns, keyword targets, and section outlines. Its main weaknesses are the lack of concrete examples (no sample copy, no YAML template inline) and the absence of a clear sequential workflow with validation steps. The progressive disclosure is handled well with appropriate references to external files.
Suggestions
Add a concrete example of a completed competitor data YAML file and at least one sample page section (e.g., a TL;DR summary) to make the skill more actionable and copy-paste ready.
Define a clear sequential workflow: e.g., '1. Check context file → 2. Gather missing info → 3. Research competitors → 4. Create data files → 5. Draft pages → 6. Review for accuracy → 7. Finalize' with explicit validation checkpoints.
Trim the Core Principles section—Claude understands concepts like 'honesty builds trust' and 'help them decide.' Replace with a brief directive like 'Be honest about competitor strengths and your limitations; recommend by use case.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary elaboration. Sections like 'Core Principles' explain concepts Claude already understands (honesty builds trust, depth over surface). The page format structures are somewhat repetitive. However, the content is generally well-organized and most sections add value. | 2 / 3 |
Actionability | The skill provides clear page structures and formats with specific URL patterns, keyword targets, and section outlines, which is useful. However, it lacks concrete executable examples—no sample page copy, no YAML template for competitor data files, no example meta tags. It describes what to include rather than showing completed examples. | 2 / 3 |
Workflow Clarity | The research process and page creation steps are listed but lack explicit sequencing and validation checkpoints. There's no clear workflow like 'do step 1, validate, then step 2.' The initial assessment, research, and content creation phases are described but not tied together into a cohesive ordered workflow with feedback loops. | 2 / 3 |
Progressive Disclosure | The skill appropriately references external files like 'references/templates.md' and 'references/content-architecture.md' for detailed templates and data structures. It checks for existing context in '.claude/product-marketing-context.md'. The main file serves as a clear overview with well-signaled one-level-deep references, and related skills are listed at the end. | 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 | |
- Repository
- freekmurze/dotfiles
- Commit
2c6f6e8
- Reviewed
Table of Contents
Is this your skill?
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.