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.

82

Quality

78%

Does it follow best practices?

Impact

Pending

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

Discovery

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 purpose, provides extensive trigger terms, and explicitly states both what the skill does and when to use it. The description covers four specific page formats and mentions concrete methodological approaches (deep research, modular content architecture), making it both specific and distinctive. It uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor pages. Also mentions specific 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 'when' clause is thorough and explicit.

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,' and '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 mention of competitive landing pages make it very unlikely to conflict with general content creation or other marketing skills.

3 / 3

Total

12

/

12

Passed

Implementation

57%

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 comprehensive framework for competitor comparison pages with good structural organization and clear page format definitions. Its main weaknesses are the lack of concrete, copy-paste-ready examples (actual page copy snippets, YAML data structures) and some verbosity in principles sections that Claude doesn't need. The workflow could benefit from explicit sequencing with validation checkpoints.

Suggestions

Add a concrete YAML example for the centralized competitor data file rather than just listing what it should contain

Include a short example of actual page copy for at least one format (e.g., a TL;DR summary or paragraph comparison) to make the guidance more actionable

Add an explicit step-by-step workflow with checkpoints: e.g., 1. Gather data → 2. Validate accuracy → 3. Draft page → 4. Review claims against sources → 5. Publish

Trim the 'Core Principles' section to bullet points only—Claude understands honesty and depth without the explanatory sub-bullets

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes some unnecessary explanation that Claude would already know (e.g., 'Honesty Builds Trust' principles, 'Readers are comparing—they'll verify claims'). The core principles section could be significantly tightened. However, the page format structures and specific guidance are reasonably lean.

2 / 3

Actionability

The skill provides clear page structures and formats with specific URL patterns and section breakdowns, which is good. However, it lacks concrete examples of actual page copy, YAML data structures, or specific output templates—it describes what to include rather than showing executable examples. The competitor data file mentions 'YAML format' but doesn't show one.

2 / 3

Workflow Clarity

The skill outlines a research process and page creation flow, but lacks explicit sequencing with validation checkpoints. There's no clear step-by-step workflow for creating a page from start to finish—it's more of a reference document than a guided process. No verification steps for accuracy of competitor claims or content review gates.

2 / 3

Progressive Disclosure

The skill is well-structured with clear sections, uses references to external files appropriately (references/templates.md, references/content-architecture.md), and organizes content logically from assessment through formats, sections, research, SEO, and output. Navigation is straightforward with one-level-deep references.

3 / 3

Total

9

/

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.