메뉴
How to write up an incident so the next person can act on it, not just read it.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/vstorm-co/agenticos --skill incident-report명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | incident-report |
| description | How to write up an incident so the next person can act on it, not just read it. |
| category | operations |
An incident report is written for somebody who was not there, reading it under time pressure, six months later. Everything below follows from that.
Impact first. Who was affected, for how long, and what they could not do. A report that opens with architecture makes the reader work to find out whether it matters.
Then the timeline: what happened, in order, with times. Then the cause. Then what is being changed.
Times are absolute and in UTC. "Twenty minutes later" forces the reader to do arithmetic while comparing two reports.
Name systems, not people. "The deploy job did not wait for the migration" is actionable. "Marek deployed too early" is not, and it makes the next person quieter about their own mistakes.
Separate what is known from what is believed. Write "we think" where it is a theory. A report that reads as certain and is wrong is worse than one that says which part is a guess.
Every action item has an owner and a date, or it is not an action item -
it is a wish. Load template.md for the structure to fill in.
Do not write "human error" as a cause. It is where the investigation stops being useful: a system that a tired person can break at 3am is the finding.
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.