fireflies-prod-checklist
Execute Fireflies.ai production deployment checklist and rollback procedures.Use when deploying Fireflies.ai integrations to production, preparing for launch,or implementing go-live procedures.Trigger with phrases like "fireflies production", "deploy fireflies","fireflies go-live", "fireflies launch checklist".
When & Why to Use This Skill
This Claude skill automates the production deployment lifecycle for Fireflies.ai integrations, ensuring high reliability through systematic checklists, automated health checks, and standardized rollback procedures. It streamlines the transition from staging to production by managing API configurations, infrastructure readiness, and gradual canary rollouts using Kubernetes and CLI tools.
Use Cases
- Safe Production Launches: Use the skill to verify environment variables, API keys, and security scopes before going live with a new Fireflies.ai integration to prevent configuration errors.
- Automated Canary Rollouts: Execute a controlled deployment strategy by deploying to a small percentage of traffic, monitoring health metrics, and scaling to full production only when stability is confirmed.
- Rapid Incident Recovery: Quickly trigger standardized rollback procedures using kubectl commands if production health checks fail or error rates spike immediately following a deployment.
- Infrastructure & Quality Audit: Automatically run through a comprehensive pre-flight checklist covering code quality, rate limiting, and logging to ensure the integration meets production-grade standards.
| name | fireflies-prod-checklist |
|---|---|
| description | | |
| allowed-tools | Read, Bash(kubectl:*), Bash(curl:*), Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Fireflies.ai Production Checklist
Overview
Complete checklist for deploying Fireflies.ai 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 Fireflies.ai error types
- Rate limiting/backoff implemented
- Logging is production-appropriate
Step 3: Infrastructure Setup
- Health check endpoint includes Fireflies.ai 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.fireflies.com
# Gradual rollout - start with canary (10%)
kubectl apply -f k8s/production.yaml
kubectl set image deployment/fireflies-integration app=image:new --record
kubectl rollout pause deployment/fireflies-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/fireflies-integration
kubectl rollout pause deployment/fireflies-integration
sleep 300
# Complete rollout to 100%
kubectl rollout resume deployment/fireflies-integration
kubectl rollout status deployment/fireflies-integration
Output
- Deployed Fireflies.ai 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; fireflies: any }> {
const start = Date.now();
try {
await firefliesClient.ping();
return { status: 'healthy', fireflies: { connected: true, latencyMs: Date.now() - start } };
} catch (error) {
return { status: 'degraded', fireflies: { connected: false, latencyMs: Date.now() - start } };
}
}
Immediate Rollback
kubectl rollout undo deployment/fireflies-integration
kubectl rollout status deployment/fireflies-integration
Resources
Next Steps
For version upgrades, see fireflies-upgrade-migration.