exa-prod-checklist
Execute Exa production deployment checklist and rollback procedures.Use when deploying Exa integrations to production, preparing for launch,or implementing go-live procedures.Trigger with phrases like "exa production", "deploy exa","exa go-live", "exa launch checklist".
When & Why to Use This Skill
This Claude skill automates the execution of production deployment checklists and rollback procedures specifically for Exa integrations. It enhances release reliability by guiding users through pre-deployment configuration, infrastructure verification, and controlled Kubernetes-based canary rollouts, ensuring that production launches are secure, monitored, and reversible.
Use Cases
- Executing a structured production launch for Exa integrations with automated environment and API key verification.
- Managing gradual canary deployments on Kubernetes to monitor real-time traffic health before full-scale release.
- Performing rapid, automated rollbacks using kubectl commands when health checks fail or latency exceeds thresholds.
- Standardizing go-live procedures to ensure all security, logging, and monitoring prerequisites are met before deployment.
| name | exa-prod-checklist |
|---|---|
| description | | |
| allowed-tools | Read, Bash(kubectl:*), Bash(curl:*), Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Exa Production Checklist
Overview
Complete checklist for deploying Exa 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 Exa error types
- Rate limiting/backoff implemented
- Logging is production-appropriate
Step 3: Infrastructure Setup
- Health check endpoint includes Exa 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.exa.com
# Gradual rollout - start with canary (10%)
kubectl apply -f k8s/production.yaml
kubectl set image deployment/exa-integration app=image:new --record
kubectl rollout pause deployment/exa-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/exa-integration
kubectl rollout pause deployment/exa-integration
sleep 300
# Complete rollout to 100%
kubectl rollout resume deployment/exa-integration
kubectl rollout status deployment/exa-integration
Output
- Deployed Exa 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; exa: any }> {
const start = Date.now();
try {
await exaClient.ping();
return { status: 'healthy', exa: { connected: true, latencyMs: Date.now() - start } };
} catch (error) {
return { status: 'degraded', exa: { connected: false, latencyMs: Date.now() - start } };
}
}
Immediate Rollback
kubectl rollout undo deployment/exa-integration
kubectl rollout status deployment/exa-integration
Resources
Next Steps
For version upgrades, see exa-upgrade-migration.