incident-response
100 / 100 · Low risk
Fine to try.
Run a live incident: impact first, stabilise before root cause, roll back before you debug, one change at a time, an append-only timeline, recovery only on an observed signal. Includes the leaked-secret containment order (revoke or rotate, scope the exposure, purge, prove the old credential dead, record).
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'incident-response' ] || [ -L ~/.agents/skills/'incident-response' ]; then echo 'A skill folder named incident-response already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/theselfruleorg/polyrob' "$d" && git -C "$d" checkout --quiet '3a595c0e3db5aa91acc53dd80673c4d80e0721d1' -- 'data/prompts/skills/incident-response' && mkdir -p ~/.agents/skills && cp -R "$d"/'data/prompts/skills/incident-response' ~/.agents/skills/'incident-response' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'incident-response' ~/.claude/skills/'incident-response' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/theselfruleorg/polyrob/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-13 | 3a595c0 | 100 |
| 2026-11-08 | 7904368 | 100 |