CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-risk-management

Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the security slice). Use when the user mentions 'AI risk,' 'AI governance,' 'NIST AI RMF,' 'AI compliance,' 'ML governance,' 'model risk management,' 'AI fairness,' 'AI bias,' 'algorithmic accountability,' 'AI Bill of Rights,' 'EU AI Act,' 'AI transparency,' 'model card,' 'AI red-team program,' 'AI safety,' 'responsible AI,' 'model drift,' 'concept drift,' 'AI monitoring,' 'AI incident,' or needs to assess or govern an AI / ML system.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, well-structured assessment workflow with strong sequencing, explicit checkpoints, a concrete output template, and a current, dated regulatory mapping. Its main weaknesses are the inline date-sensitive regulatory detail that belongs in a reference file, tool names without example invocations in the MEASURE step, and occasional concept glosses that add tokens without adding guidance.

Suggestions

Move the regulatory timeline and law-by-law detail (EU AI Act dates, Colorado SB26-189 history, EO chronology) into a references/regulatory-status.md file, keeping only the risk tiers and the as-of/re-check note in SKILL.md — this trims date-rotting tokens from the main file and improves progressive disclosure.

Add one concrete metric example to the MEASURE step (e.g., computing a disparate-impact ratio or equalized-odds difference with fairlearn.metrics) so the fairness evaluation is executable rather than purely descriptive.

Trim glosses of concepts Claude already knows (model cards, demographic parity definitions) and rationale sentences like 'A model that cannot be explained at all is a model you cannot defend in a regulatory inquiry' to tighten token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient — tables and terse lists assume competence (Fairlearn, SHAP, LIME, HELM are named without explanation) — but there are trimmable spots: concept glosses ('Model cards — Google's documentation pattern for ML models'), rationale sentences ('A model that cannot be explained at all is a model you cannot defend in a regulatory inquiry'), and a date-heavy inline regulatory timeline ('2 Dec 2027 | Annex III high-risk obligations — moved from 2 Aug 2026…'). Fits the level-4 anchor (efficient, minor over-explanation); not 5 because the date-sensitive regulatory detail adds substantial inline tokens, and not 3 because nearly everything is domain-specific operational content rather than padding.

4 / 5

Actionability

Concrete throughout for an instruction-only skill: named metrics ('equalized odds,' 'calibration,' 'individual fairness'), named tooling ('fairlearn.metrics,' 'aif360.metrics,' Foolbox, ART), a risk-to-treatment table with specific options, and a copy-paste-ready output format template with checklists. Falls short of the level-5 anchor because the MEASURE step names tools and metrics without a single example invocation or worked snippet — a minor gap, matching level 4.

4 / 5

Workflow Clarity

A clearly numbered five-step sequence (Inventory → MAP → MEASURE → MANAGE → GOVERN) where each step feeds the next ('For each material risk surfaced in MEASURE,' 'The MAP step should have decided which is most important'), with explicit validation checkpoints ('re-check dates against the primary source before relying on them,' 'state the as of date in the report'), severity ratings gating treatment, and a GOVERN posture checklist in the output template. Matches the level-5 anchor (clear sequence, explicit validation, checklists); feedback loops are not applicable to a non-destructive assessment workflow.

5 / 5

Progressive Disclosure

No bundle files exist, so all content is inline in one ~250-line file. Structure is good — clear section headers, tables, a References section of external citations, and cross-references to sibling skills — but content that would live better in a separate reference file (the EU AI Act timeline, state-law history like 'SB26-189 (signed 14 May 2026) repealed and re-enacted it') is inlined. Matches level 4 (good structure, minor organization gaps); not 5, since there are no one-level-deep bundle references and the body is well past single-file ideal size.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: it states a concrete capability scope anchored to a named framework, explicitly delineates the adjacent prompt-injection skill, and provides an explicit 'Use when' clause with over twenty natural trigger phrases including synonyms. It fully satisfies all four dimensions at the top anchor.

DimensionReasoningScore

Specificity

Names the governing action ('Apply the NIST AI Risk Management Framework (AI RMF 1.0)') and enumerates eight concrete capability areas — 'model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response' — which is comprehensive coverage for the domain, matching the level-5 anchor. Not 4: the coverage has no minor gaps; it spans the whole AI-risk lifecycle.

5 / 5

Completeness

Explicitly answers 'what' (apply NIST AI RMF and adjacent guidance to AI/ML systems, with enumerated scope) and 'when' via a literal 'Use when the user mentions…' clause with concrete trigger phrases plus 'or needs to assess or govern an AI / ML system.' This matches the level-5 anchor exactly; level 4 would require the 'when' to be less explicit or specific.

5 / 5

Trigger Term Quality

The quoted trigger list spans 20+ natural phrases a user would actually say — 'AI risk,' 'NIST AI RMF,' 'AI bias,' 'model drift,' 'concept drift,' 'EU AI Act,' 'model card,' 'AI red-team program,' 'AI incident' — including synonyms and variations, matching the level-5 comprehensive-coverage anchor. Not 4: no natural term is obviously missing; even adjacent phrasings ('responsible AI,' 'algorithmic accountability') are covered.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (lifecycle-wide AI risk management rather than the security slice), and the nearest conflict is explicitly carved out — 'Broader than prompt-injection (which is the security slice)' — with every trigger term specific to AI governance/risk. Matches the level-5 'clear niche with distinct triggers; minimal conflict risk' anchor; not 4, because no meaningful overlap with closely related skills is left unaddressed.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/ai-risk-management/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.