CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

competitor-research

When the user wants to find competitors for a product or website, assess substitutes, or analyze competition for content, search visibility, backlinks or positioning. Also use when the user mentions "competitor analysis," "competitor research," "competitor keywords," "competitor backlinks," "link gap," "content gap," "competitor content," "competitive analysis," or "competitor comparison." For content roadmap, use content-strategy.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a dense, well-organized instruction skill: concrete query templates, defined output formats, and sequenced workflows with verification habits throughout. Its main weaknesses are mildly over-dense prose in the discovery sections and underuse of the reference-file structure for detailed module content.

Suggestions

Tighten the 'Discover competitors' and 'Discover products through their distribution channels' prose into the same terse table/list style used by the SEO modules to reduce token cost without losing guidance.

Move the detailed research-type modules (keyword, content, backlink, pricing tables) into a reference file, keeping SKILL.md as a shorter overview that selects the module by scope.

Add a one-line worked example of an evidence register row (comparison unit, task, relationship, coverage, surface, URL, date, confidence) to make the abstract register spec directly executable.

DimensionReasoningScore

Conciseness

The body is efficient overall — terse tables, imperative instructions, and no explanation of concepts Claude already knows — but the dense discovery and distribution-channel prose paragraphs could be tightened and the opening paragraph partially repeats the description, fitting the 4 anchor (minor trimming possible) rather than the 5 anchor where every token earns its place.

4 / 5

Actionability

Guidance is mostly executable for a research skill: copy-paste query templates ("[brand] alternatives", "best [tool] for [audience]", site:competitor.com), named tools, a defined evidence-register field list, and a concrete report structure. It falls short of 5 because some positioning guidance remains abstract (e.g., "Use product comparisons to identify meaningful differences and claims the client can support") with no worked example.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (numbered discovery steps, the article fetch workflow, Parse→Enrich→Build→Generate) with several verification checkpoints ("verify identity before adding candidates," "check the claimed capability at the source," "Leave uncertain relationships pending"), matching the 4 anchor; it is not 5 because there are no explicit error-recovery feedback loops, and no destructive/batch cap applies to read-only research.

4 / 5

Progressive Disclosure

The body is well-sectioned and the one bundle reference (references/research-workflow.md) is real, clearly signaled, and one level deep ("Use [research workflow](references/research-workflow.md)…"), matching the 4 anchor for good structure with minor gaps; it is not 5 because substantial method detail (SEO module tables, distribution-channel prose) is inlined in SKILL.md rather than split into the existing reference structure.

4 / 5

Total

16

/

20

Passed

Description

100%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 is a strong example of the form: it states concrete capabilities in third person, provides explicit use-when guidance with an extensive list of natural trigger phrases including synonyms, and closes with a disambiguation pointer to a neighboring skill. It closely matches the rubric's good overall examples.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "find competitors for a product or website, assess substitutes, or analyze competition for content, search visibility, backlinks or positioning" — matching the 5 anchor for multiple specific actions with comprehensive coverage; only pricing analysis is unmentioned, which is not a minor-gap-level omission.

5 / 5

Completeness

Both halves are explicit: the "what" is the opening verb list, and the "when" appears twice ("When the user wants to…" and "use when the user mentions…") with concrete trigger phrases, exactly matching the 5 anchor; the 4 anchor's weaker "when could be more explicit" does not apply.

5 / 5

Trigger Term Quality

Nine quoted natural trigger phrases including synonyms ("competitive analysis" alongside "competitor analysis") and specific terms users would actually say ("link gap," "content gap," "competitor backlinks"), which matches the comprehensive 5 anchor rather than the 4 anchor that permits missing natural terms.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (competitor research scoped to content, search visibility, backlinks, positioning) with competitor-prefixed triggers, and it even disambiguates the nearest overlap ("For content roadmap, use content-strategy"), fitting the 5 anchor's minimal conflict risk rather than the 4 anchor's minor overlap risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

kostja94/marketing-skills

Path

skills/competitor-research/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.