SkillAgentSearch skills...

adobe-incident-runbook

Triage, contain, recover, and review Adobe auth, product, async-job, event, storage, spend, or App Builder incidents with evidence

Install / Use

npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-incident-runbook

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of adobe-incident-runbook

adobe-incident-runbook scores 83/100 on our quality scale, 3030th of 4,700 Development & Engineering skills we index.

Its SKILL.md is 4.1 KB long, well organised into 13 sections and no code examples: a solid amount of guidance for an agent.

With 2,785 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so adobe-incident-runbook is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

adobe-incident-runbook compared with similar skills

All 4 of these similar skills score higher than adobe-incident-runbook; compare them before choosing.

SkillScoreStarsUpdatedFormat
adobe-incident-runbook (this skill)by jeremylongshore832.8k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install adobe-incident-runbook?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-incident-runbook. The install tabs above show the steps for each supported agent.
Which AI agents does adobe-incident-runbook work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is adobe-incident-runbook safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is adobe-incident-runbook still maintained?
The repository was last updated about 2 months ago, so adobe-incident-runbook is actively maintained.

name: adobe-incident-runbook description: >- 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". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<service> <impact> <incident-window>" version: 1.8.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io 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"

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.

Related Skills

View on GitHub
GitHub Stars2.8k
CategoryDevelopment
Updated1mo ago
Forks404

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions