/firecrawl-competitive-intel
Firecrawl API key for hosted Firecrawl requests.
$ npx -y skills add firecrawl/firecrawl-workflows --skill firecrawl-competitive-intel --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/firecrawl-competitive-intel
Context preview
The summary Claude sees to decide when to auto-load this skill.
Firecrawl API key for hosted Firecrawl requests.
SKILL.md
firecrawl-competitive-intel.SKILL.mdname: firecrawl-competitive-intel
description: Monitor competitor pricing, features, changelogs, dashboards, and product changes with Firecrawl. Use for recurring competitive intelligence, pricing tier extraction, feature change tracking, or structured competitor alerts.
license: ISC
metadata:
author: firecrawl
version: "0.1.0"
homepage: https://www.firecrawl.dev
source: https://github.com/firecrawl/firecrawl-workflows
inputs:
- name: FIRECRAWL_API_KEY
description: Firecrawl API key for hosted Firecrawl requests.
required: trueFirecrawl 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
# 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.
Read more
name: firecrawl-competitive-intel
description: Monitor competitor pricing, features, changelogs, dashboards, and product changes with Firecrawl. Use for recurring competitive intelligence, pricing tier extraction, feature change tracking, or structured competitor alerts.
license: ISC
metadata:
author: firecrawl
version: "0.1.0"
homepage: https://www.firecrawl.dev
source: https://github.com/firecrawl/firecrawl-workflows
inputs:
- name: FIRECRAWL_API_KEY
description: Firecrawl API key for hosted Firecrawl requests.
required: trueFirecrawl 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
# 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.
Source of truth for Firecrawl workflow skills — outcome-focused skills for AI coding agents: research reports, SEO audits, QA reports, knowledge bases, lead lists, and agent-ready website design systems.

