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

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The body is concise and highly actionable with executable code and a clear step sequence, but it loses points on workflow clarity (no validation checkpoints on the batch indexing steps) and progressive disclosure (monolithic single file with no bundle references).

Suggestions

Add explicit validation checkpoints to the batch indexing steps (e.g. verify upsert/indexBatch succeeded and retry on failure) so the workflow has a validate→fix→retry feedback loop.

Split the detailed handler code and error-handling table into a reference file (e.g. references/handler-patterns.md) and signal it from SKILL.md, moving the body toward one-level-deep progressive disclosure.

Consider an idempotency/dedup verification step in Step 3 since the error table recommends dedup by job ID but the handler code does not demonstrate it.

DimensionReasoningScore

Conciseness

The body is lean — a one-sentence overview, tightly commented code, and compact tables — with no padded explanations of concepts Claude already knows (e.g. what webhooks or HMAC are); every section earns its tokens.

3 / 3

Actionability

Provides fully executable TypeScript (asyncCrawlUrl, Express handler, signature verification, streaming indexer, polling fallback) that is copy-paste ready with specific env vars and headers, matching the top anchor.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced and include an explicit signature-verification checkpoint and a polling-fallback error loop, but the batch indexing operations (Steps 3–4) lack explicit validation/verification checkpoints, so the batch-operations guideline caps this at 2 rather than 3.

2 / 3

Progressive Disclosure

The single ~210-line SKILL.md is well organized into sections, but no bundle files exist and all content is inline; the detailed code and error tables could be split into one-level-deep references, placing it at the 'could be better organized / content that should be separate is inline' anchor rather than 3.

2 / 3

Total

10

/

12

Passed

Description

100%

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 strong across all dimensions: it states concrete capabilities, gives explicit 'Use when' triggers with natural keyword phrases, and occupies a clear niche unlikely to conflict with other skills. It is concise without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Implement Firecrawl webhook event handling', 'setting up webhook endpoints', 'handling crawl.page/crawl.completed events', 'processing async job results in real-time' — matching the top anchor for specific concrete actions.

3 / 3

Completeness

Explicitly answers both 'what' ('Implement Firecrawl webhook event handling for async crawl and batch scrape jobs') and 'when' ('Use when setting up webhook endpoints...'), with explicit trigger guidance.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say — 'firecrawl webhook', 'firecrawl events', 'firecrawl webhook signature', 'handle firecrawl events', 'firecrawl notifications' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Firecrawl webhooks with distinct triggers; unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

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.