Agent skill · marketing growth · jeremylongshore
firecrawl-policy-guardrails
Enforce domain authorization, robots and terms review, endpoint and format allowlists, scope, spend, retention, and unsafe-content controls around Firecrawl. Use when governing automated collection. Trigger with "Firecrawl guardrails", "scraping policy", or "restrict Firecrawl domains".
Why this skill is useful
Adds executable scripts for enforcing scraping policies, including domain blocklists and credit budgets that are not commonly found in public documentation.
What it needs
Requires @mendable/firecrawl-js installed locally. Requires firecrawl account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Firecrawl Collection Policy Guardrails Overview Put enforceable policy before every Firecrawl request and downstream action. Provider capability does not establish permission to collect, retain, or reuse a source. Prerequisites The target repository or integration path and the requested operator outcome. The source authorization, data classification, and environment policy. Current Firecrawl documentation, credentials only when needed, and an owner for approvals. Current Contract Firecrawl crawl supports scope controls, explicit limits, delay, maxConcurrency, and an enterprise robotsUserAgent option. Enterprise controls include endpoint/format key restrictions, IP restrictions, threat protection, and SIEM integration. Request options such as headers, actions, proxy, cache, ZDR, lockdown, and raw formats have separate risk and availability implications. Authentication For authenticated Cloud operations, inject FIRECRAWLAPIKEY from an approved secret manager. REST requests use Authorization: Bearer with the key. Never print, commit, transmit, or place a key in a URL. Keyless access is suitable only where the current documentation explicitly allows it and the workload accepts its limits; production workflows should make identity and team ownership explicit. Instructions 1. Create a versioned source registry with owner, authorization basis, allowed purpose, domains/paths, robots and terms review, data classes, retention, and expiry. 2. Canonicalize URLs before policy evaluation. Deny unsupported schemes, embedded credentials, private/link-local addresses, disallowed ports, redirects outside scope, and lookalike hosts. 3. Allow only required operations, formats, actions, headers, locations, proxy modes, and crawl settings. Set explicit page, time, credit, and concurrency ceilings. 4. Apply provider-side key, IP, threat-protection, and audit controls where entitled, but keep application policy authoritative and fail closed if it is unavailable. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/firecrawl-policy-guardrails