Agent skill · software engineering · jeremylongshore
adobe-multi-env-setup
Separate Adobe development, stage, and production organizations/projects/workspaces, credentials, profiles, storage, events, budgets, and evidence. Use when the task requires adobe multi-environment isolation. Trigger with "Adobe environments", "separate Adobe staging", or "Adobe workspace setup".
Why this skill is useful
Provides specific configuration patterns and scripts for managing Adobe API access across multiple environments that the AI wouldn't generate on its own.
What it needs
Requires aws, gcloud, vault 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 Multi-Environment Isolation Overview Separate Adobe development, stage, and production organizations/projects/workspaces, credentials, profiles, storage, events, budgets, and evidence. 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 App Builder provides isolated workspaces such as Stage and Production within a project, while some risk boundaries require separate projects or credentials. Environment equivalence must be proven from configuration and entitlement, not assumed from names. Recheck the dated evidence map before relying on mutable product behavior. Authentication Each credential is bound to one declared environment and secret store. Product profiles, redirect URIs, event registrations, storage buckets, and consenting users are independently mapped. Instructions 1. Inventory organizations, projects, workspaces, credentials, services, profiles, users, URLs, storage, events, and billing owners. 2. Define isolation requirements and choose workspace, project, or organization separation for each threat and operational boundary. 3. Create a typed environment manifest with aliases and secret references but no values. 4. Add fail-closed assertions for organization/project/workspace, endpoint hosts, storage, event recipient, and production fixture bans. 5. Compare environment capabilities and run synthetic parity tests without copying production data. 6. Document promotion, drift detection, emergency disablement, rotation, teardown, and ownership. Tool Discipline Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-multi-env-setup