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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

A practical, code-heavy skill with strong executable examples and decent organization. Its main weaknesses are mild verbosity, lack of validation checkpoints around batch operations, and a monolithic single-file structure with no progressive disclosure into bundle files.

Suggestions

Tighten the Overview and inline code comments to remove context Claude already knows (e.g., what a 429/Retry-After is), pushing conciseness toward the lean anchor.

Add an explicit validation/feedback step for the batch scrape path (e.g., check batchResult.success and retry failed URLs) so the batch workflow has a checkpoint.

Move the rate-limit monitor example and the error-handling header table into a reference file under references/, linking from SKILL.md, to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code and a compact tiers table, but includes restated explanations (e.g., the Overview sentence re-explaining 429/Retry-After, code comments like "to prevent thundering herd") that could be trimmed; not quite the lean level-3 anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript across four patterns (withBackoff, p-queue concurrency, RateLimitTracker, batchScrapeUrls) with concrete configuration values, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Steps are labeled Step 1–4 but are really independent alternative patterns rather than a sequenced process, and the batch operation has no validation/verification checkpoint; per the batch-operations guideline this caps clarity at 2.	2 / 3
Progressive Disclosure	Well-organized into sections, but everything lives inline in one ~180-line SKILL.md with no bundle files (references/scripts/assets absent); content such as the monitor example or error-handling reference could be split out, matching the some-structure level-2 anchor.	2 / 3
	Total	9 / 12 Passed

Description

100%

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

A strong, well-scoped description that states concrete capabilities, gives an explicit Use-when clause, and supplies natural trigger phrases. Voice is imperative/third-person with no first- or second-person phrasing to penalize.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: "rate limiting, backoff, and request queuing patterns" plus "handling 429 errors, implementing retry logic, or optimizing API request throughput," matching the multiple-specific-actions anchor rather than the partial level 2.	3 / 3
Completeness	Explicitly answers both what ("Implement Firecrawl rate limiting, backoff, and request queuing") 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 phrases a user would actually say — "firecrawl rate limit", "firecrawl throttling", "firecrawl 429", "firecrawl retry", "firecrawl backoff" — giving good coverage of common variations, not just jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Firecrawl rate limiting) with distinct firecrawl-prefixed triggers, making it unlikely to fire for unrelated skills.	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
Commit: 50ab626

Reviewed: about 16 hours 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.