ClaudeSuperPower

competitor-analysis

Skill

Produce a fact-led competitive intel brief on one or more competitors — firmographics, recent strategic moves, product positioning, ICP overlap, and discovery questions. Defaults to your configured competitors from GTM context if none specified. Combines ZoomInfo data (account_research, scoops, inte

Install

git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git ~/.claude/skills/competitor-analysis

What is competitor-analysis?

Produce a fact-led competitive intel brief on one or more competitors — firmographics, recent strategic moves, product positioning, ICP overlap, and discovery questions. Defaults to your configured competitors from GTM context if none specified. Combines ZoomInfo data (account_research, scoops, intent, exec teams, similar companies) with web search for product/pricing/customer-sentiment intelligence. Identify competitors by ZoomInfo account/company ID (preferred) or name; include rich context on why the brief is being pulled and what decision it supports.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~140 tokens of context used while enabled, before you invoke anything

Documentation

README · ~8 min read

Competitor Analysis

Produce a fact-led competitive intel brief. Lead with an executive comparison across competitors, then a per-competitor section. Pull positioning verbatim from the GTM context — don't invent your own opinions about who wins or who's the biggest threat.

Input

The user will provide via $ARGUMENTS:

  • Competitor identifiers (optional) — zero or more of:
    • Preferred: ZoomInfo account/company IDs (numeric). Use directly as companyId; skip the search step for that competitor.
    • Fallback: competitor names. Resolve via search_companies (use companyWebsite from GTM context's url field if present; otherwise companyName).
    • If omitted entirely, default to all competitors configured in your GTM context.
    • For named competitors NOT in GTM context, flag as "uncovered" — research proceeds, but pre-built positioning is missing.
  • Research context (strongly recommended) — a free-form description of why this brief is being pulled and what decision it supports. Richer is better — flat depth enums and deal one-liners produce flat briefs. Capture as much as is true: the deal or situation in play, what you're losing or winning on, the offering or product line under pressure, the audience for the brief (AE prep / leadership review / enablement), how exhaustive the analysis needs to be, and any specific angles or hypotheses to test. Examples:

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.