CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-core-workflow-a

Execute Firecrawl primary workflow: scrape and crawl websites into LLM-ready markdown. Use when scraping single pages, crawling entire sites, or building content ingestion pipelines with Firecrawl's scrapeUrl and crawlUrl methods. Trigger with phrases like "firecrawl scrape", "firecrawl crawl site", "scrape page to markdown", "crawl documentation".

74

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

87%

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

A well-structured, executable Firecrawl workflow with lean code examples and good organization. Its main gap is the absence of validation/feedback checkpoints for the batch crawl operations, which keeps workflow clarity at the mid-tier despite strong sequencing.

Suggestions

Add an explicit validation checkpoint after async crawl completion (e.g., verify expected page count, flag missing/empty pages, and retry failed URLs with scrapeUrl before declaring the crawl done).

Introduce a small feedback loop for partial results — the Error Handling table mentions using scrapeUrl for blocked pages, but the Step 3 workflow never routes back to it.

Show a guard before processing in Step 4 that checks for empty markdown or missing metadata so bad pages are skipped rather than written silently.

DimensionReasoningScore

Conciseness

The body is code-heavy with terse, functional inline comments ("strips nav, footer, sidebars", "max pages to crawl") and no padding explaining what Firecrawl or crawling is; prose assumes Claude's competence and every section earns its place.

3 / 3

Actionability

All four steps plus the examples are fully executable TypeScript with real Firecrawl calls and concrete option values (limit, maxDepth, waitFor, backoff), copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

The four steps are clearly sequenced, but these are batch operations (crawl up to 500 pages, async crawl) with no explicit validation/verification checkpoint or retry feedback loop before proceeding, which caps batch-operation workflow clarity at 2.

2 / 3

Progressive Disclosure

With no bundle files present, the single-file body is well organized into clearly labeled sections (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources) and the external doc links are one level deep, satisfying the simple/well-organized-skills allowance.

3 / 3

Total

11

/

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.

A strong, third-person description that states concrete capabilities, names the underlying API methods, and supplies both an explicit Use-when clause and natural trigger phrases. It cleanly satisfies the what/when requirement with minimal fluff.

DimensionReasoningScore

Specificity

Names concrete actions ("scrape and crawl websites into LLM-ready markdown") and specific API methods (scrapeUrl, crawlUrl), matching the multiple-specific-actions anchor rather than the domain-only level 2.

3 / 3

Completeness

Explicitly answers both what ("Execute Firecrawl primary workflow: scrape and crawl...") and when ("Use when scraping single pages, crawling entire sites...") with explicit trigger guidance, matching the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Provides natural phrases a user would actually say ("firecrawl scrape", "firecrawl crawl site", "scrape page to markdown", "crawl documentation"), giving good coverage rather than just a few relevant keywords.

3 / 3

Distinctiveness Conflict Risk

The Firecrawl-specific niche and named methods make it clearly distinguishable from generic scraping skills with distinct triggers unlikely to fire for the wrong skill.

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.