Index of every page on this site: llms.txt
All skills
Run it yourself

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

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈85 tokens for metadata: the name and description. ≈863 when used: this file. ≈799 more on demand in 1 file.

Description uses 4.2% 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 ≈339 characters, or 4.2%.

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

Approval Boundaries

Incident and data owners approve collection; security approves external disclosure. Any broader trace, content sample, or retention extension requires a fresh explicit approval.

Error Handling

  • Abort if an Authorization header, token, client secret, refresh token, signed URL, or customer content survives.
  • Do not execute speculative network probes against production.
  • Quarantine a bundle whose audience or deletion owner is unknown.

Output

Return a minimal archive, allowlist manifest, hashes, redaction scan, reproduction, custody log, expiry, and deletion owner. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Diagnose a synthetic 429 without credential or content values.
  • Reject a bundle containing a pre-signed asset URL.

Validation

Exercise and record expected and observed results for:

  • secret canary
  • signed URL
  • content canary
  • request ID
  • external transfer
  • expiry deletion

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

    This skill is a diagnostic tool designed to help troubleshoot Adobe API issues by collecting system information, SDK versions, and connectivity status into a redacted debug bundle.

  • 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> <incident-window> <audience>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "adobe",
  "diagnostics"
]
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-debug-bundle