Skip to content
Back to skills

Perplexity Prod Checklist

ASecurity

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".

  • 2,688 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 7, 2026
devopstypescriptgobashapidocumentation

Works with

  • cli
  • api

Security analysis

A96/100
  • mediumUses curl or wget to download content

Pro shows the line behind each finding and how to fix it

Scanned February 12, 2026

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill perplexity-prod-checklist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Perplexity Prod Checklist?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Perplexity Prod Checklist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jeremylongshore-perplexity-prod-checklist/badge)](https://www.skillsdirectory.com/skills/jeremylongshore-perplexity-prod-checklist)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: perplexity-prod-checklist
description: |
  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".
allowed-tools: Read, Bash(kubectl:*), Bash(curl:*), Grep
version: 1.0.0
license: MIT
author: Jeremy 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
```bash
# 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
```typescript
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
```bash
kubectl rollout undo deployment/perplexity-integration
kubectl rollout status deployment/perplexity-integration
```

## Resources
- [Perplexity Status](https://status.perplexity.com)
- [Perplexity Support](https://docs.perplexity.com/support)

## Next Steps
For version upgrades, see `perplexity-upgrade-migration`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.