CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-webhooks-events

Implement Firecrawl webhook event handling for async crawl and batch scrape jobs. Use when setting up webhook endpoints, handling crawl.page/crawl.completed events, or processing async job results in real-time. Trigger with phrases like "firecrawl webhook", "firecrawl events", "firecrawl webhook signature", "handle firecrawl events", "firecrawl notifications".

71

Quality

88%

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

76%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 highly actionable with executable code and a clear step sequence, but the batch webhook-processing workflow omits an explicit idempotency/validation loop in the code itself, capping workflow clarity. Structure is good though somewhat monolithic.

Suggestions

Add an explicit dedup/idempotency check (e.g., track seen job/event IDs) inside the handler code rather than only mentioning it in the error-handling table, so the batch workflow has a real validation feedback loop.

Consider moving the full code examples or the polling-fallback section into a reference file, keeping SKILL.md a leaner overview with one-level-deep pointers.

Tighten the Overview paragraph to remove context Claude already knows about webhooks vs. polling.

DimensionReasoningScore

Conciseness

Mostly lean, code-driven content that assumes competence; the Overview paragraph and a few inline comments slightly over-explain context Claude could infer, keeping it just below the top anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript covering start crawl, signature-verified handler, page/completion/failure processing, and polling fallback — specific examples cover the common cases.

5 / 5

Workflow Clarity

Steps 1-5 give a clear sequence and signature verification is a checkpoint, but this batch-indexing workflow lacks an explicit validation/feedback loop (idempotency/dedup is only mentioned in the error table, not enforced in code), capping it per the batch-operation rule.

3 / 5

Progressive Disclosure

Well-organized sections with one-level external doc links and a Next Steps pointer to another skill; no nested references, though the code-heavy body could arguably split some detail into reference files.

4 / 5

Total

16

/

20

Passed

Description

100%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 a strong, well-structured trigger description that clearly answers what the skill does and when to use it, with natural trigger phrases and a distinct niche. Third-person/imperative voice is consistent with the good examples.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'set up webhook endpoints', 'handling crawl.page/crawl.completed events', 'processing async job results in real-time' — with comprehensive coverage of this niche, matching the top anchor.

5 / 5

Completeness

Explicitly states what ('Implement Firecrawl webhook event handling for async crawl and batch scrape jobs') and when ('Use when setting up webhook endpoints...'), plus concrete trigger phrases — both anchors fully satisfied.

5 / 5

Trigger Term Quality

Five natural trigger phrases including synonyms (webhook/events/notifications) and the specific 'firecrawl webhook signature'; users would naturally say these, matching comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

Firecrawl-specific webhook niche with distinct 'firecrawl webhook'/'firecrawl events' triggers; minimal overlap risk with other skills.

5 / 5

Total

20

/

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.