Agent skill

firecrawl-performance-tuning

Optimize Firecrawl scraping performance with caching, batch scraping, and format selection. Use when experiencing slow scrapes, optimizing credit usage per page, or building high-throughput scraping pipelines. Trigger with phrases like "firecrawl performance", "optimize firecrawl", "firecrawl latency", "firecrawl caching", "firecrawl slow", "firecrawl batch". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-performance-tuning --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Version: 1.11.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEdit
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: skills/.curated/firecrawl-performance-tuning/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Firecrawl Performance Tuning ## Overview Optimize Firecrawl API performance by choosing efficient scraping modes, caching results, using batch endpoints, and minimizing unnecessary rendering. Key levers: format selection (markdown vs HTML vs screenshot), `waitFor` tuning, `onlyMainContent`, and batch vs individual scraping. ## Latency Benchmarks | Operation | Typical | With JS Wait | With Screenshot | |-----------|---------|--------------|-----------------| | scrapeUrl (markdown) | 2-5s | 5-10s | 8-15s | | scrapeUrl (extract) | 3-8s | 8-15s | N/A | | crawlUrl (10 pages) | 20-40s | 40-80s | N/A | | mapUrl | 1-3s | N/A | N/A | | batchScrapeUrls (10) | 10-20s | 20-40s | N/A | ## Instructions ### Step 1: Minimize Formats (Biggest Win) ```typescript import FirecrawlApp from "@mendable/firecrawl-js"; const firecrawl = new FirecrawlApp({ apiKey: process.env.FIRECRAWL_API_KEY!, }); // SLOW: requesting everything const slow = await firecrawl.scrapeUrl(url, { formats: ["markdown", "html", "links", "screenshot"], // screenshot + full HTML = 3-5x slower }); // FAST: request only what you need const fast = await firecrawl.scrapeUrl(url, { formats: ["markdown"], // markdown only = fastest only

What's inside
Steps it walks through
  1. Overview
  2. Latency Benchmarks
  3. Instructions
  4. Step 1: Minimize Formats (Biggest Win)
  5. Step 2: Tune waitFor for JS-Heavy Pages
  6. Step 3: Cache Scraped Content
  7. Step 4: Use Batch Scrape for Multiple URLs
  8. Step 5: Map Before Crawl (Save Credits)
  9. Step 6: Measure Scrape Performance
  10. Error Handling
  11. Examples
  12. Performance Comparison Script
  13. Resources
  14. Next Steps
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the firecrawl-performance-tuning skill do?

Optimize Firecrawl scraping performance with caching, batch scraping, and format selection. Use when experiencing slow scrapes, optimizing credit usage per page, or building high-throughput scraping pipelines. Trigger with phrases like "firecrawl performance", "optimize firecrawl", "firecrawl latency", "firecrawl caching", "firecrawl slow", "firecrawl batch". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-performance-tuning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going