Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Search the web and scrape pages into clean markdown with the Firecrawl API — query-based discovery, single-URL extraction including public PDFs, driven by curl with a vault-stored API key.
.claude/skills/prism-shadow-firecrawl/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | -18% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -7% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 10% | 0% |
| case-13 | ✗→✓ | ▲ Improved | 22% | 0% |
| case-16 | ✗→✓ | ▲ Improved | -42% | 0% |
Firecrawl turns the live web into agent-ready markdown over a plain REST API (https://api.firecrawl.dev/v2, Authorization: Bearer $FIRECRAWL_API_KEY). Two calls cover most web work: /search to discover pages by query, /scrape to extract clean content from a URL you already have. Use it whenever a task needs current web information or the content of a specific page.
If the user's message only invokes this skill (e.g. "use firecrawl skill") without a concrete task, ask what they want to search or scrape. When the task is concrete, check the credential first:
bash[ -n "$FIRECRAWL_API_KEY" ] && echo ok || echo missing
If missing (also visible in your Vault Keys section), ask the user to add FIRECRAWL_API_KEY to this agent's key vault — gear icon on the agent card → settings → key vault tab; keys come from the Firecrawl dashboard (https://www.firecrawl.dev/signin). Vault values reach your shell environment on the next task. Only fall back to the keyless tier (below) when the user cannot provide a key right now.
bashcurl -sS -X POST https://api.firecrawl.dev/v2/search \ -H "Authorization: Bearer $FIRECRAWL_API_KEY" -H "content-type: application/json" \ -d '{"query": "<what you are looking for>", "limit": 5}' \ | jq '[.data.web[] | {url, title, description}]'
.data.web[], each with url / title / description; limit defaults to 10 (per source)."scrapeOptions": {"formats": ["markdown"]} returns each result's page content inline — prefer the two-step search → scrape flow instead when only a hit or two matters; content-included search costs far more credits and context."sources": [{"type": "news"}] (or images), "includeDomains": ["docs.example.com"], "categories": ["github"] (or research / pdf), "tbs" for time-bounded queries.bashcurl -sS -X POST https://api.firecrawl.dev/v2/scrape \ -H "Authorization: Bearer $FIRECRAWL_API_KEY" -H "content-type: application/json" \ -d '{"url": "<page url>"}' \ | jq -r '.data.markdown' > <topic>.md
onlyMainContent defaults to true). Metadata sits in .data.metadata (title, sourceURL, statusCode)."waitFor": 2000.Search first for discovery, scrape once you have the URL. Never dump full page markdown into your context or reply: pipe it to a file (as above) and read the relevant parts with shell (grep/sed), then cite metadata.sourceURL for every claim you take from a page.
The keyless free tier only works through official Firecrawl clients and is rate-limited:
bashnpx -y firecrawl-cli@latest search "<query>" npx -y firecrawl-cli@latest scrape <url> -o page.md
Use it as a stopgap and tell the user to add a real key to the vault — accounts unlock the full API and higher limits.
401 — missing/invalid key: re-check the vault entry name FIRECRAWL_API_KEY.402 / 429 — out of credits or rate-limited: report to the user; do not retry-loop.https://docs.firecrawl.dev is the source of truth for request/response schemas.| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-02 | fail→fail | 16,501 | 9,332 | -43% | 1 | 1 | 0% | 438 | 1,170 | +167% | 0 | 0 | — |
case-03 | fail→fail | 16,817 | 9,566 | -43% | 1 | 1 | 0% | 516 | 1,146 | +122% | 0 | 0 | — |
case-01 | fail→fail | 8,025 | 14,247 | +78% | 1 | 1 | 0% | 556 | 1,156 | +108% | 0 | 0 | — |
case-04 | fail→fail | 18,095 | 15,363 | -15% | 1 | 1 | 0% | 2,337 | 1,222 | -48% | 0 | 0 | — |
case-05 | fail→fail | 15,519 | 23,827 | +54% | 1 | 1 | 0% | 1,888 | 1,343 | -29% | 0 | 0 | — |
case-06 | fail→pass | 9,551 | 2,762 | -71% | 1 | 1 | 0% | 1,858 | 1,518 | -18% | 0 | 0 | — |
case-07 | fail→pass | 7,470 | 7,589 | +2% | 1 | 1 | 0% | 1,551 | 1,447 | -7% | 0 | 0 | — |
case-08 | pass→pass | 17,492 | 3,542 | -80% | 1 | 1 | 0% | 2,204 | 1,588 | -28% | 0 | 0 | — |
case-09 | pass→pass | 9,109 | 7,415 | -19% | 1 | 1 | 0% | 1,527 | 1,383 | -9% | 0 | 0 | — |
case-10 | pass→pass | 15,027 | 8,323 | -45% | 1 | 1 | 0% | 1,959 | 1,610 | -18% | 0 | 0 | — |
case-11 | pass→pass | 11,708 | 9,778 | -16% | 1 | 1 | 0% | 1,969 | 1,855 | -6% | 0 | 0 | — |
case-12 | fail→pass | 7,225 | 2,682 | -63% | 1 | 1 | 0% | 1,369 | 1,509 | +10% | 0 | 0 | — |
case-13 | fail→pass | 13,281 | 3,855 | -71% | 1 | 1 | 0% | 1,336 | 1,624 | +22% | 0 | 0 | — |
case-14 | pass→pass | 13,608 | 7,577 | -44% | 1 | 1 | 0% | 1,634 | 1,384 | -15% | 0 | 0 | — |
case-15 | pass→pass | 16,635 | 12,301 | -26% | 1 | 1 | 0% | 1,979 | 2,067 | +4% | 0 | 0 | — |
case-16 | fail→pass | 19,611 | 9,085 | -54% | 1 | 1 | 0% | 3,005 | 1,739 | -42% | 0 | 0 | — |
case-17 | fail→pass | 11,426 | 5,581 | -51% | 1 | 1 | 0% | 2,030 | 1,861 | -8% | 0 | 0 | — |
case-18 | fail→pass | 10,537 | 9,755 | -7% | 1 | 1 | 0% | 1,870 | 1,626 | -13% | 0 | 0 | — |
case-19 | pass→pass | 18,202 | 10,367 | -43% | 1 | 1 | 0% | 2,271 | 1,856 | -18% | 0 | 0 | — |
case-20 | pass→pass | 7,747 | 6,737 | -13% | 1 | 1 | 0% | 422 | 1,228 | +191% | 0 | 0 | — |
case-21 | fail→pass | 11,983 | 7,683 | -36% | 1 | 1 | 0% | 1,286 | 1,326 | +3% | 0 | 0 | — |
case-22 | pass→pass | 8,746 | 14,947 | +71% | 1 | 1 | 0% | 1,875 | 2,850 | +52% | 0 | 0 | — |
case-23 | pass→pass | 12,741 | 7,324 | -43% | 1 | 1 | 0% | 1,381 | 2,422 | +75% | 0 | 0 | — |
case-24 | pass→pass | 10,914 | 17,125 | +57% | 1 | 1 | 0% | 2,235 | 3,259 | +46% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 24 cases were attempted, and 19 counted toward the lift figure. The other 5 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +33 percentage points is the difference between those two pass rates over the 19 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.