CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-advanced-troubleshooting

Debug hard-to-diagnose Firecrawl issues with systematic isolation and evidence collection. Use when standard troubleshooting fails, investigating why scrapes return empty content, crawl jobs hang, or webhooks don't fire. Trigger with phrases like "firecrawl hard bug", "firecrawl mystery error", "firecrawl impossible to debug", "firecrawl deep debug", "firecrawl not scraping".

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

A highly actionable, well-organized debugging skill built from executable code that covers the stated failure modes, with a useful error table and escalation template. The main gaps are minor overlap between Step 1 and Step 2 code and the absence of explicit error-recovery feedback loops in the workflow narrative.

Suggestions

Collapse the Step 1 minimal reproduction into the Step 2 diagnose() function to remove overlapping scrape calls and tighten token use.

Add an explicit validate→fix→retry loop after the error-handling table (e.g., 'After applying a fix, re-run diagnose(url) and confirm all layers pass before escalating') to strengthen the workflow's feedback structure.

Fill the YOUR-FAILING-URL.com / YOUR-URL.com placeholders with a note to substitute the real target, or accept the URL as a function argument consistently, so the snippets are runnable without edits.

DimensionReasoningScore

Conciseness

The body is almost entirely executable TypeScript with brief comments and a one-sentence overview, assuming Claude's competence rather than explaining what Firecrawl is; minor trimming is possible since the Step 1 minimal-repro tests overlap with the Step 2 diagnose() layers.

4 / 5

Actionability

Five copy-paste-ready TypeScript functions cover the common failure modes (empty scrapes, stuck crawls, timing, webhooks) alongside a concrete error-cause-solution table and a fill-in escalation template — fully executable with specific examples.

5 / 5

Workflow Clarity

Steps 1–5 are clearly numbered and the layer-by-layer diagnose() uses pass/fail results with early returns as implicit checkpoints; it stops short of explicit validate→fix→retry feedback-loop framing, and the read-only diagnostic nature means the destructive-cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist, so the single self-contained SKILL.md is appropriately organized into Overview, Instructions, Error Handling, Escalation, Resources, and Next Steps with clearly signaled external links; the inline code is core instruction rather than misplaced reference material.

4 / 5

Total

17

/

20

Passed

Description

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

A strong, well-structured description that clearly states what it does and when to use it, with explicit trigger phrases and a distinct Firecrawl-specific niche. The main weakness is that the 'what' line uses generic debugging verbs rather than the concrete techniques the skill actually delivers.

Suggestions

Replace generic verbs in the opening line with the specific techniques the skill teaches, e.g. 'Debug hard-to-diagnose Firecrawl issues by isolating scrape layers, inspecting HTML-vs-markdown mismatches, and analyzing crawl job status.'

Swap artificial triggers like 'firecrawl impossible to debug' / 'firecrawl deep debug' for phrases users actually say, such as 'firecrawl returning empty', 'firecrawl crawl stuck', or 'firecrawl webhook not firing'.

DimensionReasoningScore

Specificity

Names the Firecrawl-debugging domain and two actions ('systematic isolation and evidence collection'), but those actions are generic debugging verbs rather than the specific techniques (waitFor, actions, map endpoint) the body actually teaches, so coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers both 'what' ('Debug hard-to-diagnose Firecrawl issues with systematic isolation and evidence collection') and 'when' ('Use when standard troubleshooting fails...') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Provides five explicit trigger phrases plus natural symptom terms ('scrapes return empty content', 'crawl jobs hang', 'webhooks don't fire'); a few phrases like 'firecrawl impossible to debug' and 'firecrawl deep debug' are more artificial than what users naturally say, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Tightly niched to Firecrawl debugging with 'firecrawl' embedded in every trigger phrase and symptom, giving it a clear niche with minimal conflict risk against non-Firecrawl skills.

5 / 5

Total

17

/

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.