firecrawl-policy-guardrails

Implement Firecrawl scraping policy enforcement: domain blocklists, credit budgets, content filtering, and robots.txt compliance guardrails. Use when setting up scraping policies, enforcing crawl limits, or preventing accidental scraping of prohibited domains. Trigger with phrases like "firecrawl policy", "firecrawl guardrails", "firecrawl domain blocklist", "firecrawl scraping rules", "firecrawl compliance".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

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

The content delivers highly actionable, executable code with a clearly sequenced policy-enforcement workflow and helpful summary tables. Its weaknesses are a single dangling reference to a non-existent architecture file and heavy inlining of code that would benefit from progressive disclosure into reference files.

Suggestions

Either create the referenced 'firecrawl-architecture-variants' file or remove the dangling Next Steps pointer so references point to real bundle files.

Move the large TypeScript class/function blocks into a references/ or scripts/ file and keep SKILL.md as an overview with one-level-deep pointers, improving progressive disclosure.

Add an explicit validate→fix→retry feedback loop (e.g., retry on rate-limit/429 with backoff) to the crawl workflow to strengthen validation checkpoints for the batch operation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-driven with useful inline comments, but the Overview paragraph ('Web scraping carries legal... ethical... and cost... risks') briefly restates context Claude already knows, keeping it at 4 rather than 5.	4 / 5
Actionability	All five steps provide complete, copy-paste-ready TypeScript that is directly executable, and the closing scrapePipeline example ties them together covering the common cases, matching the 5 anchor.	5 / 5
Workflow Clarity	Steps 1–5 are clearly sequenced with pre-request validation (validateUrl, budget.authorize) and a post-scrape content-quality filter, plus an error-handling table; it stops at 4 because there is no explicit validate→fix→retry feedback loop for the batch crawl, which the rubric rewards for batch operations.	4 / 5
Progressive Disclosure	Sections are well organized, but ~200 lines of inlined TypeScript that could live in separate reference files plus a Next Steps pointer to 'firecrawl-architecture-variants' (a file absent from the bundle) make this a 3: structure present but references not clearly signaled/real and content that should be separate is inline.	3 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%Scale 1-5

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' guidance, and lists natural trigger phrases within a clearly distinct Firecrawl-policy niche. Minor room remains for broader synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete mechanisms — 'domain blocklists, credit budgets, content filtering, and robots.txt compliance guardrails' — which lists several specific actions with only minor coverage gaps, fitting the 4 anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Explicitly answers both 'what' (implement policy enforcement with named mechanisms) and 'when' ('Use when setting up scraping policies, enforcing crawl limits, or preventing accidental scraping of prohibited domains') plus concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Provides natural trigger phrases users would say ('firecrawl policy', 'firecrawl guardrails', 'firecrawl domain blocklist', 'firecrawl scraping rules', 'firecrawl compliance') giving good keyword coverage, though the terms are uniformly 'firecrawl'-prefixed and miss some plain synonyms, landing at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Firecrawl-specific policy niche with distinct triggers and minimal conflict risk, but could still overlap with a general Firecrawl scraping skill, so it sits at 4 rather than the maximal 5.	4 / 5
	Total	17 / 20 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
Path: plugins/saas-packs/firecrawl-pack/skills/firecrawl-policy-guardrails/SKILL.md
Commit: 0540a62

Reviewed: about 18 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.