firecrawl-competitive-intel
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.
Works with
--- 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 --- # 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.
More Writing & Documentation skills
paper-context-resolver
lllllllama/rigorpilot-skills
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.
repo-intake-and-plan
lllllllama/rigorpilot-skills
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

