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,' or 'competitive landing pages.' 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

71%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/competitor-alternatives/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%

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

This skill provides a solid structural framework for competitor comparison pages with clear format definitions and page structures, but it suffers from verbosity (explaining marketing principles Claude already understands), lack of concrete examples/templates, and broken references to non-existent bundle files. The content would benefit significantly from trimming general marketing advice, adding concrete output examples, and either creating the referenced files or removing the references.

Suggestions

Create the referenced bundle files (references/templates.md and references/content-architecture.md) with concrete examples of competitor YAML data structures and page copy templates, or remove the broken references.

Add a concrete example of a completed competitor data file in YAML and a sample page section (e.g., a TL;DR summary for a hypothetical product comparison) to make the skill more actionable.

Remove or drastically condense the 'Core Principles' section—Claude already understands honesty, depth, and helpfulness in content creation. Replace with a brief 'Key constraints' list.

Add explicit validation steps to the workflow: e.g., verify competitor pricing against live pages before publishing, fact-check feature claims, and review output against a checklist of required sections.

DimensionReasoningScore

Conciseness

The skill is reasonably structured but includes some unnecessary content that Claude already knows—core principles like 'Honesty Builds Trust' and 'Depth Over Surface' are general marketing wisdom Claude doesn't need spelled out. The research process section and SEO considerations also contain fairly obvious guidance. However, the page format structures and specific URL patterns add genuine value.

2 / 3

Actionability

The skill provides clear page structures and format definitions, which is useful guidance. However, it lacks concrete examples of actual page copy, YAML competitor data files, or sample output. The instructions are more of a framework/checklist than executable, copy-paste-ready content. References to templates (references/templates.md) and data structures (references/content-architecture.md) that don't exist in the bundle further reduce actionability.

2 / 3

Workflow Clarity

The skill outlines a logical sequence (research → data architecture → page creation) and provides clear page structures for each format. However, there are no explicit validation checkpoints—no step to verify competitor data accuracy, no review/approval gates before publishing, and no feedback loop for checking SEO performance after launch. For content that could misrepresent competitors, validation steps are important.

2 / 3

Progressive Disclosure

The skill references two files—references/templates.md and references/content-architecture.md—but no bundle files are provided, meaning these references are broken. The main file is also quite long (~200+ lines) with content that could be split into referenced files (e.g., SEO considerations, research process). The monolithic structure with dead references is problematic.

1 / 3

Total

7

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly defines its niche in competitor comparison and alternative page creation. It excels in trigger term coverage with numerous natural phrases users would say, explicitly addresses both what the skill does and when to use it, and occupies a distinct enough niche to avoid conflicts with other skills. The description is well-structured and concise without unnecessary fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor pages. Also specifies concrete approaches like deep research, modular content architecture, and varied section types beyond feature tables.

3 / 3

Completeness

Clearly answers both 'what' (create competitor comparison/alternative pages covering four formats with modular content architecture) and 'when' (explicit 'Use when' triggers with specific phrases and scenarios). The description opens with a 'When the user wants to...' clause and includes an 'Also use when' clause with enumerated trigger terms.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'SEO,' and 'sales enablement.' These are highly natural phrases users would use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche focused specifically on competitor comparison and alternative pages for SEO/sales enablement. The four specific formats and the domain-specific trigger terms make it very unlikely to conflict with other skills like general content writing or generic SEO skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
freekmurze/dotfiles
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.