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.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/competitor-alternatives/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable playbook with concrete templates and a centralized-data architecture, but it is long and padded, lacks validation checkpoints in its workflows, and inlines material that could be split into reference files. It is strong on actionability and weaker on conciseness and progressive disclosure.

Suggestions

Move the large YAML competitor-data schema and section templates into reference files (e.g., references/competitor-data-schema.md, references/section-templates.md) and link to them from SKILL.md to improve progressive disclosure and reduce token load.

Add explicit validation checkpoints to the research and publishing workflow (e.g., verify competitor pricing against a current source, fact-check claims before publishing, re-validate after quarterly updates).

Tighten redundant sections — remove the repeated intro paragraph that duplicates the frontmatter description and consolidate overlapping principle/template lists.

Dimension	Reasoning	Score
Conciseness	The ~750-line body is mostly domain-specific templates and structures rather than explanations of concepts Claude already knows, but it is padded in places (the frontmatter description is restated in the intro, and the YAML data schema and repeated section lists could be tightened), matching the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Provides concrete, copy-paste-ready templates (page structures, a full YAML competitor-data schema, comparison-table formats, and FAQ schema JSON), giving mostly executable guidance with only minor gaps, fitting the anchor just below fully copy-paste ready.	4 / 5
Workflow Clarity	Numbered sequences exist (Research Process, Page Generation, Ongoing Updates cadence) but there are no validation checkpoints or feedback loops (e.g., verifying competitor-claim accuracy before publishing), so it sits at the 'steps listed but checkpoints missing or implicit' anchor rather than 4.	3 / 5
Progressive Disclosure	No bundle files exist and all content lives in a single SKILL.md with section headers, but content that could plausibly be split (the YAML data schema, section templates) is inlined and there are no clearly signaled one-level-deep references, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	13 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 clearly conveys the skill's domain and intent but relies on goal-oriented phrasing instead of concrete actions and lacks an explicit 'Use when' trigger clause. It is distinct from most other skills but could surface more natural search-style trigger phrases.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when creating competitor comparison pages, [competitor] vs [you] pages, or alternative-to roundup pages').

Reword in third person with concrete operations (e.g., 'Generates competitor comparison and alternative pages targeting competitive search terms') to avoid the second-person phrasing that lowers specificity.

Include natural trigger terms and synonyms a user would actually say, such as '[competitor] alternative', 'vs page', and 'compare [you] to [competitor]'.

Dimension	Reasoning	Score
Specificity	Names the domain ('competitor comparison and alternative pages') and a couple of goal-oriented actions ('build pages that rank for competitive search terms', 'position your product effectively'), but these are high-level goals rather than concrete operations, matching the anchor for naming a domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	Clearly states what the skill does but provides no explicit 'Use when...' trigger clause; per the guideline, a missing 'Use when' clause caps completeness at 3, so it is not raised to 4.	3 / 5
Trigger Term Quality	Includes relevant phrases ('competitor comparison', 'alternative pages', 'competitive search terms') but misses natural variations a user would say ('[competitor] alternative', 'vs page', 'compare tools'), fitting the anchor of some relevant keywords missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	The competitor-comparison-page niche is fairly distinct from general skills, with only minor overlap risk against adjacent SEO/copywriting skills, fitting the 'mostly distinct; minor overlap' anchor rather than the fully distinct 5.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/competitor-alternatives/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

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.