agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/cyber-risk-assessment/SKILL.md

cyber-risk-assessment

Skill1 starsChanged 25 days agoMITView on GitHub

Assesses cyber risk when leaders need prioritised threat scenarios, control gaps and treatment actions.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use during annual planning, after material change, before external assurance or following a significant incident.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cyber Risk Assessment

When to use it

Use during annual planning, after material change, before external assurance or following a significant incident.

What Claude needs

  • client-context.md for business background
  • Critical assets, systems, data and service dependencies
  • Current safeguards, incidents and testing evidence
  • Threat concerns, risk criteria and accountable owners

Method

  1. Identify crown-jewel assets and rank their confidentiality, integrity and availability needs.
  2. Build plausible threat scenarios linking actor, attack path, asset and business consequence.
  3. Evaluate inherent likelihood and impact using defined qualitative scales.
  4. Map current preventive, detective and recovery controls to each scenario.
  5. Assess residual exposure and test assumptions through a pre-mortem workshop.
  6. Prioritise avoid, reduce, transfer or accept treatments with owners and dates.

Output format

Provide an asset summary, scenario-based risk register and treatment plan with control, gap, residual rating, owner and due date.

Quality checks

  • Risks are written as cause, event and consequence.
  • Ratings follow stated criteria and cite evidence.
  • Treatments include validation measures and residual ownership.

Download now (ZIP)

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.