agentleFS
Sign inStart free
JkudjoJkudjo/oh-my-cursor/skills/incident/SKILL.md

incident

Skill1 starsChanged 7 months agoMITView on GitHub

Production incident response — structured triage, hypothesis tree, safe remediation, incident record

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only until cause is confirmed

    line 19
  2. Distinctive:

    No destructive infra changes without explicit confirmation + rollback plan

    line 22
  3. Distinctive:

    No disabling auth during incident response

    line 23

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

incident

Full production incident response protocol. Handles the furnace scenarios — green metrics but users affected, regional failures, post-deploy regressions.

Phases

  1. Impact triage — scope, symptom, start time, blast radius (2 min)
  2. Evidence gathering — read-only: recent changes, error logs, traces, infra health, dependencies, regional scope
  3. Hypothesis tree — app, infra, data, client/observability — full tree before investigating any branch
  4. Safe remediation — root cause confirmed → state blast radius + rollback → fix → verify
  5. Incident record — timeline, root cause, fix, monitoring gap, follow-up

Hard rules

  • Read-only until cause is confirmed
  • Green metrics ≠ no incident — metrics lie via wrong thresholds, aggregation, wrong segment
  • "The deploy caused it" is a hypothesis, not a fact
  • No destructive infra changes without explicit confirmation + rollback plan
  • No disabling auth during incident response

Example

@incident "intermittent 503s in us-east after today's deploy — pods Running, CPU/memory normal"

Download now (ZIP)

  • Other versions21 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 21

    1. AsiaOstrich/universal-dev-standards★ 82same name
    2. DataWithBaraa/claude-code-data-engineering-skills★ 52same name
    3. manusco/resonance★ 38same name
    4. ulises-jeremias/agent-toolkit★ 19same name
    5. lalulali/vespyr★ 11same name
    6. greglas75/zuvo★ 8same name
    7. NotHarshhaa/devops-skills★ 8same name
    8. chancegraff/rules-for-claude★ 4same name
    9. gonimar/claude-web-studio★ 4same name
    10. umararshad4/honey-stack★ 4same name

    11 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use runbook, refactor 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.
    • AnthropicSkill

      runbook

      Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.

      Also in 3 projects that use this

    • GitHubSkill

      refactor

      Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

      Also in 8 projects that use this

    • anujdutt9Skill

      handover

      Also in 3 projects that use this

    • OpenAISkill

      observability

      Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

      Also in 3 projects that use this

    • VercelSkill

      deploy

      Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

      Also in 6 projects that use this

    • tuistSkill

      migrate

      Migrates existing Xcode projects to Tuist generated workspaces with build and run validation, external dependency mapping, and migration checklists. Use when adopting Tuist for an existing app or converting a hand-edited Xcode project to generated projects.

      Also in 3 projects that use this

  • In this repository22 other files it gives its agents.

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