Skip to content
Skills Library
DevOps & cloud · Automation

adobe-deploy-integration

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

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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

Triggers from the description

deploy Adobe integrationaio app deploypromote Adobe app

Arguments

/adobe-deploy-integration <artifact> <target-environment> <rollout-scope>
Original author description

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

How it works

  1. Overview
  2. Prerequisites
  3. Current Contract
  4. Authentication
  5. Instructions
  6. Tool Discipline
  7. Approval Boundaries
  8. Error Handling
  9. Output
  10. Examples
Original SKILL.md headings · 68 lines, 458 words
SKILL.md preview
---
name: adobe-deploy-integration
description: >-
  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".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<artifact> <target-environment> <rollout-scope>"
version: 1.8.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, adobe, deployment]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval"
---
# 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. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion.

## Approval Boundaries

Release owner approves production deployment; security approves credentials; data/budget owners approve live product calls; webhook or asset deletion needs separate approval.

## Error Handling

- Stop if the selected workspace differs from the review target.
- Do not commit .env or .aio.
- Rollback if artifact, auth, entitlement, storage, or observability evidence is missing.

## Output

Return artifact and environment identity, auth path, preflight, smoke/canary metrics, decision, rollback, cleanup, and owners. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

## Examples

- Deploy to Stage and prove Production is unchanged.
- Exercise rollback after a synthetic entitlement failure.

## Validation

Exercise and record expected and observed results for:

- artifact mismatch
- workspace mismatch
- missing entitlement
- 429
- rollback
- cleanup

## Resources

- [Current first-party evidence map](references/official-docs.md) — recheck dated Adobe sources before execution.
- Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 3 KB

Versions

The database has no other skills named adobe-deploy-integration.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version e4e69c1833b0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90appbuilder-cicd-pipeline
    Set up CI/CD pipelines for Adobe App Builder projects. Generates GitHub Actions workflows using adobe/aio-cli-setup-action@3 and adobe/aio-apps-action@3.3.0, plus patterns for Azure DevOps and GitLab CI. Handles OAuth S2S secrets injection, multi-workspace promotion (stage →…
  • 100alchemy-deploy-integration
    Deploy an Alchemy-backed service through environment-scoped credentials, chain assertions, canaries, and rollback gates. Use when promoting an integration to hosted environments. Trigger with "deploy Alchemy integration", "Alchemy production deploy", or "promote an Alchemy service".
  • 100adobe-prod-checklist
    Issue an evidence-backed production decision across Adobe auth, entitlements, API versions, data custody, async reliability, spend, observability, and rollback. Use before launch or a material integration change. Use when the task requires adobe production readiness decision.…
  • 100aem-rde
    [BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly…
  • 90adobe-study
    Apply the Adobe brand study to drafts. Use for any deck, page, post or email written in this brand.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.