SKILL

competitive-report-structure

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.

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 text

Topics in the source

  • Competitive Report Structure
  • When to Activate
  • Client positioning brief (establish first)
  • Framing principle
  • Report sections
  • 1. Executive summary
  • 2. Market landscape & category framing
  • 3. Competitor tiers

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. 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. 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 exe

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

Source repository
affaan-m/ECC
Source file
skills/competitive-report-structure/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.517Z.

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.