CtrlK
BlogDocsLog inGet started
Tessl Logo

competitor-profiling

Research and analyze competitors from their URLs to build structured competitor profile documents, dossiers, and competitive intelligence overviews.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/competitor-profiling/SKILL.md

The canonical home for this skill is competitor-profiling in administrakt0r/AI-Agents-Safe-Coding-Skills

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 skill body is well-structured, actionable, and clearly sequenced across scraping, SEO, and synthesis phases, with appropriate offloading of detail to reference files. It could improve by adding explicit error-recovery feedback loops and moving the large inlined output template into the templates reference.

Suggestions

Add an explicit validate→fix→retry feedback loop for batch scraping (e.g., what to do when a Firecrawl or DataForSEO call fails or returns empty data).

Move the full profile markdown template out of SKILL.md into references/templates.md and link to it, keeping only a condensed skeleton inline.

DimensionReasoningScore

Conciseness

The body is mostly efficient with actionable tables, tool calls, and a directory layout, though the 'Core Principles' section and a few explanatory lines ('Accurate profiles are useful profiles') state things Claude could infer and could be trimmed.

4 / 5

Actionability

Provides concrete MCP tool names (firecrawl_map, backlinks_summary, dataforseo_labs_*), per-page extraction tables, a file layout, and a full output template; the `tool → input` notation is pseudo-call rather than real signatures, which are deferred to tool-reference.md.

4 / 5

Workflow Clarity

Clear three-phase sequence (scrape → SEO → synthesize) with numbered steps and a cross-reference verification step in synthesis, plus a never-overwrite-prior-data safety rule; it lacks an explicit validate→fix→retry feedback loop for the batch scraping operation, which keeps it below 5.

4 / 5

Progressive Disclosure

Good structure with clearly signaled one-level-deep references to real files (references/tool-reference.md, references/templates.md); the full profile template is inlined in the body rather than fully delegated to templates.md, a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

66%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 specific and distinct, clearly conveying what the skill produces, but it lacks an explicit 'when to use' trigger clause, which limits its completeness and runtime discoverability.

Suggestions

Append a 'Use when...' trigger clause naming concrete user requests (e.g., profiling competitors, building dossiers, gathering competitive intelligence from URLs).

Add natural trigger synonyms like 'competitor analysis' or 'research competitors' to broaden keyword coverage.

Mention the data sources (site scraping + SEO/market data) to sharpen the capability description.

DimensionReasoningScore

Specificity

Names the domain (competitor profiling) and several concrete outputs — 'structured competitor profile documents, dossiers, and competitive intelligence overviews' — giving multiple specific actions, though it stops short of naming the underlying methods (scraping, SEO data).

4 / 5

Completeness

It clearly states what the skill does but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('competitors', 'profile', 'dossiers', 'competitive intelligence', 'URLs') with good coverage, but misses common variations like 'competitor analysis' or 'research competitors'.

4 / 5

Distinctiveness Conflict Risk

Targets a fairly distinct niche (profiling competitors from URLs into structured documents) with minimal conflict risk, though it could overlap with closely related marketing/research skills.

4 / 5

Total

15

/

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.

Validation15 / 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
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.