perplexity-prod-checklist

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

⭐920stars🔀111forks📁View on GitHub🕐Updated Jan 9, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill streamlines the production deployment of Perplexity integrations by providing a structured, automated checklist and robust rollback procedures. It guides developers through critical pre-deployment configurations, infrastructure setup, and gradual canary rollouts using Kubernetes, ensuring that AI-driven features are launched securely and reliably with built-in monitoring and error handling.

Use Cases

  • Scenario 1: Executing a safe canary deployment of Perplexity integrations to production, starting with 10% traffic to monitor for latency and error rates before a full rollout.
  • Scenario 2: Automating pre-deployment security audits, including API key scope verification, environment variable configuration, and webhook HTTPS validation.
  • Scenario 3: Rapidly responding to deployment failures or performance degradation by triggering automated kubectl rollback procedures and verifying system health.
  • Scenario 4: Setting up production-ready monitoring and alerting for Perplexity API connectivity, ensuring P1 alerts are triggered for high error rates or authentication failures.
nameperplexity-prod-checklist
description|
allowed-toolsRead, Bash(kubectl:*), Bash(curl:*), Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Perplexity Production Checklist

Overview

Complete checklist for deploying Perplexity 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 Perplexity error types
  • Rate limiting/backoff implemented
  • Logging is production-appropriate

Step 3: Infrastructure Setup

  • Health check endpoint includes Perplexity 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.perplexity.com

# Gradual rollout - start with canary (10%)
kubectl apply -f k8s/production.yaml
kubectl set image deployment/perplexity-integration app=image:new --record
kubectl rollout pause deployment/perplexity-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/perplexity-integration
kubectl rollout pause deployment/perplexity-integration
sleep 300

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

Output

  • Deployed Perplexity 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; perplexity: any }> {
  const start = Date.now();
  try {
    await perplexityClient.ping();
    return { status: 'healthy', perplexity: { connected: true, latencyMs: Date.now() - start } };
  } catch (error) {
    return { status: 'degraded', perplexity: { connected: false, latencyMs: Date.now() - start } };
  }
}

Immediate Rollback

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

Resources

Next Steps

For version upgrades, see perplexity-upgrade-migration.