CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a focused, highly actionable diagnostic reference with executable code for each common error and a useful status-code table. Structure is clear and efficient, with only minor redundancy and a dangling reference to a non-existent companion bundle.

Suggestions

Remove the dangling 'Next Steps' reference to firecrawl-debug-bundle since no such bundle file exists in references/scripts/assets, or add the referenced bundle.

Trim the overlap between the 401 section's curl test, the Quick Diagnostic step 1, and the safeScrape example to reduce redundancy.

Add explicit validation checkpoints (e.g., 'confirm jq .success == true before proceeding') between the Quick Diagnostic steps to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Tight error-reference sections with error text, cause, and fix avoid explaining basic concepts, but the Quick Diagnostic partly repeats the 401 curl test and the Examples section reuses the 429 backoff pattern, leaving minor trimmable redundancy.

4 / 5

Actionability

Fully executable guidance throughout — real curl endpoints, TypeScript backoff implementations, exact npm package names, and jq filters — covering the common cases (401, 402, 429, empty markdown, zero-page crawl, stuck crawl, MODULE_NOT_FOUND) with copy-paste-ready examples.

5 / 5

Workflow Clarity

The Quick Diagnostic gives a clear 3-step numbered sequence and the crawl-stuck section includes a real feedback loop (completed/failed checks with retry), but it is primarily a reference rather than a single coherent multi-step process with explicit validation checkpoints between steps.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Overview, Prerequisites, Error Reference, Quick Diagnostic, Error Handling, Examples, Resources) with no deep nesting, though the 'Next Steps' references a firecrawl-debug-bundle that does not exist among the bundle files and the bulk error reference is inlined.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-crafted: it states a clear purpose, gives explicit 'Use when' guidance, and lists concrete natural trigger phrases including specific error codes. It is highly specific to Firecrawl with minimal overlap risk.

DimensionReasoningScore

Specificity

Names the Firecrawl error domain and several concrete actions ('Diagnose and fix', 'debugging failed scrapes', 'troubleshooting crawl job issues'), but the actions are overlapping variations of diagnose/debug/fix rather than fully distinct operations, so it sits just below the comprehensive 5-anchor.

4 / 5

Completeness

Explicitly answers both what ('Diagnose and fix Firecrawl common errors and API response codes') and when ('Use when encountering Firecrawl errors...') plus concrete trigger phrases, directly matching the 5-anchor.

5 / 5

Trigger Term Quality

Provides natural trigger phrases a user would say ('firecrawl error', 'fix firecrawl', 'firecrawl not working', 'firecrawl 429', 'firecrawl 402') with good coverage including specific status codes, though a few broader synonyms like 'scrape failing' are missing.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to a specific SaaS product with distinct, product-specific triggers, giving a clear niche with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.