CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-sdk-patterns

Apply production-ready Firecrawl SDK patterns for TypeScript and Python. Use when implementing Firecrawl integrations, building reusable scraping services, or establishing team coding standards for Firecrawl. Trigger with phrases like "firecrawl SDK patterns", "firecrawl best practices", "firecrawl code patterns", "idiomatic firecrawl", "firecrawl wrapper".

67

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

65%

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

The body delivers excellent, executable code patterns but is held back by redundant summary sections, the absence of validation feedback loops, and a monolithic inline structure with no bundle references. It is a solid, actionable skill that would benefit from tighter prose and file-based offloading.

Suggestions

Remove or merge the "Output" and "Error Handling" sections, since they restate behavior already shown in the code; let the code and comments carry that information.

Add an explicit validation/retry checkpoint for the batch scrapeMany path (e.g., verify each ScrapeResult before resolving, or surface partial failures) so the workflow has a feedback loop.

Move the factory-pattern example and the longer code listings into a references/ file (e.g., EXAMPLES.md) and link to it, keeping SKILL.md as a lean overview that enables progressive disclosure.

DimensionReasoningScore

Conciseness

Code blocks are lean and skip explanations Claude already knows, but the "Output", "Error Handling" table, and "Examples" sections restate what the code already shows (e.g., "Automatic retry with exponential backoff + jitter" duplicates Step 3), so it is mostly efficient but could be tightened.

2 / 3

Actionability

Every step provides complete, executable TypeScript/Python with imports and full function bodies that are copy-paste ready, matching the score-3 anchor and well above the pseudocode/incomplete score-2 case.

3 / 3

Workflow Clarity

Steps are clearly numbered 1–6, but these are independent building blocks rather than a fragile pipeline, and there are no validation checkpoints or feedback loops — even for the batch scrapeMany path — so checkpoints are missing or implicit per the score-2 anchor.

2 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent), yet all code lives inline in a single ~245-line file; the factory-pattern example and full code blocks could be split into one-level-deep references, so it has some structure but content that should be separate is inline.

2 / 3

Total

9

/

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: it states concrete capabilities, gives explicit 'Use when' triggers, and lists natural trigger phrases in a distinct niche. Voice is third person throughout, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "implementing Firecrawl integrations, building reusable scraping services, or establishing team coding standards" — matching the score-3 anchor rather than the partial coverage of score 2.

3 / 3

Completeness

Explicitly answers both what ("Apply production-ready Firecrawl SDK patterns") and when ("Use when implementing Firecrawl integrations...") with an explicit trigger clause, matching the score-3 anchor exactly.

3 / 3

Trigger Term Quality

Provides five natural trigger phrases ("firecrawl SDK patterns", "firecrawl best practices", "firecrawl code patterns", "idiomatic firecrawl", "firecrawl wrapper") a user would plausibly say, exceeding the single-keyword score-2 anchor.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Firecrawl SDK patterns specifically) with distinct triggers unlikely to fire for unrelated skills, matching the score-3 anchor rather than the overlapping score-2 case.

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.