Help us improve
Share bugs, ideas, or general feedback.
From firecrawl
Provides web search with full page content extraction using Firecrawl CLI. Returns search results as JSON with optional markdown scraping. Use for research, finding articles, or discovering sources.
npx claudepluginhub firecrawl/cli --plugin firecrawlHow this skill is triggered — by the user, by Claude, or both
Slash command
/firecrawl:firecrawl-searchThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Web search with optional content scraping. Returns search results as JSON, optionally with full page content.
Provides web search with full page content extraction using Firecrawl CLI. Returns search results as JSON with optional markdown scraping. Use for research, finding articles, or discovering sources.
Searches the web via the Tavily CLI, returning LLM-optimized results with content snippets, relevance scores, and metadata. Supports domain filtering, time ranges, and multiple search depths.
Performs AI-optimized web searches via Tavily API, returning clean snippets for current information and news.
Share bugs, ideas, or general feedback.
Web search with optional content scraping. Returns search results as JSON, optionally with full page content.
# 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
| 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 |
--scrape fetches full content — don't re-scrape URLs from search results. This saves credits and avoids redundant fetches..firecrawl/ with -o to avoid context window bloat.jq to extract URLs or titles: jq -r '.data.web[].url' .firecrawl/search.json.firecrawl/search-{query}.json or .firecrawl/search-{query}-scraped.jsonSearch costs 2 credits. After you've actually used the results (or decided they were useless), send structured feedback with firecrawl search-feedback <id>. The first feedback per search refunds 1 credit and helps us improve search quality. Do this once per search, in the background, after you finish processing the results — it does not block your main task.
Opt out: if FIRECRAWL_NO_SEARCH_FEEDBACK=1 (or FIRECRAWL_DISABLE_SEARCH_FEEDBACK=1) is set, the CLI silently skips the call and never sends anything. Respect that — do not try to work around it. (Team admins can also disable this server-side; the API will return feedbackErrorCode: "TEAM_OPTED_OUT" and the CLI will exit 0 silently.)
Rules to know before you call this:
--missing-content is the most important field. It's a list of specific pieces of content you expected but did not find. One topic per entry — do not pack multiple topics into one string. These aggregate across teams and tell us what to index next.good → must include at least one --valuable-sources entry.partial → must include --valuable-sources or --missing-content.bad → must include --missing-content or --query-suggestions.creditsRefundedToday / dailyRefundCap / dailyCapReached. When dailyCapReached: true, stop calling search-feedback for the rest of the UTC day — it won't refund anything and you're wasting bandwidth.--silent & is the right pattern — exit code 0 even on failure, so a rejected/expired call never crashes your pipeline.Read the search response's id:
SEARCH_ID=$(jq -r '.id' .firecrawl/search-react-hooks.json)
Then send feedback. Pick the rating that matches what actually happened:
# Results were useful, with notes on what was still missing
firecrawl search-feedback "$SEARCH_ID" \
--rating good \
--valuable-sources '[{"url":"https://react.dev/reference/react/hooks","reason":"Most authoritative"}]' \
--missing-content '[
{"topic":"useDeferredValue","description":"No example of useDeferredValue with Suspense"},
{"topic":"useTransition","description":"No coverage of useTransition for routing"}
]' \
--query-suggestions "Boost react.dev for queries about react hooks" \
--silent &
# Results were partially useful — multiple missing topics, one entry per topic
firecrawl search-feedback "$SEARCH_ID" \
--rating partial \
--missing-content '[
{"topic":"useDeferredValue"},
{"topic":"useTransition","description":"Need React 18+ examples"},
{"topic":"Server Components hooks"}
]' \
--silent &
# Quick form — repeat --missing-content or use comma-separated topics
firecrawl search-feedback "$SEARCH_ID" \
--rating bad \
--missing-content "official api reference: missing v2 endpoints" \
--missing-content "code examples in python" \
--silent &
--missing-content accepts:
{topic, description?} objects (richest, preferred)"topic: description" strings (shorthand)"topic1, topic2, topic3" (when you only have topic names)--missing-content flags--silent suppresses output and & runs it in the background so feedback never blocks you.