firecrawl-common-errors
Diagnose and fix Firecrawl common errors and API response codes. Use when encountering Firecrawl errors, debugging failed scrapes, or troubleshooting crawl job issues. Trigger with phrases like "firecrawl error", "fix firecrawl", "firecrawl not working", "debug firecrawl", "firecrawl 429", "firecrawl 402".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%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-structured skill description with strong completeness and excellent trigger term coverage. The explicit 'Use when' and 'Trigger with' clauses make it easy for Claude to select appropriately. The main weakness is that the capability description could be more specific about what concrete diagnostic or fix actions the skill performs beyond the general 'diagnose and fix'.
Suggestions
Add more specific concrete actions such as 'interpret rate limit (429) errors, resolve payment/credit (402) issues, retry failed crawl jobs, and parse API error responses' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Firecrawl errors/API response codes) and two actions (diagnose and fix), but doesn't list specific concrete actions like interpreting rate limits, handling authentication errors, or retrying failed jobs. | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and fix Firecrawl common errors and API response codes) and 'when' (encountering errors, debugging failed scrapes, troubleshooting crawl job issues) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'firecrawl error', 'fix firecrawl', 'firecrawl not working', 'debug firecrawl', and specific error codes like '429' and '402'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — Firecrawl is a specific tool, and the description targets a clear niche of error diagnosis and troubleshooting for that tool. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 diagnostic reference skill with excellent actionability — every error scenario includes exact error messages, executable diagnostic commands, and concrete fixes. The consistent structure (error → cause → code → fix) makes it easy to navigate. Minor weaknesses include some redundancy between the summary table and detailed sections, slight verbosity in the overview/prerequisites, and the content could benefit from better progressive disclosure for its length.
Suggestions
Remove the Prerequisites section — Claude already knows about SDK installation and env vars, and these are implied by the error fixes themselves.
Consider moving the comprehensive error handler and the summary table into a linked reference file to reduce the main file length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of code examples and tables, but includes some unnecessary sections like 'Prerequisites' (Claude knows SDK needs to be installed) and the 'Overview' paragraph that restates what the skill already does. The summary table partially duplicates the detailed sections above it. | 2 / 3 |
Actionability | Excellent actionability — every error includes the exact error message, a concrete cause, executable code to diagnose or fix the issue, and a clear fix statement. The bash and TypeScript examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | For a diagnostic/reference skill, the workflow is clear: each error follows a consistent pattern (error message → cause → diagnostic code → fix). The Quick Diagnostic section provides a sequenced troubleshooting flow. The summary table provides clear retryable/non-retryable guidance. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a summary table, but it's a fairly long monolithic file. The error reference table and detailed error sections have some redundancy. The 'Next Steps' reference to 'firecrawl-debug-bundle' is vague and not a proper link. Some content like the comprehensive error handler could be in a separate file. | 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
70e9fa4
- 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.