firecrawl-search

firecrawl/cli · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/firecrawl/cli --skill firecrawl-search
0 commentsdiscussion
summary

Web search with optional full-page content extraction from results.

  • Returns real search results as JSON with optional --scrape flag to fetch complete page markdown for each result, avoiding redundant fetches
  • Supports filtering by source type (web, images, news), category (GitHub, research, PDF), time range (past hour/day/week/month/year), location, and country
  • Use --limit to control result count and --scrape-formats to customize output formats when extracting full content
  • Part of
skill.md

firecrawl search

Web search with optional content scraping. Returns search results as JSON, optionally with full page content.

When to use

  • You don't have a specific URL yet
  • You need to find pages, answer questions, or discover sources
  • First step in the workflow escalation pattern: search → scrape → map → crawl → interact

Quick start

# Basic search
firecrawl search "your query" -o .firecrawl/result.json --json

# Search and scrape full page content from results
firecrawl search "your query" --scrape -o .firecrawl/scraped.json --json

# News from the past day
firecrawl search "your query" --sources news --tbs qdr:d -o .firecrawl/news.json --json

Options

Option Description
--limit <n> Max number of results
--sources <web,images,news> Source types to search
--categories <github,research,pdf> Filter by category
--tbs <qdr:h|d|w|m|y> Time-based search filter
--location Location for search results
--country <code> Country code for search
--scrape Also scrape full page content for each result
--scrape-formats Formats when scraping (default: markdown)
-o, --output <path> Output file path
--json Output as JSON

Tips

  • --scrape fetches full content — don't re-scrape URLs from search results. This saves credits and avoids redundant fetches.
  • Always write results to .firecrawl/ with -o to avoid context window bloat.
  • Use jq to extract URLs or titles: jq -r '.data.web[].url' .firecrawl/search.json
  • Naming convention: .firecrawl/search-{query}.json or .firecrawl/search-{query}-scraped.json

See also

how to use firecrawl-search

How to use firecrawl-search on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add firecrawl-search
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/firecrawl/cli --skill firecrawl-search

The skills CLI fetches firecrawl-search from GitHub repository firecrawl/cli and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/firecrawl-search

Reload or restart Cursor to activate firecrawl-search. Access the skill through slash commands (e.g., /firecrawl-search) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.446 reviews
  • Diego Lopez· Dec 24, 2024

    Useful defaults in firecrawl-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kiara Nasser· Dec 12, 2024

    Solid pick for teams standardizing on skills: firecrawl-search is focused, and the summary matches what you get after install.

  • Jin Okafor· Dec 12, 2024

    We added firecrawl-search from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Maya Wang· Nov 7, 2024

    Registry listing for firecrawl-search matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Diego Diallo· Nov 3, 2024

    firecrawl-search has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Amina Ndlovu· Nov 3, 2024

    firecrawl-search reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Jin Gupta· Oct 26, 2024

    Useful defaults in firecrawl-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Camila Bhatia· Oct 22, 2024

    firecrawl-search fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Min Chen· Oct 22, 2024

    firecrawl-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Yuki Zhang· Sep 17, 2024

    firecrawl-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 46

1 / 5