firecrawl-multi-env-setup
Configure Firecrawl across development, staging, and production environments. Use when setting up multi-environment scraping pipelines, managing credit budgets per env, or configuring self-hosted Firecrawl for development. Trigger with phrases like "firecrawl environments", "firecrawl staging", "firecrawl dev prod", "firecrawl environment setup", "firecrawl config by env". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Firecrawl Multi-Environment Setup ## Overview Firecrawl's credit-based pricing makes environment separation critical. Development should use self-hosted Firecrawl or strict limits to avoid burning production credits during testing. This skill covers per-environment config, self-hosted Docker for dev, and credit budget enforcement. ## Environment Strategy | Environment | API Source | Crawl Limit | Concurrency | Credits | |-------------|-----------|-------------|-------------|---------| | Development | Self-hosted Docker | 10 pages | 1 | Zero (local) | | Staging | Cloud API (test key) | 50 pages | 2 | Limited | | Production | Cloud API (prod key) | Per-task | Full plan | Monitored | ## Instructions ### Step 1: Environment-Aware Configuration ```typescript // config/firecrawl.ts import FirecrawlApp from "@mendable/firecrawl-js"; type Env = "development" | "staging" | "production"; interface FirecrawlConfig { apiKey: string; apiUrl?: string; maxPagesPerCrawl: number; maxDepth: number; concurrency: number; waitFor: number; } const configs: Record<Env, FirecrawlConfig> = { development: { apiKey: process.env.FIRECRAWL_API_KEY_DEV || "fc-localdev", apiUrl: process.env.FIRECRAWL_API_URL_D
- Overview
- Environment Strategy
- Instructions
- Step 1: Environment-Aware Configuration
- Step 2: Self-Hosted Firecrawl for Development
- Step 3: Credit-Safe Scraping Wrapper
- Step 4: Environment Variables
- Step 5: CI/CD Pipeline
- Error Handling
- Examples
- Check Active Configuration
- Resources
- Next Steps
set -euo pipefail docker compose -f docker-compose.dev.yml up -d CI / Staging Production
What does the firecrawl-multi-env-setup skill do?
Configure Firecrawl across development, staging, and production environments. Use when setting up multi-environment scraping pipelines, managing credit budgets per env, or configuring self-hosted Firecrawl for development. Trigger with phrases like "firecrawl environments", "firecrawl staging", "firecrawl dev prod", "firecrawl environment setup", "firecrawl config by env". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.