nist-ai-rmf
Skill9 starsChanged 7 months agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mastepanoski/claude-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mastepanoski/claude-skills★ 62same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository140 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alex-hormozi-pitchSkill
- AlgorithmSkill
- AnnualReportsSkill
- ArtGeneratorSkill
- artSkill
- autoplanSkill
- autoresearchSkill
- benchmarkSkill
- brainstormingSkill
- brand-guidelinesSkill
- brightdataSkill
- browseSkill
- BugHunterSkill
- CallIntelligenceSkill
- canarySkill
- canvasSkill
- carefulSkill
- ceo-advisorSkill
- cfo-advisorSkill
- cmmcSkill
- codebase-indexerSkill
- codexSkill
- CodingAgentSkill
- company-valuesSkill
- connect-chromeSkill
- CORESkill
- system-createcliSkill
- CreateskillSkill
- csoSkill
- cto-advisorSkill
- CybersecurityPlaybooksSkill
- defuddleSkill
- design-consultationSkill
- design-reviewSkill
- DevTeamSkill
- DiscordAdminSkill
- document-releaseSkill
- document-writerSkill
- doraSkill
- dpdpaSkill
- EmailManagerSkill
- executing-plansSkill
- fabricSkill
- fedrampSkill
- ffuf-web-fuzzingSkill
- find-communitySkill
- first-customersSkill
- FirstPrinciplesSkill
- form-croSkill
- freezeSkill
- gdpr-complianceSkill
- git-worktreesSkill
- GovernanceSkill
- grow-sustainablySkill
- gstack-upgradeSkill
- guardSkill
- hipaa-complianceSkill
- investigateSkill
- iso27001Skill
- The first 60 shown.
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
- Distinctive: line 35
Always cite specific function + category (e.g., MAP 1.5, MEASURE 2.3) — not just function names.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
NIST AI Risk Management Framework (AI RMF 1.0) Skill
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 | Risk Description | Likelihood | Impact | Treatment |
| 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 (e.g., MAP 1.5, MEASURE 2.3) — not just function names.
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 categories and subcategories
The AI RMF Playbook (companion document) provides suggested actions for each category and subcategory.
The Four Core Functions
GOVERN — Organizational Accountability (6 categories)
Sets the organizational culture, accountability, and risk tolerance for AI. GOVERN underpins all other functions.
| Category | Focus |
| GV-1 | AI risk management policies, processes, procedures and practices in place |
| GV-2 | Accountability structures for AI risk management |
| GV-3 | Organizational roles and responsibilities defined |
| GV-4 | Cross-functional team collaboration (AI, legal, privacy, security) |
| GV-5 | Organizational risk tolerance communicated and reflected in AI policies |
| GV-6 | Policies for AI risk aligned with applicable laws, regulations, principles |
MAP — Risk Identification (5 categories)
Establishes context to understand AI risks before systems are designed or deployed.
| Category | Focus |
| MP-1 | Context of intended use and deployment environment established |
| MP-2 | Scientific understanding and limitations of AI applied to context |
| MP-3 | AI risks and benefits are mapped to affected stakeholders |
| MP-4 | Risks are prioritized based on likelihood and impact |
| MP-5 | Likelihood of AI impacts (including bias, harm) characterized |
MEASURE — Risk Analysis (4 categories)
Employs quantitative, qualitative, and mixed-method tools to assess AI risks.
| Category | Focus |
| MS-1 | AI risk measurement approaches identified and applied |
| MS-2 | AI systems evaluated for trustworthiness throughout lifecycle |
| MS-3 | AI risk tracked over time; metrics monitored for drift and degradation |
| MS-4 | Feedback mechanisms for risk measurement inform MANAGE decisions |
MANAGE — Risk Response (4 categories)
Actions taken to address AI risks and realize benefits.
| Category | Focus |
| MG-1 | Risks prioritized and documented for treatment |
| MG-2 | Strategies to address AI risks planned, resourced, and actioned |
| MG-3 | AI risk responses monitored and adjusted; incident response in place |
| MG-4 | Risk treatment outcomes reviewed; lessons learned fed back into GOVERN |
Trustworthy AI Characteristics
The AI RMF defines seven trustworthiness properties that all AI systems should strive for. Use these when evaluating or scoring AI systems:
| Property | Key Questions |
| Accountable & Transparent | Can decisions be explained and traced to responsible parties? |
| Explainable & Interpretable | Can the model's behaviour be understood by technical and non-technical audiences? |
| Fair / Bias Managed | Are demographic biases identified, measured, and mitigated? |
| Privacy-Enhanced | Is PII minimized, protected, and handled per applicable laws? |
| Reliable | Does the system perform consistently within defined operational limits? |
| Resilient | Can the system withstand and recover from adversarial or unexpected inputs? |
| Safe | Are physical, psychological, and societal harms identified and controlled? |
| Secure & Cyber-Resilient | Is the system hardened against adversarial ML attacks (evasion, poisoning, extraction)? |
| Valid & Verified | Has the system been tested against intended use and verified for accuracy/robustness? |
Common Workflows
Gap Assessment
- For each of the 19 categories across GOVERN/MAP/MEASURE/MANAGE, rate status: 🔴 Not Started / 🟡 Partial / 🟢 Implemented
- For each 🔴/🟡, identify the specific gap and evidence needed
- Produce a prioritised remediation roadmap (Quick Wins → Medium Term → Long Term)
- Note which trustworthiness properties are most at risk
AI Risk Register Entry
Each entry should capture: Risk ID · AI system name · Lifecycle stage · Risk category · Trustworthiness property at risk · Likelihood · Impact · Treatment action · Owner · Review date
Incident Response (MANAGE 3.x)
- Trigger conditions: model accuracy degradation, bias threshold breach, adversarial attack, data drift
- Response steps: Contain → Assess impact → Notify stakeholders → Remediate → Document → Update risk register
Reference Files
For deeper content, read these files as needed:
- references/rmf-core.md — All 19 categories with full subcategory descriptions and Playbook suggested actions
- references/rmf-profiles.md — AI Risk Profiles, sector-specific guidance, trustworthy AI metrics, and cross-framework mapping (ISO 42001, EU AI Act, NIST CSF)
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
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.

