Agent skill · software engineering · jeremylongshore
adobe-debug-bundle
Assemble a minimal, reproducible Adobe diagnostic bundle with default-deny collection and verifiable redaction. Use for engineering or Adobe support escalation. Use when the task requires adobe redacted diagnostic bundle. Trigger with "Adobe debug bundle", "collect Adobe diagnostics", or "prepare Adobe support case".
Why this skill is useful
Adds an executable script for collecting Adobe API diagnostic information that isn't available in public documentation.
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 Redacted Diagnostic Bundle Overview Assemble a minimal, reproducible Adobe diagnostic bundle with default-deny collection and verifiable redaction. 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 Useful evidence is version, configuration-key presence, service/operation, environment aliases, timestamps, status/error class, request/job/activation identifiers, retry history, and a synthetic reproduction. Tokens, secrets, signed URLs, prompts, images, documents, event bodies, and customer identifiers are excluded by default. Recheck the dated evidence map before relying on mutable product behavior. Authentication Use one-way fingerprints only when correlation is necessary. Never call the IMS token endpoint merely to populate a support archive. Instructions 1. Define incident window, service, operation, data classification, recipients, retention, and custodian. 2. Create an allowlist manifest before collection and enumerate explicitly forbidden fields and file classes. 3. Collect dependency locks, deployment revision, sanitized configuration keys, status/error evidence, and correlation IDs. 4. Reproduce with a synthetic fixture or read-only check and record expected versus observed behavior. 5. Run secret, URL, PII, document/image, prompt, and identifier canaries across every output. 6. Hash the bundle, record redactions and gaps, transfer through an approved channel, and schedule deletion. 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-debug-bundle