Agent skill

Competitive Report Structure

by affaan-m in affaan-m/ECC

Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis…

MITAuto-check passedMarketing & SEO

Install Competitive Report Structure

skills CLI
$ npx skills add affaan-m/ECC --skill competitive-report-structure -a claude-code

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

GitHub CLI
$ gh skill install affaan-m/ECC competitive-report-structure --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-report-structure .claude/skills/competitive-report-structure && 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-report-structure
GitHub stars
276k
Used in
1 other repo
Token cost
~2.1k tokens
SKILL.md length
1,119 words
Files
1
Skills in repo
683
Repo updated
First seen
Licence
MIT

At a glance

Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis…

  • Works in 8 steps: Executive summary → Market landscape & category framing → Competitor tiers → …
  • Presenting competitive findings to leadership
  • SKILL.md covers When to Activate, Client positioning brief…, Framing principle and Report sections, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Competitive Report Structure is an agent skill from affaan-m/ECC. Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Use when presenting competitive findings to leadership or a board, writing a competitive landscape report, or as the final step of the competitive analysis pipeline.

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

It sits in Marketing & SEO, covering Competitor analysis. 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

  • Presenting competitive findings to leadership
  • Writing a competitive landscape report
  • As the final step of the competitive analysis pipeline

Example prompts

  • “/competitive-report-structure”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Executive summary
  2. Market landscape & category framing
  3. Competitor tiers
  4. Benchmarking matrix
  5. Deep dives
  6. White-space & threats
  7. Strategic recommendations
  8. Sources / methodology appendix

What it can do on your machine

Read from SKILL.md and the folder at commit 4eb71d9. 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 Report Structure loads about 2.1k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 1,119 words of instructions outside code blocks.

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

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 4eb71d9, republished under its MIT licence (© affaan-m). 1,119 words, ~2,121 tokens.

