CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-load-scale

Load test and scale Firecrawl scraping pipelines with concurrency control and batching. Use when testing scraping throughput, planning capacity for large crawl jobs, or optimizing concurrent scrape performance. Trigger with phrases like "firecrawl load test", "firecrawl scale", "firecrawl throughput", "firecrawl capacity", "firecrawl concurrent".

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%Weight 40%Scale 1-3

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

The content is lean and highly actionable with five executable TypeScript examples, but its batch/load-testing workflow lacks explicit validation checkpoints, and a single ~220-line file with inline code blocks underuses progressive disclosure.

Suggestions

Add an explicit validate-and-retry feedback loop to the load-testing steps (e.g., detect 429 responses, back off, and re-queue) so batch operations have a real checkpoint.

Move the larger code examples (queue-based scraping, async crawl polling) into a referenced file such as references/scaling-examples.ts and link from a concise overview to improve progressive disclosure.

Include a short pre-flight check step (verify FIRECRAWL_API_KEY is set and the plan's RPM/concurrency limits before running) as the first workflow checkpoint.

DimensionReasoningScore

Conciseness

The body is code-heavy with minimal explanatory padding; the overview is a single tight paragraph and the rate-limit table is dense and useful, with no explanation of basic concepts Claude already knows.

3 / 3

Actionability

Five complete, executable TypeScript snippets (baseline measurement, batch scrape, p-queue, parallel async crawls, capacity planning) plus an error-handling table and a quick load-test example make the guidance copy-paste ready.

3 / 3

Workflow Clarity

A clear 5-step sequence is present, but these batch/load operations against a rate-limited API lack explicit validation checkpoints or a validate-fix-retry feedback loop woven into the steps, which caps the score per the batch-operations guideline.

2 / 3

Progressive Disclosure

Sections are well organized and external doc links are clearly signaled, but no bundle files exist and the five substantial code blocks sit inline in a single >50-line file rather than being split into referenced materials.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concise, concrete, and fully answers both what the skill does and when to use it, with natural trigger phrases and a clear Firecrawl-specific niche. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Names several concrete actions — "Load test and scale Firecrawl scraping pipelines with concurrency control and batching" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (load test and scale scraping pipelines) and when ("Use when testing scraping throughput, planning capacity for large crawl jobs, or optimizing concurrent scrape performance").

3 / 3

Trigger Term Quality

Five natural trigger phrases ("firecrawl load test", "firecrawl scale", "firecrawl throughput", "firecrawl capacity", "firecrawl concurrent") that a user would plausibly say.

3 / 3

Distinctiveness Conflict Risk

Tied to the specific Firecrawl tool with distinct, tool-qualified triggers, making conflict with unrelated skills unlikely.

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.