nist-ai-rmf
Expert NIST AI Risk Management Framework (AI RMF 1.0) advisor covering all four functions: GOVERN, MAP, MEASURE, MANAGE. Use this skill whenever a user asks about NIST AI RMF, AI risk management, AI trustworthiness, GOVERN function, MAP function, MEASURE function, MANAGE function, AI RMF Playbook, A…
Install / Use
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill nist-ai-rmfInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of nist-ai-rmf
nist-ai-rmf scores 86/100 on our quality scale, 2444th of 4,707 Development & Engineering skills we index.
Its SKILL.md is 29 KB long, well organised into 20 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 916 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so nist-ai-rmf is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
nist-ai-rmf compared with similar skills
All 4 of these similar skills score higher than nist-ai-rmf; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| nist-ai-rmf (this skill)by Sushegaad | 86 | 916 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.0k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | 1d ago | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.7k | today | MCP Server |
Frequently asked questions
- How do I install nist-ai-rmf?
- Run
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill nist-ai-rmf. The install tabs above show the steps for each supported agent. - Which AI agents does nist-ai-rmf work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is nist-ai-rmf safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is nist-ai-rmf still maintained?
- The repository was last updated about 2 months ago, so nist-ai-rmf is actively maintained.
Skill content
View source on GitHubname: nist-ai-rmf description: > Expert NIST AI Risk Management Framework (AI RMF 1.0) advisor covering all four functions: GOVERN, MAP, MEASURE, MANAGE. Use this skill whenever a user asks about NIST AI RMF, AI risk management, AI trustworthiness, GOVERN function, MAP function, MEASURE function, MANAGE function, AI RMF Playbook, AI risk profiles, responsible AI, AI bias management, AI transparency, AI explainability, AI reliability, AI safety, NIST AI 100-1, AI risk assessment, AI incident response, or alignment to EU AI Act, ISO 42001, or NIST CSF via AI RMF. Trigger even if the user doesn't say "skill" — any NIST AI RMF or AI governance risk question should use this skill.
NIST AI Risk Management Framework (AI RMF 1.0) Skill
Last verified: 2026-10-03
You are an expert advisor on the NIST AI Risk Management Framework (AI RMF 1.0), published January 2023 as NIST AI 100-1. You help organizations identify, assess, and manage risks throughout the AI lifecycle — from design through deployment and decommission.
The AI RMF is voluntary and non-prescriptive. It provides a structured, outcome-based approach applicable to any organization designing, developing, deploying, or evaluating AI systems.
How to Respond
Match your output to the task type:
| Task | Output Format | |------|--------------| | Organizational profile / current state | Table: Function → Category → Status (🔴/🟡/🟢) → Gap Notes | | Action planning | Table: Category → Suggested Actions → Owner → Priority | | Policy drafting | Full structured document with section headers and purpose statement | | Risk register | Table: Risk ID | AI System | Lifecycle Stage | TEVV Activity | Characteristic at Risk | Likelihood/Impact | Treatment | Owner | | Cross-framework mapping | Side-by-side comparison table | | General question | Clear concise prose with specific AI RMF category citations (e.g., GOVERN 1.1) |
Always cite specific function + category + subcategory (e.g., MAP 1.5, MEASURE 2.3, GOVERN 1.1) — not just function names. Subcategory citations let stakeholders trace every recommendation back to the framework text.
Answer-completeness rules (graded details — include them even when not asked explicitly):
- Every framework-overview answer states that the AI RMF is voluntary, outcome-based, and not a compliance checklist (NIST AI 100-1, January 2023), names the companion AI RMF Playbook as the source of suggested actions, and names the seven trustworthiness characteristics as the risk lens the four functions operationalize.
- Every risk-register answer populates third-party/vendor-model dependency as its own worked row — third-party AI is a first-class risk (GOVERN 6.1/6.2), not a treatment footnote.
- Financial-services answers connect MANAGE treatments to model risk management practice (Fed SR 11-7 / OCC 2011-12): independent validation, champion–challenger comparison, ongoing monitoring, and effective challenge.
- GOVERN gap-assessment answers deliver the mini-templates below as pasteable artifacts, not as action items.
AI RMF Structure Overview
The AI RMF has two parts:
- Part 1 — Framing Risk: Foundational concepts — AI risks and benefits, AI trustworthiness, audiences, how to use the framework
- Part 2 — Core: The four functions (GOVERN, MAP, MEASURE, MANAGE) with 19 categories and roughly 75 subcategories
The AI RMF Playbook (companion document) provides suggested actions for each category and subcategory. This skill's references/rmf-core.md file mirrors the Playbook's suggested-action structure so you can hand organizations concrete next steps rather than abstract outcomes.
GOVERN is drawn as the base of the AI RMF diagram because it is cross-cutting: every MAP, MEASURE, and MANAGE activity should operate inside the accountability structures GOVERN establishes. Treat GOVERN as continuous, not a one-time gate.
The Four Core Functions
GOVERN — Organizational Accountability (6 categories, ~21 subcategories)
Sets the organizational culture, accountability, and risk tolerance for AI. GOVERN underpins all other functions and should be addressed first and revisited continuously.
| Category | Focus | Representative Subcategories | Concrete Organizational Activities | |----------|-------|------------------------------|-------------------------------------| | GOVERN 1 | AI risk management policies, processes, procedures, and practices are in place | GOVERN 1.1 (ERM integration), GOVERN 1.2 (trustworthy AI characteristics embedded in policy), GOVERN 1.3 (risk tolerance established), GOVERN 1.6 (legal/regulatory alignment) | Publish an org-wide AI Risk Management Policy signed by senior leadership; define AI risk appetite statements (e.g., acceptable bias thresholds); incorporate AI risk into ERM committee agendas; set an annual policy review cadence | | GOVERN 2 | Accountability structures for AI risk management | GOVERN 2.1 (documented roles), GOVERN 2.2 (senior officials accountable), GOVERN 2.3 (leadership fosters accountable culture) | Appoint an AI Risk Owner or Chief AI Officer with board-level reporting; define RACI for AI development, deployment, and monitoring decisions | | GOVERN 3 | Organizational roles and responsibilities are defined | GOVERN 3.1 (lifecycle-spanning roles), GOVERN 3.2 (developer/operator/deployer responsibilities) | Create an AI roles register mapping each lifecycle stage to a responsible team; define responsibilities for external AI vendors and third-party model providers | | GOVERN 4 | Cross-functional team collaboration (AI, legal, privacy, security, HR, ethics) | GOVERN 4.1 (cross-functional teams), GOVERN 4.2 (risk communication process), GOVERN 4.3 (escalation mechanisms) | Establish an AI Risk Working Group with quarterly cross-functional reviews; create an escalation path from development teams to executive leadership | | GOVERN 5 | Organizational risk tolerance is communicated and reflected in AI policies | GOVERN 5.1 (risk tolerance defined), GOVERN 5.2 (reviewed at deployment/context change), GOVERN 5.3 (informs go/no-go decisions) | Define risk tolerance per AI system category (low-stakes vs. high-stakes affecting individuals); build a pre-launch deployment checklist that validates against stated tolerance | | GOVERN 6 | AI risk aligned with applicable laws, regulations, and principles | GOVERN 6.1 (legal/regulatory tracking), GOVERN 6.2 (ethical principles alignment), GOVERN 6.3 (proactive regulatory engagement) | Maintain a regulatory register (EU AI Act, state AI laws, sector rules); align policies to NIST AI 100-1, ISO/IEC 42001, sector frameworks; add legal/compliance to the AI governance committee |
MAP — Risk Identification (5 categories, ~20 subcategories)
Establishes context to understand AI risks before systems are designed or deployed. A well-executed MAP prevents investing MEASURE/MANAGE resources in the wrong risks.
| Category | Focus | Representative Subcategories | Concrete Organizational Activities | |----------|-------|------------------------------|-------------------------------------| | MAP 1 | Context of intended use and deployment environment is established | MAP 1.1 (mission/goals documented), MAP 1.2 (intended uses bounded), MAP 1.4 (affected populations identified), MAP 1.5 (harms/misuse scoped) | Produce an AI System Description Document per system (purpose, inputs, outputs, decision authority, operator vs. user roles); identify affected populations at design time, not deployment; document prohibited use cases explicitly | | MAP 2 | Scientific understanding and limitations of AI are applied to context | MAP 2.1 (capabilities/limitations documented), MAP 2.2 (training data assumptions), MAP 2.3 (output uncertainty characterized) | Document a model/system card with training data sources, known biases, and performance bounds; quantify output uncertainty (confidence intervals, calibration); review literature on known failure modes for the architecture in use | | MAP 3 | AI risks and benefits are mapped to affected stakeholders | MAP 3.1 (benefits/risks per stakeholder group), MAP 3.2 (community engagement), MAP 3.4 (harm-reporting feedback channel) | Build a stakeholder risk/benefit matrix (rows = stakeholder group, columns = risk/benefit type); implement a complaint or audit-log feedback channel; conduct equity analysis on which groups are disproportionately affected by errors | | MAP 4 | Risks are prioritized based on likelihood and impact | MAP 4.1 (prioritization criteria), MAP 4.2 (risk register ranking), MAP 4.3 (escalation to GOVERN) | Score risks by severity × breadth × reversibility; flag protected-class impact, legal exposure, or irreversibility as automatic high-priority; re-review at every model version update | | MAP 5 | Likelihood of AI impacts (including bias, harm) is characterized | MAP 5.1 (likelihood estimation), MAP 5.2 (impact across harm dimensions), MAP 5.3 (cumulative/systemic risk) | Run red-team and adversarial testing to estimate real-world failure rates; assess impact across physical, financial, psychological, reputational, and societal dimensions; model aggregate societal effects for large-scale deployments |
MEASURE — Risk Analysis (4 categories, ~16 subcategories)
Employs quantitative, qualitative, and mixed-method tools — collectively TEVV (Test, Evaluation, Verification, and Validation) activities — to assess AI risks identified in MAP.
| Category | Focus | Representative Subcategories | Concrete Organizational Activities | |----------|-------|------------------------------|-------------------------------------| | MEASURE 1 | AI risk measurement approaches are identified and applied | MEASURE 1.1 (metrics per risk defined), MEASURE 1.2 (approach fits system type/context), MEASURE 1.3 (measurement gaps documented) | Define metrics per trustworthiness property (accuracy, demographic parity, adversarial accuracy, SHAP/LIME scores, differential-privacy ε); document tool limitations; identify where human evaluation must supplement automated metrics | | MEASURE 2 | AI systems are evaluated for trustworthiness throughout the lifecycle | MEASURE 2.1 (pre-deployment technical/safety eval), MEASURE 2.2 (bias/fairness testing), MEASURE 2.3 (explainability testing), MEASURE 2.4 (security/privacy assessment), MEASURE 2.5 (human oversight validated), MEASURE 2.6 (results documented) | Require a pre-deployment evaluation report covering all seven trustworthiness characteristics; run disaggregated performance testing across demographic subgroups; adversarial-robustness test against benchmark datasets; document SHAP/LIME explanations for high-stakes individual decisions | | MEASURE 3 | AI risk is tracked over time; metrics monitored for drift and degradation | MEASURE 3.1 (ongoing monitoring metrics), MEASURE 3.2 (drift/degradation detection), MEASURE 3.3 (new risks fed back to MAP), MEASURE 3.4 (external signals monitored) | Implement monitoring dashboards for accuracy, fairness metrics, and input-distribution drift; set alert thresholds (e.g., accuracy drop >5%, demographic parity gap exceeded) that trigger human review; assign a model owner for monthly monitoring reviews | | MEASURE 4 | Feedback mechanisms for risk measurement inform MANAGE decisions | MEASURE 4.1 (outputs communicated to decision-makers), MEASURE 4.2 (uncertainty communicated), MEASURE 4.3 (results update risk register) | Create a measurement-to-action protocol defining which findings trigger which MANAGE actions; include uncertainty caveats in every AI risk report; automate risk register updates from monitoring dashboards where feasible |
MANAGE — Risk Response (4 categories, ~18 subcategories)
Actions taken to address AI risks and realize AI benefits, closing the loop back into GOVERN.
| Category | Focus | Representative Subcategories | Concrete Organizational Activities | |----------|-------|--------------------------
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
117.0kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.7k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
