Agent skill

Competitive Platform Analysis

by affaan-m in affaan-m/ECC

A skill your agent uses when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins.

MITAuto-check passed

Install Competitive Platform Analysis

skills CLI
$ npx skills add affaan-m/ECC --skill competitive-platform-analysis -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC competitive-platform-analysis --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/competitive-platform-analysis .claude/skills/competitive-platform-analysis && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
competitive-platform-analysis
GitHub stars
276k
Used in
1 other repo
Token cost
~3k tokens
SKILL.md length
1,426 words
Files
1
Skills in repo
673
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins.

  • Works in 8 steps: Positioning stance — brand-led /… → Specialization — specialist (one tight… → Size / model — solo / micro vs boutique… → …
  • Scoping a competitive landscape — identifying
  • SKILL.md covers When to Activate, Client positioning brief…, Selection criteria and Player taxonomy — axes to…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Competitive Platform Analysis is an agent skill from affaan-m/ECC. 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.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • Scoping a competitive landscape — identifying
  • Score-filtering a competitor set before any benchmarking begins

Example prompts

  • “/competitive-platform-analysis”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Positioning stance — brand-led / editorial (competes on identity,
  2. Specialization — specialist (one tight discipline or vertical) vs
  3. Size / model — solo / micro vs boutique vs mid-size vs
  4. Engagement format — productized (named sprints, audits, fixed packages)
  5. Distinctiveness posture — conventional / safe vs *contrarian /
  6. Evidence / credibility model — outcome-led (metrics, named clients,
  7. Brand strength of the operator — interchangeable vs *cult / ownable
  8. Market / reach — local / regional vs global-remote; note whether they

What it can do on your machine

Read from SKILL.md and the folder at commit ef648e0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Competitive Platform Analysis loads about 3k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 1,426 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit ef648e0, republished under its MIT licence (© affaan-m). 1,426 words, ~2,960 tokens.

Download SKILL.mdSave it as .claude/skills/competitive-platform-analysis/SKILL.md (or your agent's skills folder).
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)

Match the source to the dimension you need. The platform types below are generic; substitute the ones native to the client's niche (e.g. Dribbble/Behance for design, showreel/Vimeo for motion, writing samples/published work for copy):

  • Portfolio / craft platforms — craft quality, range, aesthetic register (e.g. Dribbble, Behance, Vimeo, or the niche's equivalent showcase).
  • Awards / curated showcases — craft ambition and editorial recognition; over-indexes on flashy, so cross-check commercial credibility (e.g. Awwwards, industry award lists).
  • Competitor's own site — primary source for positioning, voice, offer packaging, pricing posture, named clients, manifesto/POV.
  • LinkedIn — team size/model, founder narrative, post cadence, client logos, geography.
  • Review directories — reviews, named clients, project sizes, engagement models; strongest signal for commercial credibility and enterprise-readiness (e.g. Clutch.co or the niche's equivalent).
  • Open / public work — process repos, published samples, open creative output: depth and craft-transparency evidence.
  • Conference talks / podcasts / newsletters — thought-leadership depth and POV ownership.

Always verify claims across at least two sources before treating a competitor attribute as fact (self-reported site copy ≠ verified outcome). Carry an adversarial-verification discipline into every profile.

Show full SKILL.md (512 more words)Show less

Scoring matrix template (selection stage)

A lightweight pre-filter to decide who graduates into full benchmarking. Score 1–5; keep candidates that score high on either distinctiveness or credibility — the client's strategic tension means both poles are instructive.

CandidatePositioning stanceSpecializationSize bandTierOffer overlap (1–5)Distinctiveness (1–5)Commercial credibility (1–5)Craft proximity (1–5)Include?

Rules of thumb (apply per the client's scoping consequence in the positioning brief):

  • High distinctiveness and high credibility → must-profile (proves the client's target tension is achievable).
  • High distinctiveness, low credibility → cautionary case (memorable but un-hireable — a potential failure mode to learn from).
  • High credibility, low distinctiveness → "competent but forgettable" mass the client defines itself against.
  • Low on both → drop unless needed for landscape breadth.

Output of this stage

A scoped, tiered competitor set (typically 10–18 candidates → 8–12 profiled), each tagged with its axis positions, tier, and source links, ready to hand to benchmark-methodology.

Anti-Patterns

  • Scoping without a positioning brief. A competitor list built without the client's lens is noise. The brief determines what counts as a real rival.
  • Listing every similar company. The goal is a defensible 10–18 candidate set, not a census. Breadth without pruning makes benchmarking unmanageable.
  • Blurring the Direct/Adjacent/Aspirational tiers. These tiers serve different strategic purposes. Mixing them produces a flat list that can't drive decisions.
  • Relying on a single source per competitor. Self-reported site copy is marketing, not fact. Verify attributes across at least two sources.
  • Jumping straight to scoring. This skill scopes and tiers the set. Benchmark-methodology handles scoring. Don't conflate the two steps.

Examples

Scenario: A boutique brand-identity studio (2-person, EU-remote, productized sprints, contrarian/manifesto-driven aesthetic) wants to scope its competitive set before benchmarking. The strategic tension from the positioning brief is memorability × hireability.

Step 1 — eight-axis population (sample candidates):

CandidatePositioning stanceSpecializationSize bandEngagementDistinctivenessEvidence modelBrand strengthMarket
Studio Abrand-led / editorialidentity onlymicroproductizedcontrarianaesthetic-ledcultglobal-remote
Studio Bcapability-ledbroad DS+motionboutiquebespokeconventionaloutcome-ledinterchangeableUS
Agency Ccapability-ledbrand+digitalmid-sizeretainerconventionaloutcome-ledinterchangeableEU
Freelancer Dbrand-ledbrand voice onlysoloday-rateeditorialaesthetic-ledownableglobal
Studio Ebrand-ledbrand strategymicroproductizedmanifesto-drivenoutcome-ledcultEU-remote

Step 2 — pre-filter scoring (client scoping consequence: weight distinctiveness because the client's moat is POV-first, not capability breadth):

CandidateOffer overlap (1–5)Distinctiveness (1–5)Commercial credibility (1–5)Craft proximity (1–5)TierInclude?
Studio A5535Direct✓ must-profile
Studio B3253Adjacent✓ credibility anchor
Agency C2152Aspirational✓ scale reference
Freelancer D4424Direct✓ cautionary case
Studio E5544Direct✓ must-profile

Step 3 — output handed to benchmark-methodology: Five candidates (3 Direct, 1 Adjacent, 1 Aspirational), each tagged with axis positions, tier, and source links. Studio A and Studio E are the sharpest head-to-head rivals; Freelancer D is the "memorable but un-hireable" cautionary case to learn from.

  • brand-discovery — use first to establish the positioning brief and strategic tension that scopes the competitor set.
  • benchmark-methodology — the next step; takes the tiered set and scores each competitor across nine dimensions.

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/competitive-platform-analysis of affaan-m/ECC.

Open the folder on GitHubat commit ef648e0

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Competitive Platform Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Competitive Platform Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Competitive Platform Analysis this skillaffaan-m/ECC276k1 repos~3kAutomated safety check: PassMIT
Competitive Landscapewshobson/agents40k—~3kAutomated safety check: PassMIT
Competitive Landscapeaiskillstore/marketplace4308 repos~291Automated safety check: PassNone
Claw Scoreopenclaw/openclaw392k—~2.5kAutomated safety check: PassMIT
Filterzalando/skipper3.3k—~527Automated safety check: PassMIT
Harness Scoreruvnet/ruflo74k—~605Automated safety check: NotesMIT

Similar skills

  • Competitive Landscape

    wshobson/agents

    Analyze competition, identify differentiation opportunities, and develop winning market positioning strategies using Porter's Five Forces, Blue Ocean Strategy, and positioning maps.

    40k GitHub stars~3k tokensUpdated 5 days ago
    Marketing & SEOAuto-check passed
  • Competitive Landscape

    aiskillstore/marketplace

    This skill should be used when the user asks to "analyze competitors", "assess competitive landscape", "identify differentiation", "evaluate market positioning", "apply Porter's Five Forces", or…

    430 GitHub starsUsed in 8 repos~291 tokens
    Marketing & SEOAuto-check passed
  • Claw Score

    openclaw/openclaw

    Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

    392k GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • Filter

    zalando/skipper

    Create or modify code in the filters package and all its sub-folders

    3.3k GitHub stars~527 tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Harness Score

    ruvnet/ruflo

    5-dimension harness readiness scorecard from metaharness score <path.

    74k GitHub stars~605 tokensUpdated today
    DevelopmentAuto-check: notes
  • Score Eval

    sickn33/agentic-awesome-skills

    Imported skill score-eval from upstream source. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~304 tokens
    EducationAuto-check passed

More from affaan-m/ECC

All 673 skills in this repo
  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    276k GitHub starsUsed in 5 repos~1.9k tokens
    Auto-check passed
  • Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    276k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    276k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed
  • Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    276k GitHub stars~2.9k tokensUpdated 5 days ago
    Auto-check passed
  • Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.

    276k GitHub starsUsed in 1 repo~623 tokens
    Auto-check passed
  • Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

    276k GitHub stars~3.5k tokensUpdated 5 days ago
    Auto-check passed

Questions about Competitive Platform Analysis

What does Competitive Platform Analysis do?

A skill your agent uses when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Competitive Platform Analysis is an agent skill from affaan-m/ECC. Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins.

When should I use Competitive Platform Analysis?

Competitive Platform Analysis fits situations like: scoping a competitive landscape — identifying; score-filtering a competitor set before any benchmarking begins.

How do I install Competitive Platform Analysis in Claude Code?

Run `npx skills add affaan-m/ECC --skill competitive-platform-analysis -a claude-code`. Or copy the skill folder (skills/competitive-platform-analysis in affaan-m/ECC) into .claude/skills/competitive-platform-analysis in your project. Claude Code loads it when a task matches its description.

How do I install Competitive Platform Analysis in Codex?

Run `npx skills add affaan-m/ECC --skill competitive-platform-analysis -a codex`. Or copy the skill folder (skills/competitive-platform-analysis in affaan-m/ECC) into .agents/skills/competitive-platform-analysis in your project. Codex loads it when a task matches its description.

Can I use Competitive Platform Analysis in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill competitive-platform-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/competitive-platform-analysis, .gemini/skills/competitive-platform-analysis, .github/skills/competitive-platform-analysis and .opencode/skills/competitive-platform-analysis in your project.

What does Competitive Platform Analysis need to run?

SKILL.md names no scripts, command-line tools or credentials: Competitive Platform Analysis is instructions for the agent only.

Does Competitive Platform Analysis access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Competitive Platform Analysis safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Competitive Platform Analysis use?

Competitive Platform Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Competitive Platform Analysis use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Competitive Platform Analysis?

Skills that share tags, products or a category with Competitive Platform Analysis: Competitive Landscape (wshobson/agents, 40k stars), Competitive Landscape (aiskillstore/marketplace, 430 stars), Claw Score (openclaw/openclaw, 392k stars) and Filter (zalando/skipper, 3.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Competitive Platform Analysis?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 275,546 GitHub stars. The repository holds 673 skills in this directory. The repository was last updated on October 5, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.