firecrawl-reliability-patterns

Implement Firecrawl reliability patterns: circuit breakers, crawl fallbacks, and content validation. Use when building fault-tolerant scraping pipelines, implementing crawl-to-scrape fallback, or adding content quality gates to Firecrawl integrations. Trigger with phrases like "firecrawl reliability", "firecrawl circuit breaker", "firecrawl fallback", "firecrawl resilience", "firecrawl fault tolerant".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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 code and clear validation-backed workflows. Its main weakness is progressive disclosure: everything lives in a single monolithic SKILL.md with no bundle references to offload the larger patterns.

Suggestions

Move the larger, reusable patterns (Circuit Breaker, CreditGuard) into reference files under references/ and link to them one level deep, keeping SKILL.md as a concise overview.

Add an explicit validate->fix->retry checkpoint sequence for batch crawls so the feedback loop is procedural rather than implicit in resilientFetch.

Trim the Overview paragraph to the domain-specific reliability challenges Claude would not already know (credit-based pricing, async crawl model) to further tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable TypeScript with terse inline comments that earn their place; it assumes Claude's competence and avoids restating generic concepts, with only a short domain-specific overview framing the problem.	3 / 3
Actionability	Five fully executable TypeScript code blocks (reliableCrawl, validateContent, resilientFetch, FirecrawlCircuitBreaker, CreditGuard) provide copy-paste-ready, concrete guidance with specific API calls and parameters.	3 / 3
Workflow Clarity	Steps are explicitly sequenced (1-5), with validation checkpoints via validateContent and feedback loops in the crawl-to-scrape fallback (batch threshold check then individual retries), so batch operations are not left without validation.	3 / 3
Progressive Disclosure	No bundle files exist and all substantial content (circuit breaker, credit guard, validation) is inline in a ~270-line monolithic body; well-sectioned but content that could be split into one-level-deep references is not separated, matching the "structure present but should be separate is inline" anchor rather than the cap-triggering deeply-nested case.	2 / 3
	Total	11 / 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.

The description is well-crafted: it states concrete capabilities, includes explicit "Use when" triggers with natural keyword variations, and occupies a clear niche unlikely to conflict with other skills. It cleanly satisfies all four dimensions.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions: "circuit breakers, crawl fallbacks, and content validation", matching the anchor for listing several specific concrete actions rather than a single vague domain.	3 / 3
Completeness	Explicitly answers both "what" (Implement Firecrawl reliability patterns: circuit breakers, crawl fallbacks, and content validation) and "when" ("Use when building fault-tolerant scraping pipelines..."), with explicit trigger guidance, so it is not capped at 2.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say ("firecrawl reliability", "firecrawl circuit breaker", "firecrawl fallback", "firecrawl resilience", "firecrawl fault tolerant"), giving good coverage of likely utterances.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Firecrawl reliability with distinctive 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: 6e3a65f

Reviewed: 4 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.