competitive-intel
Tear down 3-6 competitors with parallel research agents (homepage messaging, pricing, ads they pay to run, lead magnets, launches, AI-citation presence) and synthesize the exploitable gaps into ./brand/competitors.md. Use when you need to know what competitors actually say and sell before positioning, pricing, or writing copy; also runs a non-interactive diff mode for scheduled competitor watching, an ad-recon mode for paid-ads counter-positioning, and a local mode for service businesses (the top 3 in the map pack and the top paid ads for a service and city, their promises, prices, review pace, and the top complaints across their reviews).
boringmarketer · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add boringmarketer/boring-marketing-skills --skill competitive-intel技能说明
name: competitive-intel description: Tear down 3-6 competitors with parallel research agents (homepage messaging, pricing, ads they pay to run, lead magnets, launches, AI-citation presence) and synthesize the exploitable gaps into ./brand/competitors.md. Use when you need to know what competitors actually say and sell before positioning, pricing, or writing copy; also runs a non-interactive diff mode for scheduled competitor watching, an ad-recon mode for paid-ads counter-positioning, and a local mode for service businesses (the top 3 in the map pack and the top paid ads for a service and city, their promises, prices, review pace, and the top complaints across their reviews). when_to_use: competitor analysis, tear down my competitors, who am I up against, what are competitors charging, competitor watch, what changed with competitors, spy on competitor ads, ad recon, competitive landscape, why is competitor X winning, competitor teardown, who's beating me on Google Maps, local competitors, other plumbers in my area, what do my competitors' customers complain about argument-hint: "[competitor names/URLs or a category] | watch | ads " metadata: boring: version: 4.1.1 layer: foundation reads: [positioning#market-assessment, competitors, brand-manifest] writes: [competitors, assets, brand-manifest] optional-keys: [FIRECRAWL_API_KEY, EXA_API_KEY, SCRAPECREATORS_API_KEY, TREG_TOKEN] enhances_with: - toolset: social-data gains: "adds documented creator, social, and ad-library recon to public-page teardowns"
Competitive Intel
Competitor pages tell you what they claim; their ads tell you what they'll pay to claim; their pricing tells you who they're built for; their reviews tell you where they break. This skill collects all four in parallel, with verbatim evidence, and turns them into the three gaps you can actually exploit. Done means: a competitors.md another skill can act on without re-researching, where every claim traces to a quote or URL. The method is a floor, not a ceiling. When the category in front of you argues for a better path, take it and say why.
Context
Only if ./brand/, ./brands/ or MARKETING.md exists (nothing to load otherwise), run:
python3 ${CLAUDE_SKILL_DIR}/../start-here/scripts/brand_context.py --for competitive-intel
(${CLAUDE_SKILL_DIR} is this skill's folder; outside Claude Code use the folder this
file was read from, e.g. .agents/skills/competitive-intel. If the script or python3 is
unavailable, read the brand folder directly: ./brands/<slug>/ when ./brands/active
names one, else ./brand/; then MARKETING.md, preferences.md and the files in
reads:. If none exist, proceed standalone and ask only for the category or
competitor names (or, for a local business, the main service and city).)
Modes
| Trigger | Mode |
|---|---|
| Default: names, URLs, a category, or nothing | TEARDOWN |
| "watch", "diff", "what changed", or any non-interactive/scheduled invocation | WATCH |
| "ads", "ad recon", "what ads are they running" | AD RECON |
| A local service business (brand files say so, or the request names a city, "near me" or Google Maps) | LOCAL |
WATCH and AD RECON are below the teardown sections. WATCH asks zero questions. It is what the weekly competitor-watch routine calls.
Mode 1: TEARDOWN (default)
Phase 1: Build the roster
Target 3-6 competitors. Resolve in this order:
- User named them → use those, but sanity-check each is a real alternative for the brand's buyer, not just a famous name in the space.
- competitors.md exists → confirm the roster in one question ("Re-tear these five, or change the list?"). This is the only question the mode asks.
- Neither → for a local service business, switch to LOCAL mode (review sites
and "alternatives" searches don't list plumbers; the map does). Otherwise discover from the
Category:line inpositioning#market-assessment: search "best<category>tools", "<category>alternatives", and the G2/Capterra category page. Pick by ICP overlap, not size.
We use Exa for the discovery searches: it finds the pages a keyword search misses, such as a smaller peer or an up-and-comer (free tier, then pay as you go). Without it, the same searches in WebSearch work.
Roster judgment: one aspirational leader (sets the category's vocabulary), two or three true peers (fight for the same buyer this quarter), one up-and-comer (shows where the category is moving). A roster of five peers tells you nothing about trajectory; a roster of five giants tells you nothing actionable. More than six competitors dilutes the synthesis. Depth beats coverage.
Phase 2: Parallel evidence collection
Check the web first. Phase 1's discovery search counts; otherwise run one WebSearch yourself before dispatching. If it is denied or errors, the subagents will be blocked too: don't dispatch. Write competitors.md from model knowledge instead (roster and known positioning, every price and count UNVERIFIED), labeled Data: MODEL KNOWLEDGE (not checked live) in the file, and say in one line in chat that allowing WebSearch and WebFetch (/permissions) and re-running makes it live.
Dispatch one subagent per competitor, all in parallel (Task tool, general-purpose). Budget per subagent: ≤ 40 fetches, ≤ 8 minutes, no sub-agents. Six surfaces is ~6-12 fetches, not a crawl. Each subagent gets the brief below plus the competitor's name and domain, and returns the evidence pack: facts, verbatim quotes, URLs. No analysis in the packs; synthesis happens centrally so claims can be compared across competitors. The packs are working data: save them to ./campaigns/competitive-intel/<date>-evidence.md and never paste them into chat.
Scraping rules for every subagent:
- We use Firecrawl for the page reads (
firecrawl_scrape,firecrawl_search): full-page reads, including the JavaScript-rendered pricing pages that a