[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BKZ2ZW5BN6YXF6PYHTJKJ":3,"skill-same:01M75BKZ2ZW5BN6YXF6PYHTJKJ":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75BKZ2ZW5BN6YXF6PYHTJKJ","aims-audit",null,"\u002Fcs:aims-audit \u003Cscope> — ISO\u002FIEC 42001 AIMS internal-audit 6-question forcing interrogation. Use before certification stage 1, before annual internal audit cycles, or when onboarding a new AI system into an existing AIMS.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Faims-audit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"aims-audit\"\ndescription: \"\u002Fcs:aims-audit \u003Cscope> — ISO\u002FIEC 42001 AIMS internal-audit 6-question forcing interrogation. Use before certification stage 1, before annual internal audit cycles, or when onboarding a new AI system into an existing AIMS.\"\n---\n\n# \u002Fcs:aims-audit — AIMS ISO 42001 Forcing Questions\n\n**Command:** `\u002Fcs:aims-audit \u003Cscope>`\n\nThe ISO 42001 AIMS specialist pressure-tests any AI Management System work. Six questions before any certification commitment, internal audit cycle, or new-system onboarding.\n\n## When to Run\n\n- Before stage 1 ISO 42001 certification audit\n- Before annual internal audit cycle (Clause 9.2)\n- When onboarding a new AI system into existing AIMS scope\n- When AI risk register hasn't been refreshed in > 6 months\n- After material model change (re-evaluate risks per Clause 6.1.2)\n- When audit findings hint at AIMS \u002F ISMS \u002F QMS duplication\n\n## The Six AIMS Questions\n\n### 1. Does the AIMS scope statement name every AI system?\n**Scope omission = certification finding.**\n- Including: embedded models, third-party AI services, \"experimental\" production systems\n- Run `aims_gap_analyzer.py` to verify Clause 4.3 evidence\n- \"AI features added by SaaS vendors we use\" = in scope if they affect the company's services\n\n### 2. Does the AI policy commit to lawful use AND beneficial purpose AND human oversight AND continual improvement?\n**Missing any of the four = critical nonconformity at stage 1.**\n- AI policy is NOT info-sec policy — it has separate substantive content\n- Reference ISO 42001 Annex A.2.2 + Clause 5.2\n- Marketing-copy \"AI ethics\" doesn't pass\n\n### 3. What's the risk register coverage, and which Annex A controls treat each risk?\n**Risk identification without control mapping = Clause 6.1.3 fails.**\n- Run `ai_risk_register_builder.py` per ISO 23894 methodology\n- Every high\u002Fcritical risk must link to ≥ 1 Annex A control\n- \"Residual verdict: additional_treatment_required\" must be closed before stage 1\n\n### 4. Has the AI risk assessment been re-run since the last material model change?\n**Concept drift is not a one-time event.**\n- Article 9 EU AI Act + ISO 42001 Clause 6.1.2 both require iterative risk assessment\n- Material change = retraining on new data, fine-tuning, architecture change, deployment context change\n- If \"we did it 18 months ago and haven't touched it,\" the AIMS is broken\n\n### 5. What's the Clause 9.2 internal audit plan, and is auditor independence respected?\n**Without 9.2 plan, the AIMS is incomplete.**\n- Run `aims_audit_scheduler.py` with scope + auditors + prior findings\n- Audit every clause + applicable Annex A control over rolling 3-year cycle\n- Same auditor cannot audit own work\n- Cross-check with cs-quality-regulatory if integrated with 13485 audit programme\n\n### 6. Has the AIMS been integrated with existing ISMS \u002F QMS, or built in parallel?\n**Parallel systems = 5x ongoing maintenance cost.**\n- 60% of Clauses 4-10 evidence reuses ISO 27001 \u002F 13485 with AI scope appended\n- CAPA loop should be ONE loop with AI-tagged nonconformities, not separate\n- Reference `cross_framework_mapping_ai.md` for the reuse map\n- Cross-check with cs-ciso-advisor on ISO 27001 alignment\n\n## Workflow\n\n```bash\n# 1. AIMS gap analysis\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002Fscripts\u002Faims_gap_analyzer.py evidence.json\n\n# 2. AI risk register\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002Fscripts\u002Fai_risk_register_builder.py risks.json\n\n# 3. Internal audit plan\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002Fscripts\u002Faims_audit_scheduler.py audit_scope.json\n\n# 4. Cross-framework reuse map (via compliance-os)\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Fcross_framework_mapper.py program.json\n```\n\n## Output Format\n\n```markdown\n# AIMS Audit: \u003Cscope>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[gap-closure | risk-treatment | audit-scope | new-system-onboarding]\n\n## Gap Analysis (Clauses 4-10)\n- Weighted coverage: X%\n- Critical gaps: N\n- Major gaps: M\n- Certification readiness: ready | stage_2_candidate | not_ready\n\n## AI Risk Register\n- Total risks: N\n- By severity: critical=X, high=Y, medium=Z, low=W\n- Requires additional treatment: K\n- Top risk requiring action: \u003Cdescription>\n\n## Clause 9.2 Audit Plan\n- 12-month coverage: clauses=X, controls=Y\n- Auditor independence: clean | issues\n- Prior-year follow-up: scheduled in Q1\n\n## Cross-Framework Reuse\n- ISO 27001 evidence reused: % of AIMS Clauses 4-10\n- 13485 evidence reused: % (if applicable)\n- Net-new for AIMS: % (mostly Annex A)\n\n## Verdict\n🟢 STAGE-1-READY | 🟡 CLOSE-CRITICALS-FIRST | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + date]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:ai-act-readiness` — if EU AI Act also applies\n- `\u002Fcs:caio-review` — for executive AI strategy decisions\n- `\u002Fcs:ciso-review` — for ISO 27001 cross-framework alignment\n- `\u002Fcs:decide` — to log the verdict\n- `\u002Fcs:freeze 30` — on certification commitments\n\n## Related\n\n- Agent: [`cs-aims-iso42001`](..\u002F..\u002Fagents\u002Fcs-aims-iso42001.md)\n- Skill: [`iso42001-specialist`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002Fskills\u002Fcompliance-os\u002F`, `..\u002Fai-act-readiness\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:aims-audit — AIMS ISO 42001 Forcing Questions\n\n**Command:** `\u002Fcs:aims-audit \u003Cscope>`\n\nThe ISO 42001 AIMS specialist pressure-tests any AI Management System work. Six questions before any certification commitment, internal audit cycle, or new-system onboarding.\n\n## When to Run\n\n- Before stage 1 ISO 42001 certification audit\n- Before annual internal audit cycle (Clause 9.2)\n- When onboarding a new AI system into existing AIMS scope\n- When AI risk register hasn't been refreshed in > 6 months\n- After material model change (re-evaluate risks per Clause 6.1.2)\n- When audit findings hint at AIMS \u002F ISMS \u002F QMS duplication\n\n## The Six AIMS Questions\n\n### 1. Does the AIMS scope statement name every AI system?\n**Scope omission = certification finding.**\n- Including: embedded models, third-party AI services, \"experimental\" production systems\n- Run `aims_gap_analyzer.py` to verify Clause 4.3 evidence\n- \"AI features added by SaaS vendors we use\" = in scope if they affect the company's services\n\n### 2. Does the AI policy commit to lawful use AND beneficial purpose AND human oversight AND continual improvement?\n**Missing any of the four = critical nonconformity at stage 1.**\n- AI policy is NOT info-sec policy — it has separate substantive content\n- Reference ISO 42001 Annex A.2.2 + Clause 5.2\n- Marketing-copy \"AI ethics\" doesn't pass\n\n### 3. What's the risk register coverage, and which Annex A controls treat each risk?\n**Risk identification without control mapping = Clause 6.1.3 fails.**\n- Run `ai_risk_register_builder.py` per ISO 23894 methodology\n- Every high\u002Fcritical risk must link to ≥ 1 Annex A control\n- \"Residual verdict: additional_treatment_required\" must be closed before stage 1\n\n### 4. Has the AI risk assessment been re-run since the last material model change?\n**Concept drift is not a one-time event.**\n- Article 9 EU AI Act + ISO 42001 Clause 6.1.2 both require iterative risk assessment\n- Material change = retraining on new data, fine-tuning, architecture change, deployment context change\n- If \"we did it 18 months ago and haven't touched it,\" the AIMS is broken\n\n### 5. What's the Clause 9.2 internal audit plan, and is auditor independence respected?\n**Without 9.2 plan, the AIMS is incomplete.**\n- Run `aims_audit_scheduler.py` with scope + auditors + prior findings\n- Audit every clause + applicable Annex A control over rolling 3-year cycle\n- Same auditor cannot audit own work\n- Cross-check with cs-quality-regulatory if integrated with 13485 audit programme\n\n### 6. Has the AIMS been integrated with existing ISMS \u002F QMS, or built in parallel?\n**Parallel systems = 5x ongoing maintenance cost.**\n- 60% of Clauses 4-10 evidence reuses ISO 27001 \u002F 13485 with AI scope appended\n- CAPA loop should be ONE loop with AI-tagged nonconformities, not separate\n- Reference `cross_framework_mapping_ai.md` for the reuse map\n- Cross-check with cs-ciso-advisor on ISO 27001 alignment\n\n## Workflow\n\n```bash\n# 1. AIMS gap analysis\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002Fscripts\u002Faims_gap_analyzer.py evidence.json\n\n# 2. AI risk register\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002Fscripts\u002Fai_risk_register_builder.py risks.json\n\n# 3. Internal audit plan\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002Fscripts\u002Faims_audit_scheduler.py audit_scope.json\n\n# 4. Cross-framework reuse map (via compliance-os)\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Fcross_framework_mapper.py program.json\n```\n\n## Output Format\n\n```markdown\n# AIMS Audit: \u003Cscope>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[gap-closure | risk-treatment | audit-scope | new-system-onboarding]\n\n## Gap Analysis (Clauses 4-10)\n- Weighted coverage: X%\n- Critical gaps: N\n- Major gaps: M\n- Certification readiness: ready | stage_2_candidate | not_ready\n\n## AI Risk Register\n- Total risks: N\n- By severity: critical=X, high=Y, medium=Z, low=W\n- Requires additional treatment: K\n- Top risk requiring action: \u003Cdescription>\n\n## Clause 9.2 Audit Plan\n- 12-month coverage: clauses=X, controls=Y\n- Auditor independence: clean | issues\n- Prior-year follow-up: scheduled in Q1\n\n## Cross-Framework Reuse\n- ISO 27001 evidence reused: % of AIMS Clauses 4-10\n- 13485 evidence reused: % (if applicable)\n- Net-new for AIMS: % (mostly Annex A)\n\n## Verdict\n🟢 STAGE-1-READY | 🟡 CLOSE-CRITICALS-FIRST | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + date]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:ai-act-readiness` — if EU AI Act also applies\n- `\u002Fcs:caio-review` — for executive AI strategy decisions\n- `\u002Fcs:ciso-review` — for ISO 27001 cross-framework alignment\n- `\u002Fcs:decide` — to log the verdict\n- `\u002Fcs:freeze 30` — on certification commitments\n\n## Related\n\n- Agent: [`cs-aims-iso42001`](..\u002F..\u002Fagents\u002Fcs-aims-iso42001.md)\n- Skill: [`iso42001-specialist`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002Fskills\u002Fcompliance-os\u002F`, `..\u002Fai-act-readiness\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Faims-audit",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill aims-audit",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill aims-audit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill aims-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Faims-audit\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]