Wardn Hub
MCP ServersSkillsCategoriesAPI docsSubmit server
Submit server
Wardn HubTrusted MCP server directory.

Registry

  • MCP Servers
  • Skills
  • Categories

Resources

  • API docs
  • Score method

Contribute

  • Submit server
  • Advertise
© 2026 Wardn Hub
Wardn Hub
MCP ServersSkillsCategoriesAPI docsSubmit server
Submit server
skills/jeremylongshore/claude-code-plugins-plus-skills/curated-adobe-prod-checklist

adobe-prod-checklist

1
jeremylongshore/claude-code-plugins-plus-skills·Cloud Platforms·Audit passed·Snapshot 9d46c965e8a0
Installs
0

Summary

Execute Adobe production deployment checklist covering credential management,

SKILL.md

Adobe Production Checklist

Overview

Complete checklist for deploying Adobe API integrations to production, covering credential security, health monitoring, graceful degradation, and rollback procedures.

Prerequisites

  • Staging environment tested and verified
  • Production OAuth credentials created in Developer Console
  • Deployment pipeline with secret injection
  • Monitoring and alerting infrastructure ready

Instructions

Pre-Deployment: Credentials & Configuration

  • Production OAuth Server-to-Server credentials created (separate from staging)
  • ADOBE_CLIENT_ID and ADOBE_CLIENT_SECRET stored in secret manager (not env files)
  • Scopes are minimal: only APIs actually used in production
  • Token caching implemented (avoid re-generating per request)
  • I/O Events webhook endpoints use HTTPS with valid TLS cert
  • Webhook challenge response handler implemented (for registration)

Pre-Deployment: Code Quality

  • All tests passing (npm test)
  • No hardcoded credentials (grep for p8_ prefix patterns)
  • Error handling covers: 401, 403, 429, 500, 503
  • Rate limiting/backoff with Retry-After header support
  • Webhook signature verification using RSA-SHA256
  • Logging redacts credentials and PII
  • API response validation (Zod or equivalent)
  • Pre-Deployment: Infrastructure

    • Health check endpoint verifies Adobe IMS token generation:
    // api/health.ts
    export async function adobeHealthCheck() {
      const start = Date.now();
      try {
        // Test token generation (validates credentials are still valid)
        const token = await getAccessToken();
        return {
          status: 'healthy',
          latencyMs: Date.now() - start,
          tokenValid: !!token,
        };
      } catch (error: any) {
        return {
          status: 'unhealthy',
          latencyMs: Date.now() - start,
          error: error.message,
        };
      }
    }
    
    • Circuit breaker configured for Adobe API calls
    • Graceful degradation: app works (degraded) if Adobe is down
    • PDF Services monthly quota tracking (if on free tier)

    Deploy: Gradual Rollout

    # 1. Pre-flight checks
    curl -sf https://staging.example.com/health | jq '.services.adobe'
    curl -s https://status.adobe.com | head -5
    
    # 2. Verify production credentials work
    curl -s -o /dev/null -w "%{http_code}" -X POST \
      'https://ims-na1.adobelogin.com/ims/token/v3' \
      -d "client_id=${ADOBE_CLIENT_ID}&client_secret=${ADOBE_CLIENT_SECRET}&grant_type=client_credentials&scope=${ADOBE_SCOPES}"
    # Expected: 200
    
    # 3. Deploy canary (10%)
    kubectl set image deployment/app app=image:new-version
    kubectl rollout pause deployment/app
    
    # 4. Monitor for 10 minutes — check error rates
    # Watch for 401 (credential issues), 429 (rate limits), 500 (server errors)
    
    # 5. If healthy, complete rollout
    kubectl rollout resume deployment/app
    kubectl rollout status deployment/app
    

    Post-Deployment Verification

    • Health check endpoint returns healthy for Adobe
    • Test a real API call (e.g., Firefly image generation, PDF extraction)
    • Webhook delivery confirmed (check I/O Events dashboard)
    • Error rate baseline established in monitoring
    • On-call team has adobe-incident-runbook accessible

    Rollback Procedure

    # Immediate rollback
    kubectl rollout undo deployment/app
    kubectl rollout status deployment/app
    
    # Verify old version is healthy
    curl -sf https://production.example.com/health | jq '.services.adobe'
    

    Alert Configuration

    AlertConditionSeverity
    Adobe Auth FailureAny 401 errorsP1 — credential issue
    Adobe Rate Limited429 errors > 5/minP2 — reduce throughput
    Adobe API Down503 errors > 10/minP2 — enable fallback
    Adobe High Latencyp99 > 10sP3 — investigate
    PDF Quota Low< 50 transactions remainingP3 — upgrade or throttle

    Error Handling

    IssueCauseSolution
    401 after deployWrong credentials for environmentVerify secret manager path
    429 spikeTraffic increase from new featureAdd rate limiting queue
    Health check flappingToken caching not workingCheck cache TTL logic
    Webhook delivery stoppedChallenge response brokenTest webhook registration

    Output

    Following this guide produces the Adobe integration outcome for its topic—configuration, validation evidence, operational recovery, or a documented migration result. Record command output and relevant identifiers so a failed step is traceable.

    Examples

    Start with the smallest applicable command or code example already provided in this guide, using a non-production Adobe environment and credentials. Confirm the documented response or validation result before applying the pattern to production.

    Resources

    • Adobe Status Page
    • Adobe Developer Console
    • Adobe Developer Support

    Next Steps

    For version upgrades, see adobe-upgrade-migration.

    Related skills

    implementing-backup-strategieskubernetes-secrets-managerbuilding-gitops-workflowsmanaging-api-cachemanaging-network-policies