Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/adobe-deploy-integration

@820dfc8
Run it yourself

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

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/adobe-deploy-integration

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈78 tokens for metadata: the name and description. ≈845 when used: this file. ≈799 more on demand in 1 file.

Description uses 3.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈312 characters, or 3.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 — recheck dated Adobe sources before execution.
  • Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides secure deployment instructions and code patterns for Adobe integrations across Vercel, Google Cloud Run, and Adobe App Builder. It correctly leverages official platform tools and emphasizes security best practices for credential management.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<artifact> <target-environment> <rollout-scope>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
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

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/adobe-deploy-integration