Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/adobe-common-errors

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/adobe-common-errors

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈81 tokens for metadata: the name and description. ≈847 when used: this file. ≈830 more on demand in 1 file.

Description uses 4.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈323 characters, or 4.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion.

Approval Boundaries

Scope/profile/credential changes require security and organization-owner approval. Prompt, document, asset, event registration, deploy, or retry changes require their respective owners.

Error Handling

  • Never infer a 24-hour token lifetime unless the actual token response proves it.
  • Never accept 429 as a successful CI test.
  • Do not dump raw HTTP traces containing Authorization or signed URLs.

Output

Return the evidence envelope, fault class, ruled-out causes, minimal action, retry decision, verification, and escalation packet. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Distinguish missing entitlement from expired auth on a 403 path.
  • Honor Retry-After on a synthetic 429 and stop at budget.

Validation

Exercise and record expected and observed results for:

  • 401
  • 403
  • validation/policy
  • 429
  • 5xx
  • unknown async state

Resources

  • Current first-party evidence map — recheck dated Adobe sources before execution.
  • Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is a comprehensive troubleshooting guide for Adobe APIs, providing standard diagnostic commands and recovery steps. It follows best practices for secret management by using environment variables for credentials and targets official Adobe service endpoints. The automated flag regarding remote execution is a false positive, as the skill uses a standard Python module to format JSON data rather than executing external code.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<service> <operation> <status-or-error>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "adobe",
  "errors"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/adobe-common-errors