Agent skill · software engineering · jeremylongshore
firecrawl-multi-env-setup
Separate Firecrawl development, staging, and production identities, targets, budgets, policies, telemetry, and data stores. Use when creating or auditing multiple environments. Trigger with "Firecrawl environments", "Firecrawl staging", or "separate Firecrawl keys".
Why this skill is useful
Adds executable Docker and TypeScript scripts for configuring Firecrawl across multiple environments, which are not commonly found in public documentation.
What it needs
Requires docker, gcloud 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 Environment Separation Overview Prevent a test from consuming production credits, crawling production targets, or writing captured content into the wrong store. Environment identity must be explicit and fail closed. 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 Cloud keys are team-scoped credentials and team limits are shared across keys, so separate keys alone do not guarantee capacity isolation. Key restrictions, spend limits, IP restrictions, distinct teams/accounts where appropriate, and an application policy gateway provide different isolation layers. Self-hosted evaluation has a separate capability and security contract. 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. Inventory each environment's owner, team/account, key, secret path, egress, allowed domains, endpoints/formats, spend ceiling, queue capacity, retention, store, and alert destination. 2. Create distinct secret-manager entries and workload identities. Validate that configuration names the environment and refuses missing or cross-environment values. 3. Apply environment-specific domain policy, explicit crawl/batch limits, endpoint/format restrictions where available, and non-production credit ceilings. 4. Keep production targets and captured fixtures out of developer machines and pull-request CI. Use synthetic fakes by default and a protected staging tenant for live tests. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/firecrawl-multi-env-setup