Deep web research skill using Firecrawl MCP. Use when estimating market size (TAM/SAM/SOM), analyzing trends, or scraping competitors. For competitor teardowns, see competitor-analysis.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
| Tool | Purpose |
|---|---|
firecrawl_search | Web search for market data, trends, competitors |
firecrawl_scrape | Extract structured data from specific pages |
firecrawl_extract | Pull pricing, features, positioning from competitor sites |
firecrawl_map | Discover all pages on a competitor's site |
Before starting any research, clarify with the user:
Execute these searches in parallel:
firecrawl_search: "{industry} market size 2024 2025 report"
firecrawl_search: "{industry} SaaS revenue growth forecast"
firecrawl_search: "{niche} total addressable market"
Structure the output as:
| Metric | Value | Source | Confidence |
|---|---|---|---|
| TAM | $X B | {source} | High/Med/Low |
| SAM | $X M | {source} | High/Med/Low |
| SOM | $X M | {source} | High/Med/Low |
For each competitor identified:
firecrawl_extract:
urls: ["{competitor_url}"]
prompt: "Extract: company name, tagline, pricing tiers, key features, target audience, tech stack indicators"
schema: {
name: string,
tagline: string,
pricing: [{ tier: string, price: string, features: [string] }],
target_audience: string,
key_features: [string]
}
Compile into a comparison matrix:
| Feature | Competitor A | Competitor B | Competitor C | Our Opportunity |
|---|
Search for:
firecrawl_search: "{industry} trends 2025 2026"
firecrawl_search: "{niche} emerging technology"
firecrawl_search: "{industry} pain points users complain"
Categorize trends as:
Save all research to the relevant PLAYBOOK.md directory as RESEARCH.md with:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.
The English summary is being prepared. Showing the original description.
Structured competitor teardown skill. Use when scraping competitor sites, extracting pricing/features/positioning, or analyzing strategic gaps. For general research, see market-research.
The English summary is being prepared. Showing the original description.
Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.
The English summary is being prepared. Showing the original description.
Creates an llms.txt file from scratch based on repository structure. Use when configuring LLM discovery files. For updating existing configurations, see update-llms.
The English summary is being prepared. Showing the original description.
Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans ./ directory files and creates a README.md file for the project. Only used when creating a new repository. or when the README.md file is missing.
The English summary is being prepared. Showing the original description.
Standardizes git operations, branch management, and disaster recovery. Use when committing, branching, or resolving conflicts. For commit formatting, see conventional-commits.
The English summary is being prepared. Showing the original description.