firecrawl-prod-checklist

Execute FireCrawl production deployment checklist and rollback procedures.Use when deploying FireCrawl integrations to production, preparing for launch,or implementing go-live procedures.Trigger with phrases like "firecrawl production", "deploy firecrawl","firecrawl go-live", "firecrawl launch checklist".

⭐939stars🔀114forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill provides a comprehensive production deployment checklist and automated rollback procedures for FireCrawl integrations. It streamlines the go-live process by guiding users through pre-deployment configuration, code quality verification, and infrastructure setup. By utilizing Kubernetes for gradual canary rollouts and health monitoring, it ensures high reliability and minimizes the risk of downtime during production launches.

Use Cases

  • Executing a standardized production deployment for FireCrawl integrations to ensure all security and infrastructure prerequisites are met.
  • Implementing safe, gradual canary rollouts using Kubernetes to monitor error rates and latency before full traffic exposure.
  • Performing rapid rollbacks to previous stable versions using pre-defined commands when health checks fail during a deployment.
  • Verifying production readiness through automated health checks, API connectivity tests, and environment variable validation.
namefirecrawl-prod-checklist
description|
allowed-toolsRead, Bash(kubectl:*), Bash(curl:*), Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

FireCrawl Production Checklist

Overview

Complete checklist for deploying FireCrawl integrations to production.

Prerequisites

  • Staging environment tested and verified
  • Production API keys available
  • Deployment pipeline configured
  • Monitoring and alerting ready

Instructions

Step 1: Pre-Deployment Configuration

  • Production API keys in secure vault
  • Environment variables set in deployment platform
  • API key scopes are minimal (least privilege)
  • Webhook endpoints configured with HTTPS
  • Webhook secrets stored securely

Step 2: Code Quality Verification

  • All tests passing (npm test)
  • No hardcoded credentials
  • Error handling covers all FireCrawl error types
  • Rate limiting/backoff implemented
  • Logging is production-appropriate

Step 3: Infrastructure Setup

  • Health check endpoint includes FireCrawl connectivity
  • Monitoring/alerting configured
  • Circuit breaker pattern implemented
  • Graceful degradation configured

Step 4: Documentation Requirements

  • Incident runbook created
  • Key rotation procedure documented
  • Rollback procedure documented
  • On-call escalation path defined

Step 5: Deploy with Gradual Rollout

# Pre-flight checks
curl -f https://staging.example.com/health
curl -s https://status.firecrawl.com

# Gradual rollout - start with canary (10%)
kubectl apply -f k8s/production.yaml
kubectl set image deployment/firecrawl-integration app=image:new --record
kubectl rollout pause deployment/firecrawl-integration

# Monitor canary traffic for 10 minutes
sleep 600
# Check error rates and latency before continuing

# If healthy, continue rollout to 50%
kubectl rollout resume deployment/firecrawl-integration
kubectl rollout pause deployment/firecrawl-integration
sleep 300

# Complete rollout to 100%
kubectl rollout resume deployment/firecrawl-integration
kubectl rollout status deployment/firecrawl-integration

Output

  • Deployed FireCrawl integration
  • Health checks passing
  • Monitoring active
  • Rollback procedure documented

Error Handling

Alert Condition Severity
API Down 5xx errors > 10/min P1
High Latency p99 > 5000ms P2
Rate Limited 429 errors > 5/min P2
Auth Failures 401/403 errors > 0 P1

Examples

Health Check Implementation

async function healthCheck(): Promise<{ status: string; firecrawl: any }> {
  const start = Date.now();
  try {
    await firecrawlClient.ping();
    return { status: 'healthy', firecrawl: { connected: true, latencyMs: Date.now() - start } };
  } catch (error) {
    return { status: 'degraded', firecrawl: { connected: false, latencyMs: Date.now() - start } };
  }
}

Immediate Rollback

kubectl rollout undo deployment/firecrawl-integration
kubectl rollout status deployment/firecrawl-integration

Resources

Next Steps

For version upgrades, see firecrawl-upgrade-migration.