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 uses second-person voice ('Your goal') which violates the third-person requirement, and lacks an explicit 'Use when...' clause. It would benefit from more concrete actions and natural trigger terms that users would actually say when requesting this type of content.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'vs page', 'alternatives to [product]', 'competitor comparison', 'competitive landing page'.
Rewrite in third person voice (e.g., 'Creates competitor comparison and alternative pages that rank for competitive search terms') instead of second person ('Your goal').
List specific concrete actions such as 'generates feature comparison tables, writes alternative product summaries, creates SEO-optimized competitor vs pages'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (competitor comparison/alternative pages) and some actions (build pages, rank for competitive search terms, position product), but lacks specific concrete actions like 'create feature comparison tables, write alternative product summaries, 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 should cap 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 [product]', 'comparison landing page', or 'competitive analysis page'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on competitor comparison and alternative pages is a reasonably specific niche, but the description could overlap with general SEO content creation, landing page building, or marketing copy skills due to the broad language about ranking and positioning. | 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 excessively verbose, containing extensive content that Claude already knows about marketing, SEO, and comparison page best practices. While the templates and structured formats provide some value, the skill reads more like a comprehensive marketing playbook than a concise, actionable skill file. The lack of progressive disclosure means the entire ~500-line document loads into context every time, wasting significant token budget on generic guidance.
Suggestions
Reduce to ~100 lines by cutting generic marketing/SEO advice Claude already knows (e.g., 'Honesty Builds Trust', basic SEO keyword targeting, research process) and focus only on the specific page structures and data architecture.
Split into multiple files: keep SKILL.md as a concise overview with the four page formats summarized, then reference separate files for section templates (TEMPLATES.md), competitor data schema (DATA_SCHEMA.md), and index page guidance (INDEX_PAGES.md).
Add an explicit sequential workflow with validation steps, e.g.: 1) Gather inputs → 2) Create competitor data file → 3) Validate data completeness → 4) Select page format → 5) Generate content → 6) Review for accuracy claims.
Remove the YAML competitor data example or reduce it to just the schema structure—the extensive Notion example with specific ratings and complaints is illustrative filler that inflates token count without adding reusable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Much of the content is generic marketing/SEO knowledge Claude already possesses—explaining what comparison pages are, why honesty builds trust, basic SEO concepts, and research processes. The extensive YAML templates and markdown templates could be drastically condensed. | 1 / 3 |
Actionability | Provides concrete templates (YAML competitor data structure, markdown section templates, page structures) which are useful, but most content is descriptive guidance rather than executable steps. The templates are fill-in-the-blank rather than truly copy-paste ready, and there's no actual code or tooling commands. | 2 / 3 |
Workflow Clarity | The overall process is implied (research → create data files → generate pages) but never explicitly sequenced as a clear workflow. There are no validation checkpoints—no step to verify competitor data accuracy, no review gates before publishing, no feedback loops for content quality. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. The competitor data templates, section templates, SEO considerations, research process, and all four page formats are all in one massive file. Content like the detailed YAML schema, section templates, and research checklists should be split into referenced files. | 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 (762 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
93c57b2
- 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.