agentleFS
Sign inStart free
juanitourquizajuanitourquiza/shipframe/skills/incident-response/SKILL.md

incident-response

Skill4 starsChanged 22 days agoMITView on GitHub

Coordinate evidence-led incident response, first checking access to logs, metrics, and operational consoles.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dora-metrics, background-jobs and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jholhewresSkill

    dora-metrics

    Calculate DORA metrics from git + deploy logs

    Also in 3 projects that use this

  • YepAPISkill

    background-jobs

    Queue workers with BullMQ/Inngest/Trigger.dev, job retries, dead letter queues, concurrency.

    Also in 4 projects that use this

  • MicrosoftSkill

    data-modeling

    Use when the app needs to store or read data — records, a database, entities, CRUD, lists, "save/remember X", or per-user data with row-level security. This app's data layer is Rayfin's: you declare entities as TypeScript classes with decorators in rayfin/data/, register them in the schema, and read/write them through the typed rayfin-client. Covers: defining an @entity, field decorators, registering it, per-entity access with @role, owner-only row-level security, and the client query/mutation API. Triggers: data, database, model, entity, schema, table, record, CRUD, create, read, update, delete, list, store, save, persist, per-user, row-level security, RLS, access control, ownership.

    Also in 7 projects that use this

  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 4 projects that use this

  • mmondoraSkill

    infrastructure-as-code

    Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.

    Also in 5 projects that use this

  • csiddhant796-blipSkill

    threat-detection

    Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry. Covers hypothesis-driven threat hunting, IOC sweep generation, z-score anomaly detection, and MITRE ATT&CK-mapped signal prioritization.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Incident Response

Intent: incident — EN: production incident, outage, degradation, on-call response. ES: incidente de producción, caída, degradación, respuesta de guardia.

First deliverable: access check

Before diagnosis, confirm authorized access to relevant logs, metrics/traces, deployment history, and provider/operational consoles. Record which sources are accessible, their time range and freshness, and which are unavailable. If access is missing, stop investigation and make the access limitation, owner, and required grant the first deliverable. Never work around access controls.

Response

  1. Establish incident lead, severity rubric, affected service/tenants, start time, impact, and communications channel. Use the project's profile/runbook; do not invent severity or promise an ETA.
  2. Preserve evidence and timestamps. Prefer read-only queries. Avoid destructive actions, broad restarts, data edits, or customer communication without authorization.
  3. Build a timeline from verified signals; distinguish observations, hypotheses, and unknowns.
  4. Propose mitigations with risk, scope, rollback, and approval requirements. Execute only when explicitly authorized.
  5. Track owner and status for containment, recovery, and follow-up. Verify recovery against agreed user-facing signals.
  6. Produce a blameless postmortem using templates/postmortem.md; include impact, timeline, contributing factors, what worked, and owned/actionable follow-ups.

Host limits

Claude Code, Codex CLI, and OpenCode do not imply production access. Use only credentials/tools explicitly provided and authorized in the current host session. If access is absent, do not claim an incident diagnosis or resolution.

Resumen (ES)

Primero confirma acceso autorizado a logs, métricas/trazas, despliegues y consolas. Si falta acceso, ese es el primer entregable. Conserva evidencia, separa hechos de hipótesis, no ejecutes mitigaciones destructivas sin autorización y documenta el postmortem.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free