
iso-42001-ai-governance
AI governance readiness and gap assessment using ISO/IEC 42001:2023. Evaluate AI management-system practices for risk management, accountability, transparency, security, and continuous improvement.
- Installs
- 286
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mastepanoski/claude-skills --skill iso-42001-ai-governance- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads iso-42001-ai-governance automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
ISO 42001 AI Governance Audit
This skill enables AI agents to perform a comprehensive AI governance readiness and gap assessment based on ISO/IEC 42001:2023 - the international standard for Artificial Intelligence Management Systems (AIMS).
ISO 42001 provides a framework for responsible development, deployment, and use of AI systems, addressing risks, ethics, security, transparency, and regulatory compliance.
Use this skill to evaluate whether AI projects follow international best practices, manage risks effectively, and maintain ethical standards throughout the AI lifecycle.
Certification boundary: This skill can prepare evidence and identify gaps, but it is not a certification audit. Do not claim ISO/IEC 42001 conformance unless a qualified auditor or certification process verifies it.
Combine with security audits, code reviews, or ethical AI assessments for comprehensive AI system evaluation.
When to Use This Skill
Invoke this skill when:
- Developing or integrating AI systems
- Ensuring AI governance and compliance
- Managing AI risks and ethical concerns
- Preparing for AI regulatory requirements (EU AI Act, etc.)
- Auditing existing AI implementations
- Establishing AI governance frameworks
- Responding to AI security or bias incidents
- Planning responsible AI deployment
- Documenting AI systems for stakeholders
Inputs Required
When executing this audit, gather:
- ai_system_description: Detailed description (purpose, capabilities, data used, users affected, deployment context) [REQUIRED]
- use_case: Specific application (e.g., hiring tool, medical diagnosis, content moderation) [REQUIRED]
- risk_category: High-risk, limited-risk, or minimal-risk per EU AI Act classification [OPTIONAL but recommended]
- existing_documentation: Technical docs, data sheets, model cards, risk assessments [OPTIONAL]
- stakeholders: Who develops, deploys, uses, and is affected by the AI [OPTIONAL]
- regulatory_context: Applicable laws (GDPR, EU AI Act, industry regulations) [OPTIONAL]
- impact_assessment_context: Existing or needed AI impact assessments, especially for systems affecting individuals, groups, or society [OPTIONAL]
ISO 42001 Framework Overview
ISO 42001 is structured around 10 key clauses plus supporting annexes:
Core Clauses
- Scope - Define AIMS boundaries
- Normative References - Related standards
- Terms and Definitions - AI terminology
- Context of Organization - Internal/external factors
- Leadership - Management commitment and roles
- Planning - Objectives and risk management
- Support - Resources, competence, communication
- Operation - AI system lifecycle management
- Performance Evaluation - Monitoring and measurement
- Improvement - Continual enhancement
Key ISO 42001 Principles
1. Risk-Based Approach
- Identify, assess, and mitigate AI-specific risks
- Consider technical, ethical, legal, and social risks
- Proportionate controls based on risk level
2. Ethical AI
- Fairness and non-discrimination
- Transparency and explainability
- Human oversight and control
- Privacy and data protection
- Accountability
3. Lifecycle Management
- Design → Development → Deployment → Monitoring → Decommissioning
- Continuous evaluation and improvement
- Documentation throughout
4. Stakeholder Engagement
- Involve affected parties
- Clear communication about AI use
- Mechanisms for feedback and redress
Related ISO AI Standards
Use ISO/IEC 42001 as the management-system anchor. When the request focuses on social, human, environmental, or lifecycle impact assessment, also reference ISO/IEC 42005:2025 as a companion standard for AI system impact assessments. When the request focuses on risk methodology, consider ISO/IEC 23894 as supporting guidance.
Audit Procedure
Work through seven steps, each mapped to ISO 42001 clauses. The full control-by-control
checklists — evaluation questions, scoring rubrics, example risks, and the seven AI
lifecycle stages — live in references/audit-procedure.md.
Read the section for the step you are on rather than loading the whole file at once.
| Step | Focus | ISO 42001 Clause | Est. |
|---|---|---|---|
| 1. Context & Scope | AIMS boundaries, stakeholders, EU AI Act risk classification | 4 | 15 min |
| 2. Leadership & Governance | Management commitment, AI policy, roles & responsibilities | 5 | 20 min |
| 3. Planning & Risk Management | Risk categories, assessment process, AI objectives | 6 | 30 min |
| 4. Support & Resources | Resources, competence, awareness, communication, documentation | 7 | 20 min |
| 5. Operation (AI Lifecycle) | Design → data → development → validation → deployment → monitoring → decommissioning | 8 | 40 min |
| 6. Performance Evaluation | KPIs, internal audit, management review | 9 | 20 min |
| 7. Improvement | Nonconformity, corrective action, continual improvement (PDCA) | 10 | 15 min |
For each step: evaluate the documented controls, record evidence vs. gaps, assign a clause score (0–10), and carry the findings into the report.
Output Format
Assemble findings into the standard ISO 42001 audit report. The copy-ready template
and a clause-by-clause self-assessment checklist are in
references/report-template.md.
The report covers, in order:
- Executive Summary — overall conformance, per-clause status table, risk classification, top 5 critical findings, positive highlights
- Detailed Findings — clause-by-clause analysis with evidence, gaps, and recommendations
- Risk Assessment Summary — critical/high risks with controls, owners, and deadlines
- Compliance Roadmap — phased actions (0–3 / 3–6 / 6–12 months)
- Documentation Requirements — missing artifacts to create
- Recommendations by Stakeholder — leadership, AI teams, legal/compliance, operations
- Next Steps — immediate through long-term
- Appendices — checklist, risk register, glossary, references
Best Practices
- Start with Risk Assessment: Prioritize based on AI risk level
- Document Everything: ISO 42001 requires extensive documentation
- Engage Stakeholders Early: Include affected parties in governance
- Use Existing Frameworks: Leverage NIST AI RMF, EU AI Act requirements
- Automate Monitoring: Build MLOps with governance built-in
- Train Your Team: ISO 42001 requires competent personnel
- Regular Audits: Don't wait for problems—proactive reviews
- Learn from Incidents: Every issue is improvement opportunity
- Balance Innovation and Safety: Responsible AI doesn't mean no AI
- Seek Independent Review When Needed: Third-party ISO 42001 certification can add credibility, but this skill only supports readiness and evidence preparation
Regulatory Alignment
ISO 42001 aligns with major AI regulations:
EU AI Act:
- Risk classification framework
- High-risk AI obligations
- Transparency requirements
- Conformity assessment
GDPR:
- Data protection by design
- Privacy impact assessments
- Data subject rights
- Lawful processing
NIST AI RMF:
- Govern, Map, Measure, Manage functions
- Risk-based approach
- Trustworthy AI characteristics
ISO/IEC 42005:2025:
- AI system impact assessment
- Human, social, and environmental impacts across the lifecycle
- Transparent documentation of foreseeable impacts
Sector-Specific:
- Healthcare: FDA AI/ML guidance, MDR
- Finance: Model Risk Management (SR 11-7)
- Employment: EEOC AI guidance
Common Pitfalls
- "We'll add governance later" - Build it in from the start
- Treating ISO 42001 as one-time exercise - It's continual
- Documentation without implementation - Must be operational
- Ignoring low-risk AI - Even minimal-risk needs baseline governance
- No stakeholder engagement - Affected parties must be involved
- Insufficient resources - Responsible AI requires investment
- Lack of monitoring - Deploy-and-forget is non-compliant
- No incident response plan - When AI fails, you need a plan
- Training as checkbox - Teams must truly understand responsible AI
- Copying templates without customization - Tailor to your context
Version
1.0 - Initial release based on ISO/IEC 42001:2023
Remember: ISO 42001 is about building trustworthy AI systems through systematic risk management and governance. It's not a barrier to innovation—it's a framework for responsible innovation that protects both organizations and the people affected by AI.
FAQ
What does the iso-42001-ai-governance skill do?
AI governance readiness and gap assessment using ISO/IEC 42001:2023. Evaluate AI management-system practices for risk management, accountability, transparency, security, and continuous improvement.
How do I install iso-42001-ai-governance?
Run npx skills add https://github.com/mastepanoski/claude-skills --skill iso-42001-ai-governance in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/iso-42001-ai-governance/ (personal) or .claude/skills/iso-42001-ai-governance/ (project).
Which AI agents can use iso-42001-ai-governance?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is iso-42001-ai-governance safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains iso-42001-ai-governance?
It is published by mastepanoski in mastepanoski/claude-skills. It has 286 recorded installs.
More from mastepanoski/claude-skills
wcag-accessibility-audit
mastepanoski/claude-skills
Comprehensive web accessibility audit using WCAG 2.1/2.2 guidelines. Evaluate compliance across 4 POUR principles (Perceivable, Operable, Understandable, Robust) with A, AA, AAA conformance levels.
ui-design-review
mastepanoski/claude-skills
Comprehensive visual design and aesthetics evaluation. Analyzes typography, color, spacing, hierarchy, consistency, branding, and current product-category conventions for polished, professional interfaces.
ux-audit-rethink
mastepanoski/claude-skills
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
nielsen-heuristics-audit
mastepanoski/claude-skills
Evaluate UX/UI using Jakob Nielsen's 10 usability heuristics. Comprehensive audit of visibility, control, consistency, error prevention, recognition, flexibility, aesthetics, error recovery, and documentation.
cognitive-walkthrough
mastepanoski/claude-skills
Deep-dive usability evaluation of specific user tasks. Simulates novice user cognition step-by-step to identify learnability issues, unclear actions, and points of confusion.
owasp-llm-top10
mastepanoski/claude-skills
Security audit for LLM and GenAI applications using OWASP Top 10 for LLM Apps 2025. Assess prompt injection, data leakage, supply chain, and 7 more critical vulnerabilities.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.