Agent skill · software engineering · jeremylongshore
adobe-ci-integration
Build deterministic CI gates for Adobe adapters without giving fork jobs credentials or spending against live creative/document APIs. Use when testing integration changes. Trigger with "test Adobe in CI", "Adobe contract tests", or "gate Adobe deploy".
Why this skill is useful
Adds a complete CI/CD pipeline configuration with executable scripts for Adobe API testing and credential management that aren't in public docs.
What it needs
Requires gh, npm 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 Contract-Safe CI Overview Build deterministic CI gates for Adobe adapters without giving fork jobs credentials or spending against live creative/document APIs. 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 Pull requests can prove routes, headers, schemas, polling, redaction, EOL bans, errors, and retries offline. Live tests require a protected trusted branch, non-production project/workspace, synthetic fixtures, strict budget, and explicit mutation/cleanup boundaries. Recheck the dated evidence map before relying on mutable product behavior. Authentication Fork and untrusted PR jobs receive no secrets. Protected lanes use environment-scoped credentials and record aliases only; secret canaries gate artifacts and logs. Instructions 1. Map CI trust boundaries, service adapters, fixtures, secret sources, deploy workflows, and fork behavior. 2. Add offline request/response contracts for auth, async URLs, PDF assets, webhooks, errors, throttling, and EOL endpoints. 3. Separate untrusted PR jobs from protected credentialed smoke and deploy jobs. 4. Use synthetic inputs, transaction/generation ceilings, serialized jobs, and deterministic cleanup in any live lane. 5. Gate on secret scans, obsolete-route scans, negative cases, generated-file checks, and immutable artifact identity. 6. Treat skipped trusted tests as unknown and retain redacted receipts plus cleanup evidence. 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-ci-integration--bb6fe7