firecrawl-data-handling

Process, validate, and store Firecrawl scraped content with deduplication and chunking. Use when handling scraped markdown, implementing content pipelines, building RAG knowledge bases, or processing crawl results for downstream consumption. Trigger with phrases like "firecrawl data", "firecrawl content processing", "firecrawl markdown cleaning", "firecrawl storage", "firecrawl RAG pipeline".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 content is highly actionable and token-efficient, with complete executable TypeScript across five sequenced pipeline steps. Its weaknesses are a missing validation feedback loop in the batch crawl/store workflow and a lack of progressive disclosure into separate bundle files.

Suggestions

Add an explicit validation checkpoint to the crawl-and-store pipeline (e.g., verify the manifest against crawled pages and retry failed URLs before writing) to form a validate→fix→retry loop.

Move the reusable library functions (cleanMarkdown, contentHash, deduplicatePages, chunkForRAG) into a scripts/ bundle file and reference it one level deep, keeping SKILL.md as a concise overview.

Surface crawl-failure handling inline in the Step 5 workflow rather than only in the reference Error Handling table, so the batch operation has an inline recovery path.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — executable TypeScript with terse comments and a one-sentence overview, with no padding or explanations of concepts Claude already knows. Every token earns its place for a code-heavy skill.	3 / 3
Actionability	Fully executable, copy-paste-ready TypeScript functions with imports and specific options — scrapeClean, cleanMarkdown, extractArticle with Zod, deduplicatePages, chunkForRAG, and crawlAndStore — not pseudocode.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced and an error-handling table maps issues to causes and solutions, but the crawl/store pipeline is a batch operation (crawling up to 50 pages, writing files) with no explicit validate→fix→retry checkpoint inline, which caps it at 2.	2 / 3
Progressive Disclosure	Sections are well organized, but all content lives inline in a ~240-line monolithic SKILL.md with no bundle files (references/, scripts/, assets/ are absent) and no one-level-deep internal references to split the library-style functions out.	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: it names concrete capabilities, gives explicit when-to-use guidance with natural trigger phrases, and is tightly scoped to a distinct niche. It uses correct third-person voice with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Process, validate, and store Firecrawl scraped content with deduplication and chunking' — in third person, covering five distinct operations rather than just naming the domain.	3 / 3
Completeness	Explicitly answers both 'what' ('Process, validate, and store...') and 'when' ('Use when handling scraped markdown, implementing content pipelines, building RAG knowledge bases...') with explicit triggers.	3 / 3
Trigger Term Quality	Provides good coverage of natural terms a user would say — 'firecrawl data', 'firecrawl content processing', 'firecrawl markdown cleaning', 'firecrawl storage', 'firecrawl RAG pipeline', plus 'scraped markdown' and 'crawl results'.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Firecrawl content pipelines with firecrawl-prefixed triggers, giving it a clear niche unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 50ab626

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.