Download SKILL.mdSave it as .claude/skills/competitive-report-structure/SKILL.md (or your agent's skills folder).
name
competitive-report-structure
description
Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Use when presenting competitive findings to leadership or a board, writing a competitive landscape report, or as the final step of the competitive analysis pipeline.

Competitive Report Structure

Use this skill to assemble scored competitor cards into a decision-grade report. The report must answer three questions for the client: who do we compete with, how do we compete, and where is our defensible white-space? Every section earns its place by moving toward those answers — cut anything that doesn't.

When to Activate

  • All competitor profile cards from benchmark-methodology are complete and ready to assemble.
  • Need to present competitive findings to a founder, leadership team, or board.
  • The report must drive decisions (who to compete with, how, where the moat is) — not just document the landscape.
  • Preparing a client deliverable that must be auditable and defensible.

Client positioning brief (establish first)

Before assembling the report, establish the client's positioning brief. It supplies:

  • Strategic tension — the paired axes (e.g., memorability × hireability) that define the client's target white-space. All maps and synthesis resolve back to this tension.
  • Brand balance — the intended proportional mix of the client's strategic emphases (e.g., 60% strategy/evidence, 25% distinctiveness, 15% craft). Every recommendation must be checked against this balance; flag any that would shift it.
  • Differentiator — the framing principle for the executive summary and white-space section.
  • Target quadrant — where the client intends to sit in the tension map; confirming whether that quadrant is genuinely open is the report's central empirical question.

Framing principle

The whole report is organized around the client's strategic tension and recommendations resolve back to the client's deliberate brand balance. Recommendations that would break that balance must be flagged against it explicitly — "this move shifts the balance from X/Y/Z toward A/B/C; confirm intent."

Report sections

1. Executive summary

3–5 takeaways, decision-first. State the most important findings in plain language: where the client is strong, where it's exposed, who occupies its target white-space, and the top 2–3 moves. Written so a founder/PM reads only this and knows what to do. No methodology here.

2. Market landscape & category framing

Define the category and map it. Use a multi-axis map — at minimum a 2×2 (e.g., brand-led <-> capability-led × boutique <-> enterprise-scale), and ideally the client's tension plot from benchmark-methodology as the headline map. Place every profiled competitor and the client. The map should make the client's intended position visually obvious and show how crowded (or empty) it is.

3. Competitor tiers

Organize the set into Direct / Adjacent / Aspirational (from competitive-platform-analysis). One short paragraph per tier explaining who's in it and why it matters to the client. This sets reader expectations before the detail.

4. Benchmarking matrix

The full competitors × dimensions table — the quantitative spine. Rows = competitors (grouped by tier), columns = the nine benchmark dimensions (note: dimension 9 — strategic tension — has two poles (e.g., Memorability and Hireability for a brand-studio client; substitute the client's own paired axes); represent them as two separate sub-columns rather than averaging them). Include the client's own honest self-assessment as a row for contrast. Use a heatmap (color or symbol scale) so strength/weakness patterns are scannable. Do not add a blended total column — report dimensions separately (per the bias controls). Call out the columns where the client leads and where it trails.

5. Deep dives

3–5 most instructive competitors in narrative form (from their profile cards). Choose for instruction, not ranking: the best exemplar of the target tension (high on both poles), the cautionary "one pole only" case, the "competent but forgettable" archetype the client defines against, plus any direct threat. Each deep dive: what they do, what the client should learn, what the client should avoid.

6. White-space & threats

The strategic heart. Two parts:

  • White-space: the position the client can own that rivals don't — argued from the maps and matrix, not asserted. Confirm whether the target quadrant (from the positioning brief) is genuinely open.
  • Threats: who/what pressures the client — a rival closing the gap, substitutes (no-code/AI tools, in-house teams, generalist freelancers), or category shifts. Be honest about the client's own risks (e.g., a bold identity reading as un-serious to risk-averse buyers).
Show full SKILL.md (471 more words)Show less
7. Strategic recommendations

Concrete, prioritized moves: who the client competes with, how it differentiates, and where to invest (offer packaging, evidence/case studies, thought leadership, brand sharpening). Tie every recommendation back to the brand balance from the positioning brief and flag any that would shift it. Sequence by impact × effort.

8. Sources / methodology appendix

The dimensions, weights, rubrics, the scoped set with tiers, source links per competitor, and verification notes (asserted vs proven). This is what makes the report auditable and defensible — carry the adversarial citation discipline through.

How to present data

  • 2×2 / positioning maps — for landscape and the tension plot. Lead with these; they carry the argument faster than prose.
  • Heatmap matrix — for the competitors × dimensions comparison (section 4).
  • Profile cards — the source unit feeding deep dives (section 5).
  • Quadrant callouts — name who sits in each quadrant explicitly, especially the client's target one.
  • Keep tables scannable; push raw evidence and links to the appendix.

Decision framework (the report must resolve these)

  • Who do we compete with? — Name the Direct tier specifically; that's the real fight.
  • How do we compete? — State the client's differentiator in one sentence, grounded in the matrix (which dimensions the client owns).
  • Where are our differentiators defensible? — Identify the dimensions/quadrant rivals can't easily copy (the moat), vs. the ones that are table-stakes.

Trigger questions for the team alignment session

End with questions that force decisions, not admiration of the analysis:

  • Is the target quadrant truly open, or is a rival already moving in?
  • Which Direct competitor is the sharpest threat in the next 12 months, and what's the counter?
  • Does the brand balance still hold given the landscape — should any emphasis shift?
  • Which dimension where the client trails is worth closing, and which to deliberately concede?
  • What's the one move that most widens distinctiveness without costing hireability / credibility?

Anti-Patterns

  • Leading with methodology. The executive summary opens with the most important finding, not an explanation of how the benchmark was run. Methodology belongs in the appendix.
  • Presenting scores without the tension plot. The 2×2 tension map is the headline artefact. A table of numbers without the map buries the strategic insight.
  • Omitting the decision framework. The report must resolve the three questions (who to compete with, how, where the moat is). Leaving these unanswered turns the report into a literature review.
  • Starting before all profile cards are complete. Benchmark-methodology must finish before assembly begins. Partial data produces gaps that undermine the heatmap and white-space analysis.
  • Adding a blended total column to the matrix. Explicitly excluded — it creates a false composite that obscures the asymmetry the client needs to act on.
  • benchmark-methodology — the prerequisite; produces the scored competitor profile cards this skill assembles.
  • competitive-platform-analysis — provides the tier structure (Direct / Adjacent / Aspirational) used in Section 3.
  • brand-discovery — use to establish the client's positioning brief if it hasn't been defined.

© 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-report-structure of affaan-m/ECC.

Open the folder on GitHubat commit 4eb71d9

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 Report Structure 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 Report Structure compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Competitive Report Structure this skillaffaan-m/ECC276k1 repos~2.1kAutomated safety check: PassMIT
SEO Content Brief GeneratorAgriciDaniel/claude-seo19k2 repos~2.6kAutomated safety check: PassMIT
Getxapi ConnectLeoYeAI/openclaw-marketing-skills1k1 repos~715Automated safety check: PassCustom licence
Strategic SEO PlanningAgriciDaniel/claude-seo19k5 repos~1.1kAutomated safety check: PassMIT
X Twitter ConnectLeoYeAI/openclaw-marketing-skills1k1 repos~1.6kAutomated safety check: PassCustom licence
Customer Discoverygooseworks-ai/goose-skills1.2k1 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • SEO Content Brief Generator

    AgriciDaniel/claude-seo

    Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.

    19k GitHub starsUsed in 2 repos~2.6k tokens
    Marketing & SEOAuto-check passed
  • Getxapi Connect

    LeoYeAI/openclaw-marketing-skills

    Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.

    1k GitHub starsUsed in 1 repo~715 tokens
    Marketing & SEOAuto-check passed
  • Strategic SEO Planning

    AgriciDaniel/claude-seo

    Builds an SEO strategy for a new or existing site: discovery, competitor analysis, site architecture, content plan, technical foundation and a four-phase roadmap.

    19k GitHub starsUsed in 5 repos~1.1k tokens
    Marketing & SEOAuto-check passed
  • X Twitter Connect

    LeoYeAI/openclaw-marketing-skills

    Connect TweetClaw to pull public X/Twitter marketing signals into OpenClaw workflows.

    1k GitHub starsUsed in 1 repo~1.6k tokens
    Marketing & SEOAuto-check passed
  • Customer Discovery

    gooseworks-ai/goose-skills

    Discover all customers of a given company by scanning websites, case studies, review sites, press, social media, job postings, and more.

    1.2k GitHub starsUsed in 1 repo~2.1k tokens
    Marketing & SEOAuto-check passed
  • SEO Dataforseo

    AgriciDaniel/codex-seo

    Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.

    799 GitHub starsUsed in 2 repos~4.6k tokens
    Marketing & SEOAuto-check passed

More from affaan-m/ECC

All 683 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~3.1k 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
  • Docs Governance

    affaan-m/ECC

    Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references.

    276k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • 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 today
    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

Questions about Competitive Report Structure

What does Competitive Report Structure do?

Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis…. Competitive Report Structure is an agent skill from affaan-m/ECC. Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions.

When should I use Competitive Report Structure?

Competitive Report Structure fits situations like: presenting competitive findings to leadership; writing a competitive landscape report; as the final step of the competitive analysis pipeline.

How do I install Competitive Report Structure in Claude Code?

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

How do I install Competitive Report Structure in Codex?

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

Can I use Competitive Report Structure 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-report-structure -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-report-structure, .gemini/skills/competitive-report-structure, .github/skills/competitive-report-structure and .opencode/skills/competitive-report-structure in your project.

What does Competitive Report Structure need to run?

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

Does Competitive Report Structure 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 Report Structure 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 Report Structure use?

Competitive Report Structure 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 Report Structure use?

About 2.1k tokens (SKILL.md is roughly 8.5k 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 Report Structure?

Skills that share tags, products or a category with Competitive Report Structure: SEO Content Brief Generator (AgriciDaniel/claude-seo, 19k stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars), Strategic SEO Planning (AgriciDaniel/claude-seo, 19k stars) and X Twitter Connect (LeoYeAI/openclaw-marketing-skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Competitive Report Structure?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,111 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 10, 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.