competitor-alternatives
You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.
42
30%
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 ./skills/competitor-alternatives/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (competitor comparison pages) but lacks concrete action specificity and has no explicit trigger guidance ('Use when...'). It also uses second person voice ('Your goal', 'your product') which violates the third-person requirement, and reads more like a persona prompt than a skill description.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'vs page', 'alternatives to [product]', 'competitor comparison', 'competitive landing page'.
Replace vague goals with concrete actions: e.g., 'Creates comparison tables, writes feature-by-feature breakdowns, generates SEO-optimized competitor alternative pages'.
Rewrite in third person voice ('Creates competitor comparison pages...') instead of second person ('Your goal is to...').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (competitor comparison/alternative pages) and some actions (build pages, rank for competitive search terms, position product), but doesn't list multiple concrete specific actions like 'create comparison tables, write feature breakdowns, generate SEO-optimized headings'. | 2 / 3 |
Completeness | Describes what it does at a high level but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also somewhat vague, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'competitor comparison', 'alternative pages', and 'competitive search terms', but misses common user variations like 'vs page', 'alternatives to X', 'competitor landing page', 'comparison chart', or 'competitive analysis page'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on competitor comparison and alternative pages is a reasonably specific niche, but the mention of 'ranking for search terms' and 'positioning your product' could overlap with general SEO or marketing content skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive but excessively verbose reference document for creating competitor comparison pages. It covers many aspects thoroughly but fails to respect token budget—most of the content (marketing strategy, SEO basics, comparison page structures) is knowledge Claude already has. The lack of progressive disclosure makes this a monolithic wall of text that would be far more effective as a concise overview with references to detailed sub-files.
Suggestions
Reduce content by 60-70% by removing generic marketing/SEO knowledge Claude already knows (e.g., what FAQ schema is, how internal linking works, basic comparison table advice) and focus only on the specific methodology and data architecture that's unique to this skill.
Split into multiple files: keep SKILL.md as a concise overview (~50-80 lines) with the four page formats and core principles, then reference separate files for section templates, competitor data schema, SEO guidelines, and research process.
Add a clear sequential workflow with explicit steps: e.g., '1. Gather competitor data → 2. Create YAML files → 3. Choose page format → 4. Generate draft → 5. Review for honesty/accuracy → 6. Add schema markup' with validation checkpoints.
Remove the extensive YAML example with fake Notion data and replace with a minimal schema definition—Claude can infer the structure from a compact example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Much of the content is generic marketing/content strategy knowledge that Claude already possesses—page structure templates, SEO basics, research processes, comparison table advice. The YAML competitor data template alone is ~50 lines of example data that doesn't teach Claude anything new. | 1 / 3 |
Actionability | Provides concrete templates (markdown structures, YAML schemas, JSON-LD schema markup) that are somewhat actionable, but most content is strategic guidance and placeholder templates rather than executable instructions. The templates use bracketed placeholders throughout rather than being truly copy-paste ready. | 2 / 3 |
Workflow Clarity | The skill outlines a general process (research → create data files → generate pages) and lists page formats clearly, but lacks explicit sequencing with validation checkpoints. There's no clear step-by-step workflow for actually producing the deliverables—it reads more like a reference document than a guided process. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. The section templates, research process, SEO considerations, and competitor data schemas could all be split into separate referenced files. At this length, the content desperately needs progressive disclosure but has none—everything is dumped into a single massive document. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (757 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
75a3590
- 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.