aims-audit
ISO 42001 AI readiness check. Use before a stage 1 or internal audit, or /compliance-os:aims-audit.
Target: Target not categorized. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- /compliance-os:aims-audit — AIMS ISO 42001 Forcing Questions
- When to Run
- The Six AIMS Questions
- 1. Does the AIMS scope statement name every AI system?
- 2. Does the AI policy commit to lawful use AND beneficial purpose AND human oversight AND continual improvement?
- 3. What's the risk register coverage, and which Annex A controls treat each risk?
- 4. Has the AI risk assessment been re-run since the last material model change?
- 5. What's the Clause 9.2 internal audit plan, and is auditor independence respected?
Command: /compliance-os:aims-audit The ISO 42001 AIMS specialist pressure-tests any AI Management System work. Six questions before any certification commitment, internal audit cycle, or new-system onboarding. Before stage 1 ISO 42001 certification audit Before annual internal audit cycle (Clause 9.2) When onboarding a new AI system into existing AIMS scope When AI risk register hasn't been refreshed in > 6 months After material model change (re-evaluate risks per Clause 6.1.2) When audit findings hint at AIMS / ISMS / QMS duplication Scope omission = certification finding. Including: embedded models, third-party AI services, "experimental" production systems Run aimsgapanalyzer.py to verify Clause 4.3 evidence "AI features added by SaaS vendors we use" = in scope if they affect the company's services Missing any of the four = critical nonconformity at stage 1. AI policy is NOT info-sec policy — it has separate substantive content Reference ISO 42001 Annex A.2.2 + Clause 5.2 Marketing-copy "AI ethics" doesn't pass Risk identification without control mapping = Clause 6.1.3 fails. Run airiskregisterbuilder.py per ISO 23894 methodology Every high/critical risk must link to ≥ 1 Annex A
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- alirezarezvani/claude-skills
- Source file
- compliance-os/skills/aims-audit/SKILL.md
- Fixed revision
- 8f082544116fc0d014188e521ca40304cdfc86b0
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: alirezarezvani/claude-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T14:01:46.290Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.