firecrawl-rate-limits

Implement Firecrawl rate limiting, backoff, and request queuing patterns. Use when handling 429 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".

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and concise with executable TypeScript across four rate-limiting strategies. Its main weaknesses are the absence of validation checkpoints for the batch operation and a monolithic single-file structure with no progressive disclosure into bundle files.

Suggestions

Add an explicit validation/verification step after Step 4 (batch scrape) — e.g. checking batchResult.data length and error array before proceeding — to satisfy the batch-operation feedback-loop expectation.

Split the four code patterns and the RateLimitMonitor example into reference files (e.g. references/patterns.md, references/monitoring.md) and keep SKILL.md as an overview that links one level deep, improving progressive disclosure.

Clarify that Steps 1-4 are alternative strategies to choose between rather than a strict sequence, so the workflow is not misread as a pipeline.

Dimension	Reasoning	Score
Conciseness	The body is lean: a single domain-specific overview paragraph, a concrete tiers table, and tight code blocks with inline comments that earn their place; it avoids explaining generic concepts Claude already knows.	3 / 3
Actionability	All four steps provide complete, executable TypeScript (withBackoff, p-queue setup, RateLimitTracker, batchScrapeUrls) plus concrete header-handling guidance that is copy-paste ready.	3 / 3
Workflow Clarity	Steps 1-4 are clearly labeled but read as a catalog of independent patterns rather than a sequenced pipeline, and the batch-scrape step lacks an explicit validation/verification checkpoint, capping clarity at 2 per the batch-operations guideline.	2 / 3
Progressive Disclosure	The ~180-line body is a single monolithic file with no bundle files to offload detail into; sections are well organized but content that could live in separate references (e.g. the full code patterns, monitor example) is inline, so it sits at 'some structure, could be better split'.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, well-triggered, and clearly scoped to Firecrawl rate limiting. It cleanly answers both what the skill does and when to use it with natural trigger phrases.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'rate limiting, backoff, and request queuing patterns' — matching the anchor for listing several specific capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' ('Implement Firecrawl rate limiting, backoff, and request queuing patterns') and 'when' ('Use when handling 429 errors, implementing retry logic, or optimizing API request throughput'), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say — 'firecrawl rate limit', 'firecrawl throttling', 'firecrawl 429', 'firecrawl retry', 'firecrawl backoff' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to Firecrawl rate limiting with brand-specific triggers, making it unlikely to fire for unrelated skills; uses third person/imperative voice with no first/second person.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/firecrawl-pack/skills/firecrawl-rate-limits/SKILL.md
Commit: 4c47e33

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.