CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

56%

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 ./skills/competitor-alternatives/SKILL.md

The canonical home for this skill is competitor-alternatives in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 actionable templates (page formats, URL patterns, a competitor data schema), but it is a monolithic 745-line document with no progressive disclosure and notable padding from generic SEO/marketing guidance. The workflow is implicit and lacks validation checkpoints despite involving published competitive claims that need verification.

Suggestions

Split the body into reference files (e.g., references/page-formats.md, references/section-templates.md, references/competitor-data-schema.md, references/research-process.md) and keep SKILL.md as a concise overview linking to them.

Trim generic marketing/SEO explanations Claude already knows (internal linking basics, keyword strategy principles) and keep only the skill-specific structures and templates.

Add an explicit step-by-step workflow with a validation checkpoint before publishing, e.g., verify competitor pricing and feature claims against the centralized data file before generating pages.

DimensionReasoningScore

Conciseness

The 745-line body contains several padded sections explaining generic marketing/SEO knowledge Claude already has (internal linking best practices, 'honesty builds trust' principles, keyword-targeting tables) plus over 100 lines of bracket-placeholder templates, matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor rather than the mostly-efficient one.

2 / 5

Actionability

Concrete guidance throughout: URL patterns per page format, numbered page structures, a complete YAML competitor-data schema, markdown section templates, and keyword tables. These are templates with placeholders rather than fully copy-paste-ready output, leaving minor gaps that fit the score-4 anchor.

4 / 5

Workflow Clarity

A rough process exists (initial assessment, competitor research, centralized data files, page generation, index pages, maintenance) but it is scattered across topic-organized sections rather than presented as a sequence, and there are no validation checkpoints (e.g., verifying competitor pricing claims before publishing), matching the 'steps listed but validation gaps; sequence implicit' anchor.

3 / 5

Progressive Disclosure

Sections are well-organized with headers, but the body is monolithic: the section templates, competitor YAML schema, research process, and SEO details clearly belong in separate reference files, and no bundle files exist. This fits between the 'content that belongs in separate files is inlined' anchor and the good-structure anchor.

3 / 5

Total

12

/

20

Passed

Description

45%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 identifies the skill's domain but reads as a persona statement in second person rather than a capability description. It lacks any 'Use when...' trigger clause, omits natural trigger phrases users would say (e.g., 'vs page', 'competitor alternatives'), and risks overlap with generic SEO skills.

Suggestions

Rewrite in third person and lead with capabilities, e.g., 'Creates competitor comparison and alternative pages ([Competitor] alternative, [A] vs [B] pages), including URL patterns, page structures, and comparison tables.'

Add an explicit trigger clause, e.g., 'Use when the user asks to create competitor comparison, versus, or alternatives pages, or wants to rank for competitor search terms.'

Include natural user-facing keywords such as 'X vs Y page', 'alternative to', 'switch from', and 'comparison page' to improve trigger term coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain ('competitor comparison and alternative pages') and a couple of actions ('build pages that rank for competitive search terms', 'position your product'), matching the score-3 anchor, but the second-person voice ('You are an expert', 'Your goal') incurs the mandatory 1-point penalty per the rubric guidelines, reducing it to 2.

2 / 5

Completeness

It clearly answers 'what' (creating competitor comparison and alternative pages that rank and convert) but contains no 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It includes some relevant keywords ('competitor comparison', 'alternative pages', 'rank for competitive search terms') but misses the natural phrases a user would actually say, such as 'X vs Y', 'competitor alternatives', or 'comparison page', matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The competitor-comparison niche is somewhat specific, but generic phrasing like 'rank for competitive search terms' and 'position your product' creates overlap risk with general SEO, copywriting, and content-marketing skills, fitting the score-3 anchor rather than the mostly-distinct anchor above.

3 / 5

Total

11

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/competitor-alternatives/SKILL.md

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.