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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

A highly actionable, concrete error reference with executable fixes for the most common Firecrawl failures. It is held back by mild internal redundancy and by a dangling bundle reference that weakens progressive disclosure and navigation.

Suggestions

Consolidate the redundant coverage between the per-error fixes, the Error Handling table, and the safeScrape example so each earns its place and tokens are not spent restating the same status-code handling.

Fix or remove the dangling Next Steps reference to `firecrawl-debug-bundle`, or create that bundle file and link it explicitly so progressive disclosure points to a real resource.

Add an explicit validation/checkpoint step to the Quick Diagnostic (e.g., what a healthy response looks like before proceeding) to lift workflow clarity above an implicit sequence.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and code-heavy without explaining concepts Claude already knows, but the per-error fixes, the Error Handling table, and the safeScrape example overlap, so it could be tightened rather than fully earning 'every token earns its place'.	2 / 3
Actionability	It provides fully executable curl, TypeScript, and bash snippets (backoff retry loop, credit check, diagnostic checks, npm install) that are specific and copy-paste ready.	3 / 3
Workflow Clarity	The Quick Diagnostic is numbered and the crawl-stuck section includes a polling feedback loop, but the skill is primarily a reference catalog lacking explicit validation checkpoints across a full end-to-end workflow.	2 / 3
Progressive Disclosure	Sections are well-organized, but all content is inline in a body well over 50 lines, and the Next Steps reference to `firecrawl-debug-bundle` points to a bundle file that does not exist in the skill directory, making it a dangling reference.	2 / 3
	Total	9 / 12 Passed

Description

90%

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

A strong, well-targeted description that clearly states capability, use-conditions, and natural trigger phrases for a distinct Firecrawl niche. Its only weakness is that the capability statement relies on a couple of generic verbs rather than a fuller list of concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the domain and a couple of verbs ("Diagnose and fix Firecrawl common errors and API response codes") but does not enumerate a comprehensive list of concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what it does ("Diagnose and fix Firecrawl common errors and API response codes") and when to use it ("Use when encountering Firecrawl errors, debugging failed scrapes, or troubleshooting crawl job issues") with explicit trigger phrases, satisfying both what and when.	3 / 3
Trigger Term Quality	Phrases like "firecrawl error", "fix firecrawl", "firecrawl not working", "debug firecrawl", "firecrawl 429", "firecrawl 402" are natural terms a user would actually say, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Every trigger and the described capability are Firecrawl-specific, giving it a clear niche that is unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: about 4 hours ago

Table of Contents

Discovery Implementation Validation

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.