firecrawl-competitive-intel

Name: firecrawl-competitive-intel
Author: firecrawl

29kinstalls18forks

How to install firecrawl-competitive-intel?

firecrawl/firecrawl-workflows/firecrawl-competitive-intel

$npx -y skills add firecrawl/firecrawl-workflows --skill firecrawl-competitive-intel

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Firecrawl Competitive Intel
2
3	Use this for monitoring competitors over time. This is not the broad competitor analysis workflow.
4
5	## Onboarding Interview
6
7	Infer competitors, focus, cadence, and output format from context. If competitors are clear, proceed immediately.
8
9	Ask at most 1-3 concise questions only if blocked, such as the competitor list, focus area, or whether authenticated pages/profiles are required.
10
11	## Firecrawl Collection Plan
12
13	For each competitor, use Firecrawl scrape or browser as needed:
14
15	- pricing pages, annual/monthly toggles, expanded feature tables
16	- feature and product pages
17	- changelogs, blogs, release notes, docs updates
18	- authenticated dashboards only when the user has legitimate access
19
20	## Parallel Work
21
22	If appropriate, use sub-agents or equivalent parallel task runners. A natural split is one competitor per researcher or one focus area per researcher.
23
24	Each researcher should return pricing tiers, features, recent changes, source URLs, and confidence notes.
25
26	## Final Deliverable
27
28	```markdown
29	# Competitive Intel: [Competitors]
30
31	## Alerts
32	[Notable pricing, feature, or positioning changes]
33
34	## Per-Competitor Breakdown
35	[Pricing tiers, feature inventory, recent changes]
36
37	## Cross-Competitor Comparison
38	[Pricing table, feature matrix, key differentiators]
39
40	## Suggested Follow-Ups
41	[What to monitor next]
42
43	## Sources
44	[URLs visited]
45
46	## Rerun Inputs
47	workflow: firecrawl-competitive-intel
48	competitors: [list]
49	focus: [all/pricing/features/changelog]
50	cadence: [one-off/weekly/monthly]
51	```
52
53	## JSON Shape
54
55	When structured output is requested, include `generatedAt`, `competitors`, `pricing`, `recentChanges`, `features`, and `sources`.
56
57	## Quality Bar
58
59	- Extract real plan names, limits, and dates when available.
60	- Note contact-sales or gated details instead of guessing.
61	- Preserve sources for diffing future runs.

People who liked this also viewed

6 picks

Type

firecrawl-competitive-intel

29kinstalls18forks

View on GitHub

How to install firecrawl-competitive-intel?

firecrawl/firecrawl-workflows/firecrawl-competitive-intel

$npx -y skills add firecrawl/firecrawl-workflows --skill firecrawl-competitive-intel

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Firecrawl Competitive Intel
2
3	Use this for monitoring competitors over time. This is not the broad competitor analysis workflow.
4
5	## Onboarding Interview
6
7	Infer competitors, focus, cadence, and output format from context. If competitors are clear, proceed immediately.
8
9	Ask at most 1-3 concise questions only if blocked, such as the competitor list, focus area, or whether authenticated pages/profiles are required.
10
11	## Firecrawl Collection Plan
12
13	For each competitor, use Firecrawl scrape or browser as needed:
14
15	- pricing pages, annual/monthly toggles, expanded feature tables
16	- feature and product pages
17	- changelogs, blogs, release notes, docs updates
18	- authenticated dashboards only when the user has legitimate access
19
20	## Parallel Work
21
22	If appropriate, use sub-agents or equivalent parallel task runners. A natural split is one competitor per researcher or one focus area per researcher.
23
24	Each researcher should return pricing tiers, features, recent changes, source URLs, and confidence notes.
25
26	## Final Deliverable
27
28	```markdown
29	# Competitive Intel: [Competitors]
30
31	## Alerts
32	[Notable pricing, feature, or positioning changes]
33
34	## Per-Competitor Breakdown
35	[Pricing tiers, feature inventory, recent changes]
36
37	## Cross-Competitor Comparison
38	[Pricing table, feature matrix, key differentiators]
39
40	## Suggested Follow-Ups
41	[What to monitor next]
42
43	## Sources
44	[URLs visited]
45
46	## Rerun Inputs
47	workflow: firecrawl-competitive-intel
48	competitors: [list]
49	focus: [all/pricing/features/changelog]
50	cadence: [one-off/weekly/monthly]
51	```
52
53	## JSON Shape
54
55	When structured output is requested, include `generatedAt`, `competitors`, `pricing`, `recentChanges`, `features`, and `sources`.
56
57	## Quality Bar
58
59	- Extract real plan names, limits, and dates when available.
60	- Note contact-sales or gated details instead of guessing.
61	- Preserve sources for diffing future runs.

People who liked this also viewed

6 picks

Type