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

/adobe-incident-runbook

@820dfc8
Run it yourself

Triage, contain, recover, and review Adobe auth, product, async-job, event, storage, spend, or App Builder incidents with evidence. Use when the task requires adobe integration incident command. Trigger with "Adobe incident", "Firefly outage", or "Adobe credential leak".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈74 tokens for metadata: the name and description. ≈880 when used: this file. ≈785 more on demand in 1 file.

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

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 Integration Incident Command

Overview

Triage, contain, recover, and review Adobe auth, product, async-job, event, storage, spend, or App Builder incidents with evidence. 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

Vendor status, local deployment, credentials/entitlement, request validity, queues, storage, and downstream systems are separate failure domains. Containment preserves evidence while stopping new harm; recovery never starts with blind retry or credential deletion. Recheck the dated evidence map before relying on mutable product behavior.

Authentication

A suspected secret or signed-URL exposure is a security incident. Add/rotate/deploy/verify before approved old-secret deletion; invalidate exposed temporary access and preserve last-use evidence.

Instructions

  1. Declare severity, commander, service/operation, environment, customer/data/spend impact, and incident clock.
  2. Freeze risky deploys/replays and capture content-safe request/job/activation IDs, queue state, artifact revision, and vendor status.
  3. Classify local, auth/entitlement, validation/policy, throttling, vendor, event-delivery, storage, or downstream failure.
  4. Contain via queue pause, circuit, credential rotation, registration disablement, or traffic rollback according to owner authority.
  5. Recover with one bounded synthetic canary, reconcile ambiguous jobs/events/assets, and restore traffic in stages.
  6. Verify data/spend/cleanup, communicate status, preserve timeline, and assign corrective actions with evidence.

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

Commander coordinates; security authorizes secret response; product/data/budget owners authorize replay, generation, transfer, or deletion; release owner authorizes rollback/redeploy.

Error Handling

  • Do not delete the only credential during containment.
  • Do not replay unknown PDF/Firefly jobs without reconciliation.
  • Do not declare recovery from endpoint health alone.

Output

Return severity, timeline, evidence, fault domain, containment, recovery tests, reconciliation, customer/data/spend impact, and follow-ups. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Contain a synthetic leaked secret with overlap rotation.
  • Recover a queue after vendor 429s without duplicate submissions.

Validation

Exercise and record expected and observed results for:

  • credential exposure
  • entitlement loss
  • 429 storm
  • unknown jobs
  • event disablement
  • rollback

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 legitimate incident response runbook for managing Adobe API integrations. It includes standard troubleshooting commands for service health checks, authentication recovery, and log analysis. While automated scanners flagged a potential remote code execution pattern, analysis confirms this is a false positive used for formatting JSON data. The skill follows security best practices by recommending secret managers instead of hardcoded credentials.

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