SKILL

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.

Target: Target not categorized. Automatically collected · unverified.

Excerpt from the author’s documentation

Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.

Read the original English text

Topics in the source

  • Competitive Platform Analysis
  • When to Activate
  • Client positioning brief (establish first)
  • Selection criteria
  • Player taxonomy — axes to populate across
  • Competitive tiers (how the set resolves)
  • Data sources (where to look)
  • Scoring matrix template (selection stage)

Use this skill to decide who to benchmark and where to find them before any scoring begins. A competitive analysis is only as good as its frame: the wrong set makes the client look either unbeatable or doomed. The goal is a defensible, decision-relevant set — not an exhaustive census. About to start a competitive benchmarking project and need to define the competitor set first. Unsure which companies belong in Direct / Adjacent / Aspirational tiers. Need a defensible, pruned scope for a market landscape report. Has a positioning brief and wants to identify who contests that position. First step before running benchmark-methodology. Before scoping the set, establish the client's positioning brief. If you don't already have it, run a short brand-discovery interview to elicit it — do not invent one and do not scope the set blind. The brief supplies: Identity / aesthetic register — what kind of studio or company this is and how it presents itself. Offer — what services or products it delivers. Target clients — who it sells to. Differentiator — the moat or positioning argument the client believes in. Scoping consequence — the implication for how to weight competitors (e.g., prioritize b

This is an excerpt. Refer to the complete source and its current requirements.

Source repository
affaan-m/ECC
Source file
skills/competitive-platform-analysis/SKILL.md
Fixed revision
d2ef2680594f9a17526a6e1a2e18b3d242c5d17b
Read the complete original documentation ↗

Sources and evidence

This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.

Author: affaan-m/ECC · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T15:01:43.509Z.

Categories are inferred from names, descriptions and paths. They do not establish compatibility.

License and attribution

MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.

Original license ↗

Synchronization, copying and user-reported success do not mark a resource as runtime-tested.

Limitations and notes

  • Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.