Risk & Compliance

Incident Severity & Response

An incident overview in, a severity band and response plan out — mapped against the response playbook and policies held in your Knowledge Hub.

  • Risk & Compliance
  • Traceable reasoning
  • Runs anywhere
Preview methodology

1–2 hours ~5 minutes

For one document, brief or record at a time

No coding required

Input
Risk registers, control descriptions and policy documents
Output
A scored register with the reasoning per risk
Runs in
Skillsize · ChatGPT · Claude · Copilot
Export
SKILL.md · MCP
Time saved
~1–2 hours per run

— USE CASES

What people use Incident Severity & Response for

Comparable registers

Score every risk identically, so results hold up across teams, entities and quarters.

Committee-ready evidence

Show the basis for each rating rather than asserting a residual score.

Coverage instead of sampling

Assess the whole of the risk universe in scope rather than the subset there was time for.

What it works from

  • Risk registers, control descriptions and policy documents
  • Your scoring scales, thresholds and appetite statements

What you get back

  • A scored register with the reasoning per risk
  • An aggregated view at the level the committee reads

Why this is expensive by hand

Assessing the risk universe in scope by hand means every assessor scores slightly differently and the register stops being comparable. Comparable registers is the typical trigger — score every risk identically, so results hold up across teams, entities and quarters. Done properly it is defensible; done at pace it becomes a judgement call nobody can retrace. And "properly" usually means 1–2 hours of manual work.

How this Skill produces it

As a Skill, the work is already sequenced. You bring the evidence, and the run produces a scored register with the reasoning per risk plus an aggregated view at the level the committee reads. The criteria, ordering and review points that make the answer trustworthy are encoded in the Skill itself — which is the difference between a structured method and a prompt someone pastes in. In effect, 1–2 hours of senior time compresses into ~5 minutes — and the output is comparable across clients, quarters and colleagues instead of shaped by whoever ran it.

Who it's for

  • Internal audit and risk functions
  • Compliance and controls teams
  • Second-line functions reporting to committees
  • Risk consultants running assessments

Run it in Skillsize — or export it anywhere

Incident Severity & Response exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.

ChatGPTClaudeCopilotAI Products (MCP)

More Risk & Compliance Skills

Browse the full library →