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

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

70%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 body is highly actionable with five executable, well-structured TypeScript patterns and a useful error-handling table, but it stays monolithic rather than progressively disclosing detail into reference files and lacks explicit validation feedback loops in its batch/fallback workflows.

Suggestions

Move the longer code patterns (circuit breaker, credit guard) into a references/ file and keep SKILL.md as an overview with one-level-deep links, improving progressive disclosure.

Add explicit validate-fix-retry feedback checkpoints to the resilientFetch and budgetedCrawl workflows (e.g., 'if validateContent fails, retry with waitFor; if still failing, skip and log') to support batch operations.

Trim the Overview's explanation of Firecrawl's async/credit model since Claude can infer it; lead with what the skill provides.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code, but the Overview re-explains Firecrawl's async model and credit pricing that Claude could infer, and inline comments add some padding; could be tightened.	2 / 3
Actionability	Five complete, executable TypeScript code blocks (reliableCrawl, validateContent, resilientFetch, FirecrawlCircuitBreaker, CreditGuard) that are copy-paste ready with specific APIs and parameters.	3 / 3
Workflow Clarity	Steps are sequenced (Step 1–5) but batch/destructive-style operations like resilientFetch and budgetedCrawl lack explicit validate-fix-retry feedback checkpoints; the validation helper exists but is not framed as an error-recovery loop.	2 / 3
Progressive Disclosure	Content is well-sectioned but everything is inline in one ~270-line file with no bundle references; the 'Next Steps' pointer to another skill is one-level but external, so structure could be better split for a skill this size.	2 / 3
	Total	9 / 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.

A strong description: it names concrete capabilities, provides explicit 'Use when' guidance, and lists natural trigger phrases that would surface the skill for the right requests. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'circuit breakers, crawl fallbacks, and content validation' plus 'crawl-to-scrape fallback' and 'content quality gates', matching the multiple-specific-actions anchor.	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.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say ('firecrawl reliability', 'firecrawl circuit breaker', 'firecrawl fallback', 'firecrawl resilience', 'firecrawl fault tolerant') with good coverage.	3 / 3
Distinctiveness Conflict Risk	Clear Firecrawl-specific niche with distinct trigger phrases; unlikely to conflict with non-scraping skills, though 'reliability patterns' could overlap with general fault-tolerance 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
Path: plugins/saas-packs/firecrawl-pack/skills/firecrawl-reliability-patterns/SKILL.md
Commit: 4c47e33

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