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".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a well-crafted skill description that clearly defines its scope around Firecrawl reliability patterns with specific actions, explicit 'Use when' guidance, and dedicated trigger phrases. It uses proper third-person voice and is concise without being vague. The description effectively carves out a distinct niche that would be easy for Claude to differentiate from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: circuit breakers, crawl fallbacks, and content validation. Also mentions crawl-to-scrape fallback and content quality gates. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement circuit breakers, crawl fallbacks, content validation) and 'when' (building fault-tolerant scraping pipelines, implementing crawl-to-scrape fallback, adding content quality gates), with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes a rich set of natural trigger terms: 'firecrawl reliability', 'firecrawl circuit breaker', 'firecrawl fallback', 'firecrawl resilience', 'firecrawl fault tolerant', plus contextual phrases like 'fault-tolerant scraping pipelines' and 'content quality gates'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining Firecrawl specifically with reliability patterns. The triggers are specific enough (e.g., 'firecrawl circuit breaker', 'firecrawl fallback') that they are unlikely to conflict with general web scraping or other Firecrawl skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with complete, executable TypeScript implementations for each reliability pattern. The workflow is well-sequenced with explicit validation checkpoints and error recovery. The main weaknesses are that the content is somewhat long for a single SKILL.md (could benefit from splitting into bundle files) and the overview includes some unnecessary context-setting.
Suggestions
Trim the overview paragraph to remove explanations of Firecrawl's model that Claude can infer from the code itself.
Consider splitting the circuit breaker, credit guard, and validation patterns into separate bundle files referenced from the main SKILL.md to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code, but the overview paragraph explains things Claude would already know (e.g., 'Firecrawl's async crawl model, JS rendering, and credit-based pricing create specific reliability challenges'). Some inline comments are helpful but the overall content is quite long (~200 lines of code) and could be tightened. | 2 / 3 |
Actionability | Every step provides fully executable TypeScript code with concrete implementations—circuit breaker, content validation, crawl-to-scrape fallback, and credit guard. The code is copy-paste ready with real Firecrawl API calls, specific thresholds, and complete class implementations. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from basic crawl with timeout → content validation → fallback strategy → circuit breaker → credit management. Each step builds on previous ones, validation is explicit (validateContent checks at multiple points), and the error handling table provides a clear troubleshooting reference. The resilientFetch function includes a feedback loop (batch fails → individual retries with validation). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's quite monolithic—all patterns are inline in a single file with no bundle files to offload detail. The circuit breaker, credit guard, and validation patterns could each be separate reference files. The references to external docs and 'firecrawl-policy-guardrails' are good but the main file is heavy. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- Reviewed
Table of Contents
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.