/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
$ npx -y skills add affaan-m/everything-claude-code --skill competitive-platform-analysis --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/competitive-platform-analysis
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
competitive-platform-analysis.SKILL.mdname: competitive-platform-analysis
description: >-
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.
Competitive Platform Analysis
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.
When to Activate
- 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.
Client positioning brief (establish first)
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 by distinctiveness vs. capability overlap vs. price).
- **Strategic tension** — the paired axes that define the client's white-space
(e.g., memorability × hireability).
**Do not proceed without the positioning brief.** A competitor list scoped without the client's lens is noise, not intelligence. The scoping consequence in particular determines which competitors are *strong* rivals (those that contest the client's moat) vs. merely overlapping on service menu.
Selection criteria
For each candidate, capture these axes — they decide both inclusion and tier:
- **Size / model** — solo, micro-studio (2–8), boutique (sub-30), mid-size
agency. Match the client's own band; same-band studios are the realistic head-to-head set.
- **Niche / specialization** — how closely the candidate's focus overlaps with
the client's offer. Tighter overlap = more direct.
- **Geography / market** — EU vs US vs global-remote; language; time-zone reach.
Note whether they win the same clients the client targets.
- **Pricing & engagement model** — productized sprints, retainer, project,
day-rate; transparent vs "contact us". Signals positioning maturity.
- **Portfolio style** — generic vs. opinionated/editorial vs. contrarian. Closer
to the client's aesthetic register = more they contest the client's distinctiveness.
- **Technical depth / craft maturity** — relevant if the client's credibility
story includes public process work, open tooling, or documented systems.
- **Brand strength** — does the studio have an ownable verbal/visual identity, or
is it interchangeable? Weight this per the client's scoping consequence.
Player taxonomy — axes to populate across
Don't sort competitors into niche-specific buckets; sort them along a few generic axes so the landscape isn't skewed toward one archetype. These axes apply to any creative-service market (design, motion, copywriting, branding, content, film, etc.). Aim for breadth across each axis first, then prune to the most instructive.
1. **Positioning stance** — *brand-led / editorial* (competes on identity, voice, POV) vs *capability-led* (competes on craft, throughput, outcomes). Populate both poles; the client's closest mirror sits at its own end. 2. **Specialization** — *specialist* (one tight discipline or vertical) vs *generalist* (broad service menu). Tighter overlap with the client's focus = more direct. 3. **Size / model** — *solo / micro* vs *boutique* vs *mid-size* vs *enterprise-scale*. Same-band players are the realistic head-to-head; larger bands are the aspirational/commercial-maturity reference. 4. **Engagement format** — *productized* (named sprints, audits, fixed packages) vs *bespoke* (custom project / retainer). Signals positioning maturity. 5. **Distinctiveness posture** — *conventional / safe* vs *contrarian / manifesto-driven*. The opinionated end is key for distinctiveness benchmarking in any niche. 6. **Evidence / credibility model** — *outcome-led* (metrics, named clients, case depth) vs *aesthetic-led* (portfolio, awards). Tells you how each player earns trust. 7. **Brand strength of the operator** — *interchangeable* vs *cult / ownable identity* (including senior independents who prove the "memorable solo brand" model). 8. **Market / reach** — *local / regional* vs *global-remote*; note whether they win the same clients the client targets.
Plot each candidate on the relevant axes; a competitor is *direct* when it sits near the client on positioning, specialization, size, and market at once.
Competitive tiers (how the set resolves)
Group the final set into three tiers — this structure carries through to the report:
- **Direct** — same band, overlapping offer, same client targets. The realistic
head-to-head.
- **Adjacent** — partial overlap (one capability, or a different client size)
that pressures at the edges.
- **Aspirational** — players the client is not competing with today but whose
brand or commercial maturity sets the bar to aim at.
- *(Watch also for substitutes: no-code/AI tools, in-house teams, generalist
freelancers — note as a threat vector, not a profiled competitor unless materially relevant.)*
Data sources (where to look)
Matc
Read more
name: competitive-platform-analysis description: >- 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.
Competitive Platform Analysis
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.
When to Activate
- 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.
Client positioning brief (establish first)
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 by distinctiveness vs. capability overlap vs. price).
- **Strategic tension** — the paired axes that define the client's white-space
(e.g., memorability × hireability).
**Do not proceed without the positioning brief.** A competitor list scoped without the client's lens is noise, not intelligence. The scoping consequence in particular determines which competitors are *strong* rivals (those that contest the client's moat) vs. merely overlapping on service menu.
Selection criteria
For each candidate, capture these axes — they decide both inclusion and tier:
- **Size / model** — solo, micro-studio (2–8), boutique (sub-30), mid-size
agency. Match the client's own band; same-band studios are the realistic head-to-head set.
- **Niche / specialization** — how closely the candidate's focus overlaps with
the client's offer. Tighter overlap = more direct.
- **Geography / market** — EU vs US vs global-remote; language; time-zone reach.
Note whether they win the same clients the client targets.
- **Pricing & engagement model** — productized sprints, retainer, project,
day-rate; transparent vs "contact us". Signals positioning maturity.
- **Portfolio style** — generic vs. opinionated/editorial vs. contrarian. Closer
to the client's aesthetic register = more they contest the client's distinctiveness.
- **Technical depth / craft maturity** — relevant if the client's credibility
story includes public process work, open tooling, or documented systems.
- **Brand strength** — does the studio have an ownable verbal/visual identity, or
is it interchangeable? Weight this per the client's scoping consequence.
Player taxonomy — axes to populate across
Don't sort competitors into niche-specific buckets; sort them along a few generic axes so the landscape isn't skewed toward one archetype. These axes apply to any creative-service market (design, motion, copywriting, branding, content, film, etc.). Aim for breadth across each axis first, then prune to the most instructive.
1. **Positioning stance** — *brand-led / editorial* (competes on identity, voice, POV) vs *capability-led* (competes on craft, throughput, outcomes). Populate both poles; the client's closest mirror sits at its own end. 2. **Specialization** — *specialist* (one tight discipline or vertical) vs *generalist* (broad service menu). Tighter overlap with the client's focus = more direct. 3. **Size / model** — *solo / micro* vs *boutique* vs *mid-size* vs *enterprise-scale*. Same-band players are the realistic head-to-head; larger bands are the aspirational/commercial-maturity reference. 4. **Engagement format** — *productized* (named sprints, audits, fixed packages) vs *bespoke* (custom project / retainer). Signals positioning maturity. 5. **Distinctiveness posture** — *conventional / safe* vs *contrarian / manifesto-driven*. The opinionated end is key for distinctiveness benchmarking in any niche. 6. **Evidence / credibility model** — *outcome-led* (metrics, named clients, case depth) vs *aesthetic-led* (portfolio, awards). Tells you how each player earns trust. 7. **Brand strength of the operator** — *interchangeable* vs *cult / ownable identity* (including senior independents who prove the "memorable solo brand" model). 8. **Market / reach** — *local / regional* vs *global-remote*; note whether they win the same clients the client targets.
Plot each candidate on the relevant axes; a competitor is *direct* when it sits near the client on positioning, specialization, size, and market at once.
Competitive tiers (how the set resolves)
Group the final set into three tiers — this structure carries through to the report:
- **Direct** — same band, overlapping offer, same client targets. The realistic
head-to-head.
- **Adjacent** — partial overlap (one capability, or a different client size)
that pressures at the edges.
- **Aspirational** — players the client is not competing with today but whose
brand or commercial maturity sets the bar to aim at.
- *(Watch also for substitutes: no-code/AI tools, in-house teams, generalist
freelancers — note as a threat vector, not a profiled competitor unless materially relevant.)*
Data sources (where to look)
Matc
Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills
Repo: affaan-m/everything-claude-code
Other skills on ecc.
- /everything-claude-code
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Open skill - /accessibility
Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA
Open skill - /agent-architecture-audit
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for
Open skill - /agent-eval
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics
Open skill - /agent-harness-construction
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
Open skill - /agent-introspection-debugging
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
Open skill

