Agent skill · software engineering · jeremylongshore
firecrawl-deploy-integration
Deploy a Firecrawl v2 client integration or a reviewed self-hosted stack with secrets, canaries, health evidence, and rollback controls. Use when releasing Firecrawl-backed services. Trigger with "deploy Firecrawl", "Firecrawl production rollout", or "self-host Firecrawl".
Why this skill is useful
Adds executable scripts for deploying Firecrawl integrations across multiple platforms with specific configurations that aren't in public docs.
What it needs
Requires docker, gcloud, vercel 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 Production Deployment Overview Deploy the application client and the Firecrawl service as separate responsibilities. Cloud integrations need a protected key and egress policy; self-hosting adds databases, queues, browsers, storage, authentication, upgrades, and recovery. 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 clients use the v2 API and secret-managed FIRECRAWLAPIKEY. The official self-host guide's Compose example is an evaluation baseline with authentication disabled and without durable storage, TLS, high availability, or every Cloud capability. Pin the reviewed release and its own Compose contract; do not copy a floating main configuration into production. 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 the application release, Firecrawl Cloud or self-host decision, required features, environments, domains, data flows, SLOs, and rollback owner. 2. For Cloud, inject the key from the platform secret manager, restrict outbound destinations, choose retention/cache policy, and prevent request or response bodies from application logs. 3. For self-hosting, pin a verified release and review its Compose, SELFHOST, and feature-support documentation. Map every optional provider and outbound flow. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/firecrawl-deploy-integration