[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75DMGETQ1GZDHV7H4K1KWH5":3,"skill-same:01M75DMGETQ1GZDHV7H4K1KWH5":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},"01M75DMGETQ1GZDHV7H4K1KWH5","fda-qsr-audit-prep",null,"\u002Fcs:fda-qsr-audit-prep \u003Cscope> — FDA 21 CFR 820 (QSR \u002F QMSR) audit 6-question forcing interrogation. Post-Feb 2026 substantially harmonized with ISO 13485. Use before annual internal QSR audit, pre-FDA-inspection readiness, or Form 483 response.","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\u002Ffda-qsr-audit-prep\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"fda-qsr-audit-prep\"\ndescription: \"\u002Fcs:fda-qsr-audit-prep \u003Cscope> — FDA 21 CFR 820 (QSR \u002F QMSR) audit 6-question forcing interrogation. Post-Feb 2026 substantially harmonized with ISO 13485. Use before annual internal QSR audit, pre-FDA-inspection readiness, or Form 483 response.\"\n---\n\n# \u002Fcs:fda-qsr-audit-prep — FDA QSR Forcing Questions\n\n**Command:** `\u002Fcs:fda-qsr-audit-prep \u003Cscope>`\n\nThe FDA QSR auditor pressure-tests any US medical-device QSR work. Six questions before any internal audit, FDA inspection, Form 483 response, or recall decision.\n\n## When to Run\n\n- Before annual internal QSR audit\n- Before pre-FDA-inspection readiness review (any device commercially distributed in US)\n- After receiving Form 483 observations\n- After Warning Letter receipt\n- After MDR-reportable event\n- Before recall decision (voluntary vs FDA-initiated)\n- Before submitting 510(k) \u002F PMA (where QSR posture affects approval timeline)\n\n## The Six QSR Questions\n\n### 1. Show me the complaint files from the last quarter — and the corresponding MDR reports.\n**21 CFR 820.198 + 21 CFR 803 — most-cited FDA inspection area.**\n- Complaint log complete: who \u002F what \u002F when \u002F device \u002F batch\n- Investigation closure within reasonable timeline\n- MDR-reporting decision tree applied: death OR serious injury OR malfunction-that-could-cause = MDR\n- 30-day timeline for most MDR reports; 5 days for certain serious events\n- Complaint trending input to management review\n\n### 2. When was process validation (IQ\u002FOQ\u002FPQ) last revalidated per 21 CFR 820.75?\n**Cross-walks ISO 13485 Clause 7.5.6 (substantially harmonized post-Feb 2026).**\n- Initial validation at process introduction\n- Revalidation triggers: process \u002F equipment \u002F material change OR periodic schedule\n- Statistical techniques per 21 CFR 820.250 where applicable\n- Cross-check with cs-cqm-iso13485 for ISO 13485 alignment\n\n### 3. Show me the DHRs for products commercially distributed in last 2 years.\n**21 CFR 820.180 — 2-year retention from commercial distribution; check sampling for completeness.**\n- Device History Record (DHR) for each unit\u002Flot\u002Fbatch\n- Must include: dates of manufacture, quantity manufactured, quantity released, acceptance records, primary identification label, device identification, control number\n- Sample stratified by product class\n- Verify DHR closeness to DHF (design history file)\n\n### 4. Show me CAPAs from the last 6 months with effectiveness verification.\n**21 CFR 820.100 = ISO 13485 8.5.2 substantially harmonized.**\n- Root cause analysis depth (5 Why minimum)\n- Effectiveness verification = measurable evidence, not \"we updated the procedure\"\n- Containment \u002F correction \u002F corrective action distinction documented\n- Closure approval by appropriate authority\n- Aging CAPAs > 90 days flagged\n\n### 5. Show me labeling (21 CFR 801) review for the most recent product launch.\n**FDA-specific overlay not in ISO 13485.**\n- Labeling per 21 CFR 801 requirements\n- For specific device types: also 21 CFR 800 series sectoral overlays\n- UDI (Unique Device Identification) per 21 CFR 830\n- Promotional materials reviewed for accuracy + non-misleading\n\n### 6. If a Form 483 was issued in the last 3 years, show me the closure status.\n**Form 483 = FDA observation; not equivalent to ISO nonconformity.**\n- Response within 15 working days\n- Each observation has documented corrective + preventive action with timeline\n- Effectiveness verification evidence\n- For Warning Letters: separate response track + potentially FDA meeting\n\n## Workflow\n\n```bash\n# 1. QSR compliance posture\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fqsr_compliance_checker.py compliance_state.json\n\n# 2. FDA submission tracking (510(k) \u002F PMA \u002F IDE)\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Ffda_submission_tracker.py submissions.json\n\n# 3. HIPAA overlap (if connected device handles PHI)\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fhipaa_risk_assessment.py phi_inventory.json\n\n# 4. Mock FDA inspection\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Faudit_simulator.py fda_qsr_scope.json\n```\n\n## Output Format\n\n```markdown\n# FDA QSR Audit Prep: \u003Cscope>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[programme-plan | inspection-readiness | 483-response | MDR-decision | recall]\n\n## Complaint + MDR Posture\n- Complaints last quarter: N\n- MDR-reportable events: M\n- MDR reports filed within timeline: % (target 100%)\n- Complaint trending review at management level: yes\u002Fno\n\n## Process Validation Status (21 CFR 820.75)\n- Validations on schedule: %\n- Stale validations: \u003Clist>\n- Statistical techniques applied: yes\u002Fno per process\n\n## DHR Completeness (21 CFR 820.180)\n- DHRs sampled: N\n- Completeness rate: %\n- 2-year retention compliant: yes\u002Fno\n- Stratified by product class: yes\u002Fno\n\n## CAPA Health (21 CFR 820.100)\n- CAPAs sampled: N\n- Root cause analysis depth: adequate\u002Finadequate\n- Effectiveness verification: complete\u002Fincomplete\n- Aging CAPAs > 90 days: N\n\n## Labeling (21 CFR 801)\n- Recent products reviewed: \u003Clist>\n- Labeling accurate + non-misleading: yes\u002Fno\n- UDI compliance per 21 CFR 830: yes\u002Fno\n\n## Form 483 \u002F Warning Letter History\n- Form 483s last 3 years: N (each: closed\u002Fin-progress)\n- Warning Letters last 5 years: N (each: closed\u002Fin-progress)\n- Pattern across observations: \u003Cthematic>\n\n## ISO 13485 Cross-Walk (post-Feb 2026 harmonization)\n- ISO 13485 audit findings: \u003Clink to cs-cqm-iso13485 output>\n- FDA-specific overlays remaining: labeling + complaint handling + MDR reporting + recall procedures\n- Cross-framework reuse: % of evidence shared\n\n## Verdict\n🟢 INSPECTION-READY | 🟡 GAPS-IDENTIFIED | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + FDA-cited timeline (15 days \u002F 30 days \u002F etc.)]\n\n## Outside Counsel Required\n[For Warning Letter response, recall decisions, or 510(k) \u002F PMA strategy disputes]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:iso13485-audit-prep` — for ISO 13485 cross-walk pair (substantially harmonized)\n- `\u002Fcs:gdpr-audit-prep` — if connected device handles personal data\n- `\u002Fcs:gc-review` — for Warning Letter response coordination\n\n## Related\n\n- Agent: [`cs-fda-qsr-auditor`](..\u002F..\u002Fagents\u002Fcs-fda-qsr-auditor.md)\n- Skill: [`fda-consultant-specialist`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002FSKILL.md)\n- Adjacent: `..\u002Fiso13485-audit-prep\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:fda-qsr-audit-prep — FDA QSR Forcing Questions\n\n**Command:** `\u002Fcs:fda-qsr-audit-prep \u003Cscope>`\n\nThe FDA QSR auditor pressure-tests any US medical-device QSR work. Six questions before any internal audit, FDA inspection, Form 483 response, or recall decision.\n\n## When to Run\n\n- Before annual internal QSR audit\n- Before pre-FDA-inspection readiness review (any device commercially distributed in US)\n- After receiving Form 483 observations\n- After Warning Letter receipt\n- After MDR-reportable event\n- Before recall decision (voluntary vs FDA-initiated)\n- Before submitting 510(k) \u002F PMA (where QSR posture affects approval timeline)\n\n## The Six QSR Questions\n\n### 1. Show me the complaint files from the last quarter — and the corresponding MDR reports.\n**21 CFR 820.198 + 21 CFR 803 — most-cited FDA inspection area.**\n- Complaint log complete: who \u002F what \u002F when \u002F device \u002F batch\n- Investigation closure within reasonable timeline\n- MDR-reporting decision tree applied: death OR serious injury OR malfunction-that-could-cause = MDR\n- 30-day timeline for most MDR reports; 5 days for certain serious events\n- Complaint trending input to management review\n\n### 2. When was process validation (IQ\u002FOQ\u002FPQ) last revalidated per 21 CFR 820.75?\n**Cross-walks ISO 13485 Clause 7.5.6 (substantially harmonized post-Feb 2026).**\n- Initial validation at process introduction\n- Revalidation triggers: process \u002F equipment \u002F material change OR periodic schedule\n- Statistical techniques per 21 CFR 820.250 where applicable\n- Cross-check with cs-cqm-iso13485 for ISO 13485 alignment\n\n### 3. Show me the DHRs for products commercially distributed in last 2 years.\n**21 CFR 820.180 — 2-year retention from commercial distribution; check sampling for completeness.**\n- Device History Record (DHR) for each unit\u002Flot\u002Fbatch\n- Must include: dates of manufacture, quantity manufactured, quantity released, acceptance records, primary identification label, device identification, control number\n- Sample stratified by product class\n- Verify DHR closeness to DHF (design history file)\n\n### 4. Show me CAPAs from the last 6 months with effectiveness verification.\n**21 CFR 820.100 = ISO 13485 8.5.2 substantially harmonized.**\n- Root cause analysis depth (5 Why minimum)\n- Effectiveness verification = measurable evidence, not \"we updated the procedure\"\n- Containment \u002F correction \u002F corrective action distinction documented\n- Closure approval by appropriate authority\n- Aging CAPAs > 90 days flagged\n\n### 5. Show me labeling (21 CFR 801) review for the most recent product launch.\n**FDA-specific overlay not in ISO 13485.**\n- Labeling per 21 CFR 801 requirements\n- For specific device types: also 21 CFR 800 series sectoral overlays\n- UDI (Unique Device Identification) per 21 CFR 830\n- Promotional materials reviewed for accuracy + non-misleading\n\n### 6. If a Form 483 was issued in the last 3 years, show me the closure status.\n**Form 483 = FDA observation; not equivalent to ISO nonconformity.**\n- Response within 15 working days\n- Each observation has documented corrective + preventive action with timeline\n- Effectiveness verification evidence\n- For Warning Letters: separate response track + potentially FDA meeting\n\n## Workflow\n\n```bash\n# 1. QSR compliance posture\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fqsr_compliance_checker.py compliance_state.json\n\n# 2. FDA submission tracking (510(k) \u002F PMA \u002F IDE)\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Ffda_submission_tracker.py submissions.json\n\n# 3. HIPAA overlap (if connected device handles PHI)\npython ..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fhipaa_risk_assessment.py phi_inventory.json\n\n# 4. Mock FDA inspection\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Faudit_simulator.py fda_qsr_scope.json\n```\n\n## Output Format\n\n```markdown\n# FDA QSR Audit Prep: \u003Cscope>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[programme-plan | inspection-readiness | 483-response | MDR-decision | recall]\n\n## Complaint + MDR Posture\n- Complaints last quarter: N\n- MDR-reportable events: M\n- MDR reports filed within timeline: % (target 100%)\n- Complaint trending review at management level: yes\u002Fno\n\n## Process Validation Status (21 CFR 820.75)\n- Validations on schedule: %\n- Stale validations: \u003Clist>\n- Statistical techniques applied: yes\u002Fno per process\n\n## DHR Completeness (21 CFR 820.180)\n- DHRs sampled: N\n- Completeness rate: %\n- 2-year retention compliant: yes\u002Fno\n- Stratified by product class: yes\u002Fno\n\n## CAPA Health (21 CFR 820.100)\n- CAPAs sampled: N\n- Root cause analysis depth: adequate\u002Finadequate\n- Effectiveness verification: complete\u002Fincomplete\n- Aging CAPAs > 90 days: N\n\n## Labeling (21 CFR 801)\n- Recent products reviewed: \u003Clist>\n- Labeling accurate + non-misleading: yes\u002Fno\n- UDI compliance per 21 CFR 830: yes\u002Fno\n\n## Form 483 \u002F Warning Letter History\n- Form 483s last 3 years: N (each: closed\u002Fin-progress)\n- Warning Letters last 5 years: N (each: closed\u002Fin-progress)\n- Pattern across observations: \u003Cthematic>\n\n## ISO 13485 Cross-Walk (post-Feb 2026 harmonization)\n- ISO 13485 audit findings: \u003Clink to cs-cqm-iso13485 output>\n- FDA-specific overlays remaining: labeling + complaint handling + MDR reporting + recall procedures\n- Cross-framework reuse: % of evidence shared\n\n## Verdict\n🟢 INSPECTION-READY | 🟡 GAPS-IDENTIFIED | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + FDA-cited timeline (15 days \u002F 30 days \u002F etc.)]\n\n## Outside Counsel Required\n[For Warning Letter response, recall decisions, or 510(k) \u002F PMA strategy disputes]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:iso13485-audit-prep` — for ISO 13485 cross-walk pair (substantially harmonized)\n- `\u002Fcs:gdpr-audit-prep` — if connected device handles personal data\n- `\u002Fcs:gc-review` — for Warning Letter response coordination\n\n## Related\n\n- Agent: [`cs-fda-qsr-auditor`](..\u002F..\u002Fagents\u002Fcs-fda-qsr-auditor.md)\n- Skill: [`fda-consultant-specialist`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002FSKILL.md)\n- Adjacent: `..\u002Fiso13485-audit-prep\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Ffda-qsr-audit-prep",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 fda-qsr-audit-prep",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill fda-qsr-audit-prep",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill fda-qsr-audit-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Ffda-qsr-audit-prep\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",[],[]]