competitor-intel-brief
Run a structured competitive teardown in 20 minutes. Covers positioning, ICP, offer analysis, moat assessment, vulnerability mapping, and a direct attack brief. Use when someone says "analyze my competitor," "competitive research," "how do I differentiate from X," or "what are my competitor's weaknesses.
npx skills add majiayu000/claude-skill-registry --skill competitor-intel-brief --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill performs a structured competitive teardown in 20 minutes, focusing on positioning, ICP, offer analysis, moat assessment using Helmer's 7 Powers, vulnerability mapping, and a direct attack brief. It handles different modes (quick, standard, deep) with a default of standard, and can save outputs to a memory path. It drives cross-skill handoffs to Brand Positioning Audit and Founder Intelligence. It requires prior context from related skills and uses Claude Code / OpenClaw as the runtime platform. The output is designed to be pitch-deck ready without editing and aims to surface concrete signals for each finding.
How it works
- Intake: Collect competitor name, website URL, your positioning, and decision purpose in a single message. Fetch the competitor's homepage, about page, pricing, and relevant reviews; flag missing live data.
- Live Research Protocol: Retrieve hero copy (headline/subheadline), origin/mission/team, pricing tiers, and external signals (reviews, comparisons, complaints). Capture direct quotes verbatim from live pages and categorize by signal source.
- Output: Deliver six sections (Positioning Snapshot, Offer & Pricing, Content & Channel, Moat, Vulnerability Map, Attack Brief) with concrete, signal-backed statements. Ensure all claims tie to explicit data points and avoid vague assertions. Include cross-skill handoff formats when applicable.
- Moat and Vulnerability: Apply Helmer's 7 Powers, scoring each power as Have it / Weak version / Doesn't have it, followed by a durability assessment and a concise rationale.
- Handoffs: Provide structured outputs for Brand Positioning Audit and Founder Intelligence integrations, including precise markdown blocks for landscape and context.
When to use it
Use this when someone asks to analyze a competitor, conducts competitive research, seeks differentiation from a named rival, or asks about their weaknesses. Choose mode based on depth needed: quick for fast context, standard for pre-pitch/go-to-market planning, deep for ongoing strategic overhaul and quarterly audits.
What it can touch
- Runtime platform: Claude Code / OpenClaw
- Output paths: Memory Protocol paths like research/competitor-[name]-YYYY-MM-DD.md
- Cross-skill dependencies: Upstream sources (Founder Intelligence, Brand Positioning Audit) and downstream handoffs to Brand Positioning Audit and Founder Intelligence
Caveats
- License: MIT
- Data should be sourced from live pages and public sources; if data is missing, indicate with a DATA NEEDED note rather than guessing.
- The skill emphasizes concrete signals and explicit quotes; avoid speculation beyond what's evidenced.
# Competitor Intel Brief ## Mode Detect from context or ask: *"Quick teardown, full intel brief, or full brief with attack plan?"* | Mode | What you get | Best for | |------|-------------|----------| | `quick` | Positioning snapshot + top 3 vulnerabilities | Fast competitive context before a sales call | | `standard` | Full 4-step teardown: positioning, ICP, offer, moat + vulnerability map | Pre-pitch, GTM planning, repositioning | | `deep` | Full teardown + direct attack brief + quarterly re-audit comparison | Competitive strategy overhaul, new market entry | **Default: `standard`** — use `quick` before a call. Use `deep` if you're building a sustained competitive strategy. --- ## Runtime Context **Platform:** Claude Code / OpenClaw **File system:** Available. Read prior outputs before starting. Save all outputs to the paths specified in Memory Protocol. **Cross-skill dependencies:** - Upstream: Founder Intelligence (competitive context may come from there), Brand Positioning Audit (positioning gaps to investigate) - Downstream: Brand Positioning Audit (Section 3 — Competitive Separation), Founder Intelligence (competitive context for lens application) --- ## Memory Protocol **Sav
- Mode
- Runtime Context
- Memory Protocol
- Ecosystem Connections
- How This Works
- Step 1 — Intake
- Step 2 — Live Research Protocol
- Step 3 — Output
- SECTION 1: Positioning Snapshot
- SECTION 2: Offer & Pricing Analysis
- SECTION 3: Content & Channel Fingerprint
- SECTION 4: Moat Assessment
- SECTION 5: Vulnerability Map
- SECTION 6: Attack Brief
What does the competitor-intel-brief skill do?
Run a structured competitive teardown in 20 minutes. Covers positioning, ICP, offer analysis, moat assessment, vulnerability mapping, and a direct attack brief. Use when someone says "analyze my competitor," "competitive research," "how do I differentiate from X," or "what are my competitor's weaknesses.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill competitor-intel-brief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.