agentleFS
Sign inStart free
joemccannjoemccann/radon/.claude/skills/incident-response/SKILL.md

incident-response

Skill34 starsChanged 49 days agoLicence not identifiedView on GitHub

The exact Radon triage playbook for a production incident - reproduce locally, write a FAILING regression test first, fix, run the full test gate, commit a focused single-purpose commit, push a fix/** branch, ensure an open PR (never merge), wait for CI green, verify live in the browser. Use whenever an incident JSON from data/incidents/ or a production bug report is being worked; /incident orchestrates the parallel-analysis phase on top of this playbook.

  • Commits and pushes

We split this skill into the rules it gives an agent

14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 61 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.

  • Other versions72 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 72

    1. anthropics/knowledge-work-plugins★ 34ksame name
    2. microsoft/hve-core★ 1.6ksame name
    3. hypnguyen1209/offensive-claude★ 401same name
    4. duyet/clickhouse-monitoring★ 305same name
    5. kid-sid/claude-spellbook★ 190same name
    6. irahardianto/awesome-agv★ 157same name
    7. harness/harness-skills★ 127same name
    8. nahid-sparktales/agent-dispatcher★ 59same name
    9. Happy-Technologies-LLC/happy-platform-skills★ 41same name
    10. drafthq/draft★ 40same name

    62 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 dora-metrics, data-modeling 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

    • 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 6 projects that use this

    • YepAPISkill

      background-jobs

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

      Also in 3 projects that use this

    • MasriyanSkill

      exploit-development

      Authorized exploit development and vulnerability research skill for lab environments, CTFs, owned software, crash analysis, memory corruption, exploitability assessment, fuzzing results, proof-of-concept design, and remediation. Use for defensive validation and education; avoid real-world weaponization, stealth, persistence, evasion, or unauthorized targets.

      Also in 3 projects that use this

    • motao123Skill

      browser-verification

      Use when a change needs browser-level evidence such as UI flow checks, form interaction validation, console inspection, or end-to-end smoke verification. This skill focuses on observable behavior instead of code assumptions.

      Also in 3 projects that use this

    • ffsshhttiikkSkill

      chaos-engineering

      Resilience testing through controlled experiments

      Also in 4 projects that use this

  • In this repository14 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