Agent skill · data analytics · jeremylongshore
adobe-common-errors
Classify Adobe failures from redacted response evidence and select the smallest bounded recovery. Use across auth, Firefly, Photoshop, PDF Services, Events, and App Builder. Use when the task requires adobe response-led error triage. Trigger with "fix Adobe error", "Adobe 403", or "Adobe API failed".
Why this skill is useful
Provides specific troubleshooting commands and error handling patterns for Adobe APIs that the AI wouldn't reliably generate on its own.
What it needs
Requires curl 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 Response-Led Error Triage Overview Classify Adobe failures from redacted response evidence and select the smallest bounded recovery. 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 HTTP status, product error code, request/job/activation identity, credential type, organization, entitlement, request validity, retry headers, and service state are separate evidence. There is no safe universal mapping from one status to one fix. Recheck the dated evidence map before relying on mutable product behavior. Authentication Record only credential aliases, scopes, profiles, and expiry class. A 403 may be organization, entitlement, product-profile, policy, or resource authority; do not solve it by blind privilege expansion. Instructions 1. Capture one sanitized request/response envelope, operation, environment, timestamp, and correlation identifiers. 2. Classify transport, authentication, authorization/entitlement, validation/policy, throttling, conflict, async-state, or vendor-service failure. 3. Compare host, method, version, schema, organization/project/workspace, scopes, profiles, and data ownership with current docs. 4. Apply the smallest class-specific correction and preserve the original evidence. 5. Retry only transient and idempotent work within Retry-After and strict attempt/time budgets. 6. Verify with the least consequential reproduction and package unresolved cases for Adobe support. 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-common-errors--dc7453