CtrlK
BlogDocsLog inGet started
Tessl Logo

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,' 'competitive landing pages,' 'switch from competitor,' or 'comparison content.' 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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is competitor-alternatives in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

46%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 well-organized and offers genuinely specific guidance for building competitor comparison pages, but it is undermined by three dead bundle references, a tool/artifact naming mismatch, and absent validation checkpoints in the workflow. These issues cap actionability and progressive_disclosure below their potential.

Suggestions

Create the referenced bundle files (references/templates.md, references/content-architecture.md, scripts/comparison_matrix_builder.py) — or remove the references — since all three currently point to non-existent files and break navigation.

Reconcile the data-format mismatch: the tool is invoked with --input competitors.json but the Output Artifacts define a YAML 'Competitor Intelligence File'; pick one canonical name and format and use it consistently.

Add an explicit end-to-end workflow with validation checkpoints (e.g., research -> build -> verify every claim is sourced -> run seo-audit -> publish) instead of leaving validation only implied by the Related Skills section.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but sections like 'Core Principles' ('Honesty Builds Trust,' 'Show, don't just tell,' 'Readers are comparing—they'll verify claims') restate generic marketing platitudes Claude already knows and could be trimmed.

3 / 5

Actionability

Section structures, URL patterns, and keyword tables are concrete, but the single executable command (`python3 scripts/comparison_matrix_builder.py --input competitors.json --markdown`) points to a non-existent script, and its input name (`competitors.json`) conflicts with the YAML 'Competitor Intelligence File' artifact — material gaps that fall short of the 'mostly executable' anchor 4.

3 / 5

Workflow Clarity

A rough sequence exists (Initial Assessment → research → choose format → build sections → output) spread across sections, but it is not presented as one unified workflow and validation checkpoints are only implied via the Related Skills seo-audit reference rather than integrated explicitly.

3 / 5

Progressive Disclosure

References are clearly signaled but all three target files are missing — references/templates.md, references/content-architecture.md, and scripts/comparison_matrix_builder.py do not exist in the bundle — so navigation breaks, and detailed page structures are inlined that the skill itself claims to externalize.

2 / 5

Total

11

/

20

Passed

Description

95%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.

A strong, well-structured description that clearly states the skill's purpose, provides rich natural trigger terms, and cleanly separates what from when. The only weakness is a mildly aspirational clause ('Emphasizes deep research...') that is not a concrete capability.

DimensionReasoningScore

Specificity

Names the domain and concrete deliverables ('create competitor comparison or alternative pages') and enumerates four specific formats (singular/plural alternative, you vs competitor, competitor vs competitor), but 'Emphasizes deep research, modular content architecture' is aspirational rather than a concrete action, leaving minor gaps versus the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both what ('create competitor comparison or alternative pages for SEO and sales enablement' covering four formats) and when ('When the user wants to create...' plus 'Also use when the user mentions...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and variations a user would actually say: 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'switch from competitor,' 'competitive landing pages,' 'comparison content.'

5 / 5

Distinctiveness Conflict Risk

Clear niche (competitor comparison/alternative SEO pages) with distinctive triggers like '[Product] vs [Product]' and 'switch from competitor' that are unlikely to fire for unrelated skills; the body's explicit boundary-setting against sibling skills further reduces conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
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.