Agent skill · software engineering · jeremylongshore
anth-deploy-integration
Deploy Claude API integrations to production cloud environments.
Why this skill is useful
Adds executable deployment scripts for Claude API integrations with secret management and health checks across multiple cloud environments.
What it needs
Requires docker, gcloud, kubectl installed locally. Requires anthropic account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Anthropic Deploy Integration Overview Deploy Claude API integrations with proper secret management, health checks, and rollback procedures across Docker, GCP Cloud Run, and Kubernetes. Docker Deployment GCP Cloud Run Kubernetes Rollback Error Handling Issue Cause Fix ------- ------- ----- Container crash on start Missing API key env var Verify secret binding Health check fails Key invalid in prod Test key with curl 429 after scaling up More replicas = more RPM Shared rate limiter (Redis) Prerequisites Have an approved artifact digest, environment/workspace mapping, secret-manager reference, health probe, deployment owner, canary plan, and tested rollback command. Use a least-privileged runtime identity and synthetic fixtures in staging; never embed API keys in images, manifests, command history, or deployment output. Define deployment SLOs for health, errors, latency, rate limits, cost, and data-policy checks, with explicit halt thresholds. Instructions 1. Build and scan the pinned artifact, bind the environment-specific secret at runtime, and verify that logs and probes cannot expose prompts, responses, or credentials. 2. Deploy to staging and run the token-count/health probe plus synthetic Messages API, error, timeout, rate-limit, and redaction tests. Confirm the workspace and model are approved. 3. Release to one sandbox or internal canary, monitor aggregate SLOs and sensitivecontentlogged=0, and require owner approval before wider traffic. 4. Promote in bounded stages while preserving the prior revision and idempotent deployment record. Do not bypass failed health, authorization, or data-policy gates. 5. On failure, stop traffic, roll back to the prior revision, revoke temporary access, clean up staged artifacts under the retention policy, and issue a redacted deployment receipt. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/anth-deploy-integration