sushegaad/claude-skills-governance-risk-and-compliance/nist-ai-rmf
Claude Code and agent skill by sushegaad/claude-skills-governance-risk-and-compliance
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install sushegaad/claude-skills-governance-risk-and-compliance/nist-ai-rmfSKILL.md
The same SKILL.md was published earlier as sushegaad/claude-skills-governance-risk-and-compliance/nist-ai-rmf.
NIST AI Risk Management Framework (AI RMF 1.0) Skill
Last verified: 2026-11-14
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 72 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, 19 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, transparent, and implemented effectively | GOVERN 1.1 (legal/regulatory requirements understood and managed), GOVERN 1.2 (trustworthy AI characteristics embedded in policy), GOVERN 1.3 (risk tolerance drives level of risk management), GOVERN 1.6 (AI system inventory) | Publish an org-wide AI Risk Management Policy signed by senior leadership; maintain a regulatory register (EU AI Act, state AI laws, sector rules); define AI risk appetite statements (e.g., acceptable bias thresholds); incorporate AI risk into ERM committee agendas; set an annual policy review cadence; keep a resourced AI system inventory | |
| GOVERN 2 | Accountability structures so teams and individuals are empowered, responsible, and trained | GOVERN 2.1 (documented roles, responsibilities, and lines of communication), GOVERN 2.2 (AI risk management training for personnel and partners), GOVERN 2.3 (executive leadership takes responsibility for AI risk decisions) | Appoint an AI Risk Owner or Chief AI Officer with board-level reporting; define RACI for AI development, deployment, and monitoring decisions; create an AI roles register mapping each lifecycle stage to a responsible team; train personnel and partners on AI risk duties | |
| GOVERN 3 | Workforce diversity, equity, inclusion, and accessibility processes are prioritized | GOVERN 3.1 (diverse teams inform AI risk decision-making), GOVERN 3.2 (roles and responsibilities for human-AI configurations and oversight) | Staff AI risk decisions with diverse teams across demographics, disciplines, and backgrounds; define and differentiate human-AI oversight roles: who operates, who oversees, who can override | |
| GOVERN 4 | Organizational teams are committed to a culture that considers and communicates AI risk | GOVERN 4.1 (safety-first, critical-thinking mindset), GOVERN 4.2 (teams document and communicate risks and impacts), GOVERN 4.3 (AI testing, incident identification, and information sharing) | Establish an AI Risk Working Group with quarterly cross-functional reviews; create an escalation path from development teams to executive leadership; maintain an incident log and information-sharing practices | |
| GOVERN 5 | Processes for robust engagement with relevant AI actors | GOVERN 5.1 (external feedback on individual and societal impacts collected and integrated), GOVERN 5.2 (adjudicated feedback incorporated into design and implementation) | Implement external feedback channels (complaint forms, community engagement); define an adjudication process that feeds accepted external feedback into system design on a regular cadence | |
| GOVERN 6 | Policies and procedures for third-party software, data, and supply chain risks | GOVERN 6.1 (third-party risks addressed, including IP infringement), GOVERN 6.2 (contingency processes for high-risk third-party failures) | Define contractual requirements for AI vendors and third-party model providers; maintain a third-party AI register; define fallback and contingency plans for failures in high-risk third-party data or AI systems |
MAP — Risk Identification (5 categories, 18 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 is established and understood | MAP 1.1 (intended purposes, uses, laws/norms, and deployment settings documented), MAP 1.3 (mission and goals documented), MAP 1.5 (risk tolerances determined and documented), MAP 1.6 (system requirements elicited from relevant AI actors) | 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 | Categorization of the AI system is performed | MAP 2.1 (tasks and methods defined, e.g., classifier, generative model, recommender), MAP 2.2 (knowledge limits and human oversight of outputs documented), MAP 2.3 (scientific integrity and TEVV considerations documented) | Document a model/system card with training data sources, known biases, knowledge limits, and performance bounds; review literature on known failure modes for the architecture in use; document data representativeness and construct validation | |
| MAP 3 | AI capabilities, targeted usage, goals, and expected benefits and costs are understood | MAP 3.1 (potential benefits documented), MAP 3.2 (potential costs including non-monetary costs documented), MAP 3.3 (targeted application scope specified), MAP 3.5 (human oversight processes defined) | Document expected benefits and costs of errors against benchmarks tied to risk tolerance; keep application scope bounded by demonstrated capability; define operator proficiency requirements and human oversight processes | |
| MAP 4 | Risks and benefits are mapped for all components, including third-party software and data | MAP 4.1 (legal and IP risks of components including third-party data/software mapped), MAP 4.2 (internal risk controls for components documented) | Maintain a component inventory (data sources, models, libraries, APIs) with risk and control status; map IP infringement and legal risk for third-party data and pre-trained models | |
| MAP 5 | Impacts to individuals, groups, communities, organizations, and society are characterized | MAP 5.1 (likelihood and magnitude of each impact characterized), MAP 5.2 (engagement with relevant AI actors and impact feedback) | Run red-team and adversarial testing to estimate real-world failure rates; assess impact across physical, financial, psychological, reputational, and societal dimensions; build a stakeholder risk/benefit matrix; implement a complaint or audit-log feedback channel; conduct equity analysis on which groups are disproportionately affected by errors |
MEASURE — Risk Analysis (4 categories, 22 subcategories)
Employs quantitative, qualitative, and mixed-method tools — collectively TEVV (Test, Evaluation, Verification, and Validation) activities — to assess AI risks identified in MAP.
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/nist-ai-rmf/skills/nist-ai-rmf/SKILL.md
Popularity
- Repository stars
- 886
- Repository forks
- 180
- 7-day trend score
- 34
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 8 Sep 2026, 2 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/sushegaad/claude-skills-governance-risk-and-compliance/nist-ai-rmf)