Agent skill · software engineering · jeremylongshore
adobe-install-auth
Select and prove the correct Adobe authentication model, entitlement, product profile, and secret lifecycle before integration work. Use when creating or repairing Adobe credentials. Trigger with "set up Adobe auth", "Adobe OAuth server-to-server", or "Adobe user authentication".
Why this skill is useful
Adds executable scripts for OAuth authentication and SDK installation specific to Adobe services that are not commonly known.
What it needs
Requires node, python 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 Authentication and Entitlement Intake Overview Select and prove the correct Adobe authentication model, entitlement, product profile, and secret lifecycle before integration work. 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 OAuth Server-to-Server uses client credentials for application- or organization-owned data. User Authentication uses authorization code, explicit user consent, and optional offline access for user-owned data. Service Account JWT is deprecated and is never a valid new-work fallback. Recheck the dated evidence map before relying on mutable product behavior. Authentication Keep client secrets and refresh tokens in an approved server-side secret store. Product profiles constrain organization data; scopes and a valid token do not prove entitlement by themselves. Instructions 1. Classify the API, data owner, organization, environment, and whether a user must consent. 2. Confirm the service is visible in the selected Developer Console organization and identify its license and admin owner. 3. Choose OAuth Server-to-Server or User Authentication from the ownership contract; reject JWT configuration. 4. Select only required scopes and product profiles and record requested versus granted authority. 5. Acquire a token through an established OAuth library and run one read-only, product-specific proof. 6. Document expiry, refresh, revocation, rotation, break-glass, and owner-transfer procedures. 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-install-auth--91d089