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".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a strong skill description that clearly defines specific capabilities (domain blocklists, credit budgets, content filtering, robots.txt compliance), provides explicit 'Use when' guidance, and includes well-chosen trigger phrases. The description is concise, uses third-person voice, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: domain blocklists, credit budgets, content filtering, and robots.txt compliance guardrails. These are clearly defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement Firecrawl scraping policy enforcement with specific capabilities) and 'when' (explicit 'Use when' clause covering setting up policies, enforcing limits, preventing prohibited scraping) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes a rich set of natural trigger terms: 'firecrawl policy', 'firecrawl guardrails', 'firecrawl domain blocklist', 'firecrawl scraping rules', 'firecrawl compliance', plus contextual phrases like 'scraping policies', 'crawl limits', 'prohibited domains'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Firecrawl scraping policy enforcement) with domain-specific triggers like 'firecrawl domain blocklist' and 'firecrawl compliance' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with executable TypeScript code covering all major policy enforcement patterns for Firecrawl scraping. The workflow is well-sequenced with clear validation checkpoints and a helpful summary table. The main weaknesses are moderate verbosity (some unnecessary explanatory text and comments) and a somewhat monolithic structure that could benefit from splitting detailed implementations into referenced files.
Suggestions
Trim the overview paragraph—Claude doesn't need an explanation of why web scraping carries legal/ethical/cost risks; jump straight to what the skill enforces.
Consider moving the detailed class implementations (Steps 1-3) into a referenced file and keeping only the policedCrawl orchestration and pipeline example in the main SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code, but includes some unnecessary commentary (e.g., explaining what web scraping risks are in the overview, inline comments explaining obvious things like '// Meta ToS'). The content is substantial but could be tightened—the overview paragraph explains concepts Claude already knows about legal/ethical risks. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with concrete implementations—domain blocklist checking, budget enforcement, content quality gates, rate limiting, and a complete pipeline example. Every step provides copy-paste ready code with specific patterns. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced from domain validation → budget check → content quality → crawl limits → rate limiting. Step 4 (policedCrawl) demonstrates the full validation chain with explicit checkpoints: validate URL, enforce limits, check budget, execute, record usage, filter quality. The policy summary table provides a clear overview of enforcement points and consequences. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and summary tables, but it's quite long (~180 lines of code) and could benefit from splitting detailed implementations into separate files. The reference to 'firecrawl-architecture-variants' is good, but the main file is somewhat monolithic with all implementation details inline. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
c8a915c
- 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.