CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

competitive-platform-analysis

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong to, and which sources to mine. First step in the three-skill competitive pipeline; precedes benchmark-methodology.

68

Quality

85%

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 content is a well-structured, highly actionable instruction-only skill with concrete axes, templates, a worked example, and explicit validation discipline. Its main costs are token redundancy from axes duplicated across two sections and a monolithic single-file layout that could offload the example and source catalogue to reference files.

Suggestions

Merge the overlapping 'Selection criteria' and 'Player taxonomy' sections into a single axis list — Size/model, Engagement format, Brand strength, and Market each appear twice, and stating each axis once with its inclusion rule would cut significant tokens.

State the two-source verification rule once (in Data sources) and drop its repetition in Anti-Patterns, or convert the Anti-Patterns list to one-line pointers referencing the sections that already cover each rule.

Move the worked 'Examples' section (~30 lines of filled tables) into a one-level-deep reference file (e.g. references/example-walkthrough.md) linked from the body, keeping the core SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body carries genuinely novel domain guidance but repeats itself: the Size/model, Engagement format, Brand strength, and Market/geography axes appear in both "Selection criteria" and "Player taxonomy" sections, and the two-source verification rule is stated in both "Data sources" and "Anti-Patterns". Mostly efficient but could be tightened by merging the duplicated axes — the 3 anchor, not 4, because the redundancy spans whole sections rather than isolated over-explanations.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: an eight-axis taxonomy with defined poles, a named source per dimension (Dribbble, Behance, Clutch.co, Awwwards, LinkedIn), a copy-paste scoring matrix with defined 1–5 columns, explicit keep/drop rules, expected output counts (10–18 candidates → 8–12 profiled), and a fully worked example. This matches the 5 anchor's standard of specific examples covering the common cases.

5 / 5

Workflow Clarity

The sequence is clear and well-ordered (brief → axis population → tiering → pre-filter scoring → handoff), with an explicit validation gate ("Do not proceed without the positioning brief") and a verification checkpoint ("verify claims across at least two sources"), and the example walks Step 1→3. It falls short of the 5 anchor because there are no feedback loops or checkpoints for the failure cases (e.g. what to do when too few candidates survive the pre-filter).

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so the skill is a single self-contained document; internal navigation is easy with clear, well-ordered section headers. It sits at the 4 anchor rather than 5 because at ~205 lines some separable material (the worked example, the data-source catalogue) could be moved to one-level-deep reference files to slim the core SKILL.md.

4 / 5

Total

16

/

20

Passed

Description

88%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: concrete, third-person-free in its 'Use when...' phrasing, explicit about both what the skill does and when to trigger it, and well-positioned within its skill pipeline. Its only gaps are a few missing natural synonyms and slight trigger overlap with the adjacent benchmarking skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "identifying, categorising, and score-filtering a competitor set" and "Decides who counts as a competitor, which tier they belong to, and which sources to mine" — with no vague filler. Coverage of the skill's capabilities is comprehensive for its domain, matching the 5 anchor.

5 / 5

Completeness

Both questions are answered explicitly: what ("identifying, categorising, and score-filtering a competitor set... Decides who counts as a competitor, which tier, which sources") and when ("Use when scoping a competitive landscape... before any benchmarking begins"), with concrete trigger phrasing — a clear match to the 5 anchor. Not the 4 anchor because the 'when' clause is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Natural domain phrases are present ("scoping a competitive landscape", "competitor set", "before any benchmarking begins") and would plausibly be said by a user starting this work. A few natural synonyms and variations are missing (e.g. "competitor research", "market landscape", "competitive analysis"), placing it at the 4 anchor rather than comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (pre-benchmark competitor scoping) and it explicitly disambiguates its pipeline position ("First step in the three-skill competitive pipeline; precedes benchmark-methodology"), but the mention of "benchmarking" creates minor overlap risk with the sibling benchmark-methodology skill. Mostly distinct with minor overlap — the 4 anchor, not 5.

4 / 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

affaan-m/ECC

Path

skills/competitive-platform-analysis/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.