Agent skill · data analytics · jeremylongshore
adobe-advanced-troubleshooting
Isolate complex Adobe failures across DNS/TLS, auth, entitlement, schema, async state, storage, Runtime, and downstream layers without leaking credentials or content. Use when the task requires adobe layered failure isolation. Trigger with "deep debug Adobe", "Adobe job stuck", or "Adobe intermittent failure".
Why this skill is useful
Provides advanced debugging techniques and specific commands for troubleshooting Adobe API issues that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq, tcpdump 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 Layered Failure Isolation Overview Isolate complex Adobe failures across DNS/TLS, auth, entitlement, schema, async state, storage, Runtime, and downstream layers without leaking credentials or content. 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 Troubleshooting proceeds from sanitized wire facts and known control boundaries. Decoding a bearer token locally is not authoritative proof of entitlement and raw verbose traces are unsafe defaults; use token response metadata, Console assignments, and request/job IDs. Recheck the dated evidence map before relying on mutable product behavior. Authentication Collect aliases, scope/profile names, expiry class, last rotation/use evidence, and correlation IDs. Never expose token payloads, Authorization, signed URLs, prompts, documents, images, or event bodies. Instructions 1. Freeze speculative retries and capture one redacted failure envelope, topology, time window, and expected contract. 2. Check DNS/TLS/egress and service status without sending customer data or credentials to unapproved tools. 3. Verify credential type, organization/project/workspace, entitlement, scopes, profiles, host, method, version, and schema. 4. Trace submission, returned status URL, polling, terminal state, storage access, webhook/activation, and downstream acknowledgement. 5. Compare a synthetic control and the failing path one layer at a time while preserving request/job/activation IDs. 6. State the isolated layer, falsified hypotheses, minimal remediation, verification, and Adobe escalation evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-advanced-troubleshooting