CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

competitor-profiling

When the user wants to research competitors into dated profiles, or asks what a rival charges, claims, or is doing, or whether a conclusion about them is fair: positioning, pricing, features, reviews, SEO, observed facts kept apart from inference. For comparison pages, see competitors. For battle cards, see sales-enablement. For accounts you sell to, see prospecting. For how a competitor grew, see reverse-engineer-marketing.

Quality

83%

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

71%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-engineered operational skill: the research workflow is concrete and executable with specific tools, paths, and extraction checklists, and the writing never over-explains. Its main weakness is duplication — the full profile template and per-tool details are inlined in SKILL.md despite dedicated reference files existing for exactly that content.

Suggestions

Move the full profile template (the ~140-line block under "Each profile follows this structure") into references/templates.md, keeping only a section outline in the body — the existing "For the full profile and summary templates" pointer already promises this split.

Trim the Phase 2 subsections to tool name + one-line purpose, since tool-reference.md already documents each tool's purpose, when-to-use, and key output; keep the save-path and cross-referencing instructions inline.

Add an explicit validation checkpoint in Phase 1 (e.g., verify each scrape returned usable content and re-fetch or fall back to WebFetch on failure) rather than deferring all error handling to the reference.

DimensionReasoningScore

Conciseness

The prose itself is lean — no basic-concept explanations, efficient tables — but the ~140-line full profile template is inlined in the body even though a dedicated templates.md reference exists, and the Phase 2 per-tool listings overlap tool-reference.md's per-tool documentation. Not 4 because a third of the body could be trimmed or moved; not 2 because there is no padding or over-explanation of known concepts.

3 / 5

Actionability

Fully actionable for the common cases: exact MCP tool names per step ("firecrawl_map → competitor URL", "dataforseo_labs_google_ranked_keywords"), exact save paths with naming conventions ("competitor-profiles/raw/<competitor-slug>/<YYYY-MM-DD>/scrapes/<page-name>.md"), per-page extraction tables, and a default-depth heuristic ("Default to quick scan unless... 3 or fewer"). As an instruction-only skill the guidance is concrete throughout, with literal example calls correctly one reference away.

5 / 5

Workflow Clarity

The sequence is clear and well-phased (assessment → stack selection → scrape → SEO → synthesis → output → summary) with real checkpoints (persist raw data before extracting, "never estimate" unavailable SEO metrics, cross-reference claims in Phase 3, check active MCPs before starting). Not 5 because error-recovery loops are delegated to the reference rather than stated as explicit validate-retry steps in the body.

4 / 5

Progressive Disclosure

References are real, clearly signaled, and one level deep, but the body inlines the full profile template right after pointing to references/templates.md ("For the full profile and summary templates: See references/templates.md"), and the Phase 2 tool-by-tool listings duplicate tool-reference.md's structure. Not 4 because content that clearly belongs in the existing reference files occupies roughly a third of the body.

3 / 5

Total

15

/

20

Passed

Description

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

A strong description: it explicitly answers what and when with natural trigger phrasings, uses third person, and disambiguates against four neighboring skills. The only soft spot is that the capability is expressed as one research action plus topic coverage rather than several distinct concrete verbs, and a few common trigger synonyms are missing.

DimensionReasoningScore

Specificity

Concrete scope is named — "research competitors into dated profiles" with enumerated dimensions "positioning, pricing, features, reviews, SEO" and the observed/inference discipline — but the description rests on one macro action plus topic nouns rather than the multiple distinct action verbs of the top anchor.

4 / 5

Completeness

Both what and when are explicit: the "When the user wants to research competitors into dated profiles, or asks what a rival charges, claims, or is doing" clause gives concrete trigger phrases, and the what is stated with the profile dimensions and epistemic rules. Not 4 because the when-clause enumerates multiple concrete trigger scenarios rather than being merely adequate.

5 / 5

Trigger Term Quality

Natural user phrasings are well covered — "what a rival charges, claims, or is doing", "whether a conclusion about them is fair", with the competitor/rival synonym pair — but common variations like "competitor analysis" or "competitive landscape" are absent.

4 / 5

Distinctiveness Conflict Risk

It actively routes overlapping intents to sibling skills — "For comparison pages, see competitors. For battle cards, see sales-enablement. For accounts you sell to, see prospecting. For how a competitor grew, see reverse-engineer-marketing" — giving a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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

coreyhaines31/marketingskills

Path

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