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".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/firecrawl-pack/skills/firecrawl-common-errors/SKILL.mdQuality
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 trigger terms and clear completeness. Its main weakness is that the capability description could be more specific about what concrete diagnostic and fix actions it performs (e.g., handling rate limits, authentication issues, timeout errors). Overall it would perform well in skill selection scenarios.
Suggestions
Add more specific concrete actions beyond 'diagnose and fix', such as 'handle rate limiting (429), resolve payment/auth errors (402), retry failed crawl jobs, interpret API response codes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Firecrawl errors/API response codes) and some actions (diagnose, fix), but doesn't list specific concrete actions like 'handle rate limiting', 'resolve authentication errors', or 'retry failed crawl 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 when encountering issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused specifically on Firecrawl error troubleshooting. The specific tool name and error codes make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid error reference guide with excellent actionability — each error has real error messages, executable diagnostic commands, and concrete fixes. The main weaknesses are moderate verbosity (the content could be tightened by removing the overview/prerequisites and deduplicating the summary table with the detailed sections) and the lack of a clear top-level diagnostic workflow that guides Claude through a decision tree rather than presenting a flat list of errors.
Suggestions
Add a brief diagnostic decision tree at the top (e.g., 'Got a status code? → jump to section. Empty content? → see Empty Markdown. Crawl stuck? → see Crawl Stuck') to improve workflow clarity.
Remove the Prerequisites and Overview sections — Claude already knows what Firecrawl is and these consume tokens without adding actionable value.
Consider whether the summary table and the detailed sections duplicate each other; either make the table the primary quick-reference and move details to a bundle file, or remove the table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of code examples and tables, but includes some unnecessary sections like 'Prerequisites' (Claude knows these) and mild verbosity in explanations. The 'Overview' paragraph could be trimmed. 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, and a clear fix statement. Code examples are copy-paste ready with real API endpoints, proper imports, and bash safety flags. | 3 / 3 |
Workflow Clarity | The Quick Diagnostic section provides a sequential check, and individual error sections are well-structured (error → cause → fix). However, there's no explicit diagnostic workflow tying these together (e.g., 'start here, then check X if Y'). The crawl timeout fix includes a feedback loop, but other multi-step scenarios lack validation checkpoints. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and a summary table, but it's a long monolithic file (~150 lines of error reference) that could benefit from splitting detailed examples into a separate file. The reference to 'firecrawl-debug-bundle' at the end is good but no bundle files exist to support it, and the reference is vague. | 2 / 3 |
Total | 9 / 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
a04d1a2
- 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.