Name: competitor-profiling
Rating: 53.6 (1 reviews)
Author: administrakt0r

competitor-profiling

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

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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

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.

The body is a well-structured, actionable research workflow with concrete tool calls, file paths, and a real two-file reference bundle. Its main weaknesses are a duplicated inlined template that hurts conciseness, and the absence of explicit validation/feedback checkpoints in the batch scraping workflow.

Suggestions

Remove the fully inlined profile template from the body and rely on the existing references/templates.md link, keeping only a short structural outline inline.

Add explicit validation checkpoints to the scraping workflow (e.g., verify each Firecrawl scrape returned content before extracting fields; flag and retry failed scrapes) to lift workflow clarity above the batch-operation cap.

Consolidate the overlapping 'When to Use', 'Task-Specific Questions', and 'Initial Assessment' sections to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but the full profile template is inlined in the body (lines ~197-337) while also being pointed to references/templates.md, and the 'When to Use', 'Task-Specific Questions', and 'Initial Assessment' sections overlap on setup/trigger information.	3 / 5
Actionability	Provides concrete tool invocations ('firecrawl_map → competitor URL', 'firecrawl_scrape → each key page URL'), named DataForSEO endpoints, explicit directory layout, and extraction tables — mostly executable with minor gaps in full call syntax (deferred to tool-reference.md).	4 / 5
Workflow Clarity	Phases 1-3 and the numbered sub-steps give a clear sequence, but this batch scraping operation lacks explicit validate-then-proceed checkpoints or feedback loops, which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Well-structured with clearly signaled, one-level-deep references to references/templates.md and references/tool-reference.md (both real files), though the inlined full profile template slightly duplicates content that already lives in templates.md.	4 / 5
	Total	14 / 20 Passed

Description

58%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 uses correct third-person voice and conveys a clear, specific 'what', but omits any explicit 'when to use' trigger guidance, which limits completeness and trigger-term quality. It is distinct and reasonably specific but would benefit from a 'Use when...' clause with concrete trigger phrases.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when the user asks to profile competitors, build competitive intelligence from URLs, or create competitor dossiers').

Include common synonyms and variations users might say (e.g., 'competitor analysis', 'competitive landscape', 'competitor research') to broaden trigger coverage.

Tighten the action list toward a single comprehensive sentence that pairs 'what' and 'when' concretely.

Dimension	Reasoning	Score
Specificity	Names the domain ('competitors from their URLs') plus several concrete actions — 'Research and analyze', 'build structured competitor profile documents, dossiers, and competitive intelligence overviews' — with only minor coverage gaps.	4 / 5
Completeness	Clearly states 'what' the skill does, but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant natural terms ('competitors', 'competitor URLs', 'dossiers', 'competitive intelligence') but lacks common variations/synonyms a user would naturally say and has no explicit trigger phrase list.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (competitor profiling from URLs, dossiers, competitive intelligence) that is mostly distinct from adjacent marketing skills, with only minor overlap risk.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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: plugins/AI-Agents-Safe-Coding-Skills/skills/competitor-profiling/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.