Agent skill · operations · jeremylongshore
adobe-incident-runbook
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".
Why this skill is useful
Provides specific commands and procedures for handling Adobe API outages that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, kubectl 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 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-incident-runbook