Firecrawl Competitive Intel
Run recurring Firecrawl monitoring on competitor pricing, features, changelogs, and product pages to catch tier and positioning shifts before you ship or pitch.
Overview
Firecrawl Competitive Intel is an agent skill most often used in Idea (also Validate, Grow) that monitors competitor pricing, features, and changelogs with Firecrawl for recurring structured alerts.
Install
npx skills add https://github.com/firecrawl/firecrawl-workflows --skill firecrawl-competitive-intelWhat is this skill?
- Per-competitor Firecrawl scrape or browser passes on pricing, features, changelogs, blogs, and docs
- Extracts pricing tiers including annual/monthly toggles and expanded feature tables
- Explicitly not the broad one-shot competitor analysis workflow—optimized for recurring intel
- Parallel split: one competitor or one focus area per researcher when using sub-agents
- Authenticated dashboards only when the user has legitimate access
- At most 1–3 onboarding questions when competitor list or focus is blocked
- Natural parallel split: one competitor per researcher
Adoption & trust: 11.5k installs on skills.sh; 29 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Competitors silently change pricing tables and ship features on public pages, and you only notice weeks later when a prospect mentions it.
Who is it for?
Solo builders in crowded SaaS or tool categories who want a repeatable Firecrawl ritual to diff public competitor surfaces on a schedule.
Skip if: One-time landscape reports or deep strategic teardowns; use a broader analysis workflow instead, or skip if you have no named competitors yet.
When should I use this skill?
User needs recurring competitive intelligence, pricing tier extraction, feature change tracking, or structured competitor alerts with Firecrawl.
What do I get? / Deliverables
You get structured per-competitor snapshots—pricing tiers, feature deltas, and release signals—formatted for recurring comparison or alerts.
- Per-competitor pricing tier extraction
- Feature and changelog change summary
- Structured intel report or alert-oriented output
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Idea because sustained competitor watching informs positioning, pricing hypotheses, and differentiation before and while you commit roadmap bets. Competitors subphase matches structured rival tracking—pricing toggles, feature tables, release notes—not a single broad market landscape essay.
Where it fits
Diff three rivals’ annual versus monthly pricing toggles before you pick your own tier structure.
Capture expanded feature matrices on competitor plans while you test willingness-to-pay on a landing page.
Harvest changelog and blog posts to update comparison pages and SEO battlecopy.
Log docs and release-note updates to see which integrations competitors prioritize this quarter.
How it compares
Narrow monitoring workflow for pricing and changelog deltas—not a substitute for full market sizing or qualitative win-loss interviews.
Common Questions / FAQ
Who is firecrawl-competitive-intel for?
Indie founders and small teams tracking a defined competitor set who need machine-friendly captures of public pricing and product changes.
When should I use firecrawl-competitive-intel?
Use it in Idea while refining positioning against named rivals, in Validate when pricing tests must reflect live market tiers, and in Grow when you refresh battlecards before campaigns or sales pushes.
Is firecrawl-competitive-intel safe to install?
See the Security Audits panel on this Prism page; respect site terms and only use authenticated scraping where you have lawful access—never for credential sharing across competitors’ private dashboards.
SKILL.md
READMESKILL.md - Firecrawl Competitive Intel
# Firecrawl Competitive Intel Use this for monitoring competitors over time. This is not the broad competitor analysis workflow. ## Onboarding Interview Infer competitors, focus, cadence, and output format from context. If competitors are clear, proceed immediately. Ask at most 1-3 concise questions only if blocked, such as the competitor list, focus area, or whether authenticated pages/profiles are required. ## Firecrawl Collection Plan For each competitor, use Firecrawl scrape or browser as needed: - pricing pages, annual/monthly toggles, expanded feature tables - feature and product pages - changelogs, blogs, release notes, docs updates - authenticated dashboards only when the user has legitimate access ## Parallel Work If appropriate, use sub-agents or equivalent parallel task runners. A natural split is one competitor per researcher or one focus area per researcher. Each researcher should return pricing tiers, features, recent changes, source URLs, and confidence notes. ## Final Deliverable ```markdown # Competitive Intel: [Competitors] ## Alerts [Notable pricing, feature, or positioning changes] ## Per-Competitor Breakdown [Pricing tiers, feature inventory, recent changes] ## Cross-Competitor Comparison [Pricing table, feature matrix, key differentiators] ## Suggested Follow-Ups [What to monitor next] ## Sources [URLs visited] ## Rerun Inputs workflow: firecrawl-competitive-intel competitors: [list] focus: [all/pricing/features/changelog] cadence: [one-off/weekly/monthly] ``` ## JSON Shape When structured output is requested, include `generatedAt`, `competitors`, `pricing`, `recentChanges`, `features`, and `sources`. ## Quality Bar - Extract real plan names, limits, and dates when available. - Note contact-sales or gated details instead of guessing. - Preserve sources for diffing future runs.