From clay-pack
Execute Clay production deployment checklist and rollback procedures. Use when deploying Clay integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "clay production", "deploy clay", "clay go-live", "clay launch checklist".
How this skill is triggered — by the user, by Claude, or both
Slash command
/clay-pack:clay-prod-checklistThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Complete checklist for deploying Clay integrations to production.
Complete checklist for deploying Clay integrations to production.
npm test)set -euo pipefail
# Pre-flight checks
curl -f https://staging.example.com/health
curl -s https://status.clay.com
# Gradual rollout - start with canary (10%)
kubectl apply -f k8s/production.yaml
kubectl set image deployment/clay-integration app=image:new --record
kubectl rollout pause deployment/clay-integration
# Monitor canary traffic for 10 minutes
sleep 600 # 600: timeout: 10 minutes
# Check error rates and latency before continuing
# If healthy, continue rollout to 50%
kubectl rollout resume deployment/clay-integration
kubectl rollout pause deployment/clay-integration
sleep 300 # 300: timeout: 5 minutes
# Complete rollout to 100%
kubectl rollout resume deployment/clay-integration
kubectl rollout status deployment/clay-integration
| 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 |
async function healthCheck(): Promise<{ status: string; clay: any }> {
const start = Date.now();
try {
await clayClient.ping();
return { status: 'healthy', clay: { connected: true, latencyMs: Date.now() - start } };
} catch (error) {
return { status: 'degraded', clay: { connected: false, latencyMs: Date.now() - start } };
}
}
set -euo pipefail
kubectl rollout undo deployment/clay-integration
kubectl rollout status deployment/clay-integration
For version upgrades, see clay-upgrade-migration.
npx claudepluginhub terrylica/claude-code-plugins-plus --plugin clay-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026