Agent skill · software engineering · jeremylongshore
adobe-hello-world
Prove one Adobe API connection with a current, read-only or synthetic operation and a content-safe receipt. Use during onboarding before any production workflow. Use when the task requires adobe minimal access proof. Trigger with "Adobe hello world", "test Adobe connection", or "verify Adobe entitlement".
Why this skill is useful
Adds three executable scripts for Adobe API integrations that provide capabilities not commonly found in public documentation.
What it needs
Requires node 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 Minimal Access Proof Overview Prove one Adobe API connection with a current, read-only or synthetic operation and a content-safe receipt. 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 The smallest useful proof is product-specific: token acquisition alone does not demonstrate API entitlement. Prefer a documented read or a synthetic asynchronous job whose artifact can be safely deleted; do not use retired Photoshop v1, /sensei/cutout, or Lightroom Firefly Services endpoints. Recheck the dated evidence map before relying on mutable product behavior. Authentication Use a dedicated non-production credential or consenting test user and record only aliases, scope names, product profiles, response status, and request identifiers. Instructions 1. Resolve the exact Adobe organization, project, workspace, credential type, and service. 2. Read the current product quickstart and identify the least consequential documented proof. 3. Validate endpoint host, method, request schema, scopes, entitlement, and storage requirements offline. 4. Run exactly one bounded proof and capture redacted response and correlation evidence. 5. Verify the expected allow case and one safe denied or invalid fixture without broadening access. 6. Delete approved temporary assets and issue a pass, fail, or entitlement-blocked result. 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-hello-world--6eac80