firecrawl-common-errors
Diagnose and fix FireCrawl common errors and exceptions. Use when encountering FireCrawl errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "firecrawl error", "fix firecrawl", "firecrawl not working", "debug firecrawl".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-common-errors75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excellent trigger terms and clear 'what/when' guidance. The main weakness is the lack of specific concrete actions - it could benefit from listing specific error types or fixes it handles (e.g., 'rate limiting errors', 'authentication failures', 'timeout issues').
Suggestions
Add specific error types or scenarios handled, such as 'rate limiting errors, authentication failures, timeout issues, malformed responses' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (FireCrawl) and general actions ('diagnose and fix', 'debugging failed requests', 'troubleshooting integration issues'), but doesn't list specific concrete actions like particular error types handled or specific fixes provided. | 2 / 3 |
Completeness | Clearly answers both what ('Diagnose and fix FireCrawl common errors and exceptions') and when ('Use when encountering FireCrawl errors, debugging failed requests, or troubleshooting integration issues') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say: 'firecrawl error', 'fix firecrawl', 'firecrawl not working', 'debug firecrawl'. These are realistic phrases users would type when encountering issues. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on FireCrawl errors specifically. The explicit tool name and error-focused triggers make it unlikely to conflict with general debugging skills or other web scraping tools. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structure and organization but underdelivers on its promise of covering 'top 10 most common errors' - only 3 are documented. The framing sections (Overview, Prerequisites, Instructions, Output) add boilerplate without value. The actual error solutions are reasonable but lack verification steps to confirm fixes worked.
Suggestions
Remove the generic Instructions steps 1-3 and Output section - they describe obvious actions Claude already knows
Add the missing 7 errors to fulfill the 'top 10' promise, or change the overview to accurately reflect content
Add verification commands after each solution (e.g., 'Verify fix: curl -H "Authorization: Bearer $FIRECRAWL_API_KEY" https://api.firecrawl.com/health')
Inline the rate limit exponential backoff solution rather than deferring to another skill for this common case
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary scaffolding (Overview, Prerequisites, Instructions steps 1-3, Output section) that adds little value. The actual error solutions are reasonably concise, but the framing could be tightened. | 2 / 3 |
Actionability | Provides some executable commands (curl, bash, typescript) but only covers 3 errors despite claiming 'top 10'. The rate limit solution defers to another skill rather than providing inline guidance. Missing concrete solutions for 7 promised errors. | 2 / 3 |
Workflow Clarity | The 3-step diagnostic process is clear but generic. Individual error solutions lack verification steps - after applying a fix, there's no guidance on confirming resolution. The escalation path is helpful but disconnected from the error-specific workflows. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections. References to external resources and related skills (firecrawl-rate-limits, firecrawl-debug-bundle) are well-signaled and one level deep. Content is appropriately organized for quick scanning. | 3 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.