CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

75%

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 ./skills/competitive-platform-analysis/SKILL.md
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 well-structured, actionable scoping playbook with clear sequencing, a usable scoring template, and a worked example, all written at a level that assumes Claude's competence. Its main limitations are mild redundancy between the selection-criteria and taxonomy sections and validation framed as a principle rather than an explicit checkpoint loop.

Suggestions

Consolidate the overlapping size-band and specialization framing between 'Selection criteria' and 'Player taxonomy' to remove redundancy and tighten token use.

Promote the two-source verification rule into an explicit numbered checkpoint in the workflow (e.g. 'Verify each attribute against ≥2 sources before tagging as fact') to make the feedback loop concrete.

Consider moving the full worked example or scoring-matrix template into a one-level-deep reference file so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is largely efficient and assumes Claude's competence — it defines axes and rules without re-explaining basic competitive-analysis concepts — though sections like the eight-axis taxonomy and selection criteria repeat size-band and specialization framing in slightly different wording, leaving minor trim opportunities.

4 / 5

Actionability

Provides concrete, usable artifacts: a ready scoring-matrix table with columns and 1–5 scales, explicit tier definitions, and a worked end-to-end example with populated tables — but it is guidance and templates rather than executable code/commands, which is appropriate for an instruction skill yet not fully 'copy-paste ready'.

4 / 5

Workflow Clarity

Clear sequencing is implied across positioning brief → selection criteria → taxonomy → tiers → sources → scoring matrix → output, with validation discipline ('verify claims across at least two sources') and a 'Do not proceed without the positioning brief' checkpoint; however the validation is a principle rather than an explicit step-by-step checkpoint loop, so it stops short of a 5.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (When to Activate, Selection criteria, Player taxonomy, Competitive tiers, Data sources, Scoring matrix, Output, Anti-Patterns, Examples, Related Skills) with no bundle files present and no nested references — content is appropriately self-contained; the only gap is the absence of one-level-deep reference files for the larger reference material (e.g. the scoring matrix or example).

4 / 5

Total

16

/

20

Passed

Description

76%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 strong: it explicitly covers both what the skill does and when to use it, and stakes out a distinct niche in a multi-skill pipeline. Its main weakness is trigger-term breadth — it relies on one formal phrasing rather than covering the natural synonyms a user would actually say.

Suggestions

Broaden trigger-term coverage with everyday synonyms such as 'competitor analysis', 'market landscape', 'competitive set', or 'who should we benchmark' so it matches how users actually phrase the request.

Consider naming the concrete deliverable (a tiered competitor set of ~10–18 candidates) alongside the scoping actions to make the output even more specific.

DimensionReasoningScore

Specificity

Names 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' — but these are scoping actions rather than the fully comprehensive action set a 5 would list.

4 / 5

Completeness

Explicitly answers both 'what' (identifying, categorising, score-filtering a competitor set, deciding tiers and sources) and 'when' ('Use when scoping a competitive landscape... before any benchmarking begins'), with the pipeline position reinforcing the trigger context.

5 / 5

Trigger Term Quality

Includes the natural phrase 'Use when scoping a competitive landscape' but is thin on common user variations or synonyms — it lacks everyday terms like 'competitor analysis', 'market landscape', or 'who are my competitors' that a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche ('score-filtering a competitor set before any benchmarking begins', 'First step in the three-skill competitive pipeline; precedes benchmark-methodology') that distinguishes it from the downstream benchmark-methodology skill and minimizes wrong-skill triggering.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
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.