Implement FireCrawl rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for FireCrawl. Trigger with phrases like "firecrawl rate limit", "firecrawl throttling", "firecrawl 429", "firecrawl retry", "firecrawl backoff".
7.0
Rating
0
Installs
Backend Development
Category
Excellent skill with comprehensive coverage of FireCrawl rate limiting patterns. The description clearly triggers on relevant phrases (429 errors, throttling, backoff). Task knowledge is strong with production-ready TypeScript implementations of exponential backoff with jitter, idempotency keys, queue-based limiting, and rate limit monitoring. Structure is clean with clear sections, tables for tiers and headers, and logical progression. Novelty is solid—while retry logic exists in libraries, the FireCrawl-specific implementation with idempotency patterns, header monitoring, and queue integration provides meaningful value beyond basic CLI prompting. The skill references firecrawl-security-basics which is assumed to exist per instructions. Minor improvement possible: could add Python examples for broader applicability, but TypeScript implementation is complete and well-documented.
Loading SKILL.md…

Skill Author