Agent skill · software engineering · jeremylongshore
adobe-deploy-integration
Deploy an Adobe-backed service or App Builder application with isolated environments, immutable artifacts, canaries, observability, and rollback. Use when the task requires adobe integration deployment. Trigger with "deploy Adobe integration", "aio app deploy", or "promote Adobe app".
Why this skill is useful
Adds executable scripts for deploying Adobe applications with credential management across multiple platforms, which aren't covered in public documentation.
What it needs
Requires aio, gcloud, vercel installed locally. Requires adobe account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Adobe Integration Deployment Overview Deploy an Adobe-backed service or App Builder application with isolated environments, immutable artifacts, canaries, observability, and rollback. This workflow produces a reviewable artifact and evidence before any live side effect. Prerequisites Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle. Named product, identity, security, data, budget, release, and operations owners appropriate to the scope. Synthetic or approved non-production fixtures with secret and content canaries. Current Contract AIO CLI v11 and later require Adobe IMS authentication for App Builder deploys: interactive aio login locally or OAuth Server-to-Server in CI. Runtime namespace auth is not a current deploy mechanism. Stage and Production workspaces are isolated. Recheck the dated evidence map before relying on mutable product behavior. Authentication Bind deploy credentials and product credentials to the target environment. app.config.yaml is reviewed source; .env and .aio are local state and must not be committed. Instructions 1. Verify the artifact digest, dependency locks, configuration schema, tests, migration, and rollback artifact. 2. Resolve organization, project, workspace, service credentials, product profiles, storage, and event registrations. 3. Confirm the AIO CLI/auth path or external platform identity and fail closed on environment mismatch. 4. Deploy dark, verify configuration and logs, then run one approved read-only or synthetic smoke path. 5. Canary bounded traffic while watching auth, 429, jobs, queue age, spend, activations, and content-safe errors. 6. Promote or roll back from declared thresholds and preserve deployment, activity-log, cleanup, and owner receipts. Tool Discipline Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-deploy-integration