Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, and preparing for audit. Use this to stand up a risk program, assess the risk in a decision or initiative, prepare for a certification or audit, decide whether a risk should be accepted, mitigated, transferred, or avoided, or report risk posture to leadership.
npx skills add https://github.com/cbrock84/headcount --skill enterprise-risk
A risk that is not written down with an owner is not managed. Each entry carries:
category, not a risk. "If an employee's credentials are phished, an attacker reaches customer
records" is a risk you can do something about.
the score.
omitted.
Mitigate (reduce it), transfer (insure or contract it away), avoid (do not do the
thing), or accept. Accepting is legitimate and often correct — but acceptance must be explicit,
at the right level of authority, and recorded. Risk accepted by silence is risk nobody owns.
Anything above the threshold that only the chief executive can accept goes to them. Never let an
unacceptable risk be quietly downgraded to fit an existing authority.
Two failure modes, both common:
Re-assess on a schedule and require evidence for any reduction. A control's existence is not
evidence it works; a test of the control is.
Continuous, not a project. What auditors need: documented policies, evidence they are followed,
records of exceptions and approvals, and a clear line from the framework's requirement to your
control to the evidence.
Collect evidence as work happens. Assembling a year of it retrospectively is expensive, and gaps
found then cannot be fixed retroactively.
Leadership needs the few risks whose residual exposure is above appetite, what is being done, and
what needs a decision. Not the whole register. A risk report that requires reading forty rows to
find the three that matter will not be read.
Take cbrock84/enterprise-risk from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.