CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

competitors

Create competitor comparison or alternative pages. Covers singular, plural alternatives, you vs competitor, and competitor vs competitor formats.

Quality

68%

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/competitors/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, largely actionable reference for a content-creation skill, with genuinely useful concrete detail (formats, URL patterns, keyword tables, research process) and properly split one-level-deep bundle files. Its weaknesses are a padded generic-principles section, an implicit rather than explicit end-to-end workflow, and some duplication between the body and the references.

Suggestions

Replace the 'Core Principles' section (generic advice Claude already knows) with a short explicit workflow, e.g. 1. Read product-marketing context and ask the task-specific questions → 2. Pick the matching page format → 3. Research competitors → 4. Draft from templates → 5. Output the competitor data file and page set plan.

Add a verification checkpoint before output (e.g., 'confirm pricing claims are current and competitor strengths are accurately represented before finalizing copy') to anchor the honesty principle in the workflow.

Trim 'Essential Sections' to one-line pointers into references/templates.md to remove duplication with the templates file.

DimensionReasoningScore

Conciseness

The bulk is efficient and concrete (URL patterns, keyword tables, numbered page structures, named review sources), but the 'Core Principles' section is ~25 lines of generic marketing advice Claude already knows ('Show, don't just tell', 'Different tools fit different needs'), and 'Essential Sections' partially duplicates what references/templates.md already covers. This is more than the 'minor instances' of anchor 4, so anchor 3 fits best.

3 / 5

Actionability

For an instruction-only skill, the guidance is concrete and executable: four page formats with URL patterns and target keywords, numbered 6-8 step page structures, a keyword-targeting table, specific research steps with named sources (G2, Capterra, TrustRadius), and explicit output formats. Minor gaps (e.g., the 'Competitor Data File' YAML structure is described but not shown, deferring to references/content-architecture.md) keep it below the fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

The document is organized as a reference catalog rather than a sequenced workflow: the implied flow (assess context → understand product/landscape → pick format → research → produce outputs) is never made explicit, and there are no checkpoints (e.g., verify claims or validate pricing data before publishing). No destructive or batch operations are involved, so the validation cap does not apply; anchor 3 (sequence implicit, checkpoints missing) fits better than anchor 4.

3 / 5

Progressive Disclosure

Both referenced files (references/templates.md and references/content-architecture.md) exist, are one level deep, and are clearly signaled with markdown links at the relevant sections ('For detailed templates', 'For data structure and examples'). Minor gaps — the 'Essential Sections' summary duplicates templates.md content and the body is 264 lines where some material (Core Principles, per-format details) could be trimmed or moved — keep it below anchor 5.

4 / 5

Total

14

/

20

Passed

Description

61%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 states what the skill does with good natural trigger terminology for the niche, and uses proper third-person voice. Its main weakness is the complete absence of 'when to use' guidance, which caps completeness and limits its discoverability, plus a single-verb action description that undersells the research and architecture work the skill actually covers.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks to create an alternatives page, a "X vs Y" comparison page, or competitor research for SEO.'

Broaden trigger vocabulary with natural synonyms users say: 'versus', 'comparison page', 'compare [competitor] and [competitor]', 'tools like [competitor]'.

Reflect the additional concrete actions the skill covers (competitor research, centralized competitor data architecture) to raise specificity beyond a single 'create' verb.

DimensionReasoningScore

Specificity

Names the domain ('competitor comparison or alternative pages') and one concrete action ('Create') with an enumeration of four format variants, but does not list several distinct actions like research, optimization, or data maintenance. It exceeds anchor 2 (which would have only generic actions) but falls short of anchor 4's 'several specific actions' since there is effectively a single verb.

3 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is specific and detailed (formats enumerated), and not a 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural user phrases are present: 'competitor comparison', 'alternative pages', 'you vs competitor', 'competitor vs competitor' — terms a user requesting this page type would actually say. A few natural variations are missing ('versus', 'comparison pages', 'compare X and Y', 'competitive intelligence'), keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (marketing comparison/alternative pages) has distinct triggers unlikely to fire for unrelated skills. Minor overlap risk exists with closely related marketing/SEO skills (e.g., programmatic-seo, copywriting referenced in the body), keeping it below anchor 5's 'minimal conflict risk'.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/competitors/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.