[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7792R9SW35P1FHRXQDC1HVP":3,"skill-same:01M7792R9SW35P1FHRXQDC1HVP":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7792R9SW35P1FHRXQDC1HVP","fda-consultant-specialist",null,"FDA regulatory consultant for medical device companies. Provides 510(k)\u002FPMA\u002FDe Novo pathway guidance, QSR (21 CFR 820) compliance, HIPAA assessments, and device cybersecurity. Use when user mentions FDA submission, 510(k), PMA, De Novo, QSR, premarket, predicate device, substantial equivalence, HIPAA medical device, or FDA cybersecurity.","kruxshnx\u002Fclaude-skills-devin","kruxshnx","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F127938788?v=4","01M757YM3F96N4K1BSE7Z0NQK7","ARJANGI GOVINDA KRISHNA","01M757YM43H5T7MP2B3DC13GZ2",2,"MIT","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"fda-consultant-specialist\"\ndescription: FDA regulatory consultant for medical device companies. Provides 510(k)\u002FPMA\u002FDe Novo pathway guidance, QSR (21 CFR 820) compliance, HIPAA assessments, and device cybersecurity. Use when user mentions FDA submission, 510(k), PMA, De Novo, QSR, premarket, predicate device, substantial equivalence, HIPAA medical device, or FDA cybersecurity.\n---\n\n# FDA Consultant Specialist\n\nFDA regulatory consulting for medical device manufacturers covering submission pathways, Quality System Regulation (QSR), HIPAA compliance, and device cybersecurity requirements.\n\n## Table of Contents\n\n- [FDA Pathway Selection](#fda-pathway-selection)\n- [510(k) Submission Process](#510k-submission-process)\n- [QSR Compliance](#qsr-compliance)\n- [HIPAA for Medical Devices](#hipaa-for-medical-devices)\n- [Device Cybersecurity](#device-cybersecurity)\n- [Resources](#resources)\n\n---\n\n## FDA Pathway Selection\n\nDetermine the appropriate FDA regulatory pathway based on device classification and predicate availability.\n\n### Decision Framework\n\n```\nPredicate device exists?\n├── YES → Substantially equivalent?\n│   ├── YES → 510(k) Pathway\n│   │   ├── No design changes → Abbreviated 510(k)\n│   │   ├── Manufacturing only → Special 510(k)\n│   │   └── Design\u002Fperformance → Traditional 510(k)\n│   └── NO → PMA or De Novo\n└── NO → Novel device?\n    ├── Low-to-moderate risk → De Novo\n    └── High risk (Class III) → PMA\n```\n\n### Pathway Comparison\n\n| Pathway | When to Use | Timeline | Cost |\n|---------|-------------|----------|------|\n| 510(k) Traditional | Predicate exists, design changes | 90 days | $21,760 |\n| 510(k) Special | Manufacturing changes only | 30 days | $21,760 |\n| 510(k) Abbreviated | Guidance\u002Fstandard conformance | 30 days | $21,760 |\n| De Novo | Novel, low-moderate risk | 150 days | $134,676 |\n| PMA | Class III, no predicate | 180+ days | $425,000+ |\n\n### Pre-Submission Strategy\n\n1. Identify product code and classification\n2. Search 510(k) database for predicates\n3. Assess substantial equivalence feasibility\n4. Prepare Q-Sub questions for FDA\n5. Schedule Pre-Sub meeting if needed\n\n**Reference:** See [fda_submission_guide.md](references\u002Ffda_submission_guide.md) for pathway decision matrices and submission requirements.\n\n---\n\n## 510(k) Submission Process\n\n### Workflow\n\n```\nPhase 1: Planning\n├── Step 1: Identify predicate device(s)\n├── Step 2: Compare intended use and technology\n├── Step 3: Determine testing requirements\n└── Checkpoint: SE argument feasible?\n\nPhase 2: Preparation\n├── Step 4: Complete performance testing\n├── Step 5: Prepare device description\n├── Step 6: Document SE comparison\n├── Step 7: Finalize labeling\n└── Checkpoint: All required sections complete?\n\nPhase 3: Submission\n├── Step 8: Assemble submission package\n├── Step 9: Submit via eSTAR\n├── Step 10: Track acknowledgment\n└── Checkpoint: Submission accepted?\n\nPhase 4: Review\n├── Step 11: Monitor review status\n├── Step 12: Respond to AI requests\n├── Step 13: Receive decision\n└── Verification: SE letter received?\n```\n\n### Required Sections (21 CFR 807.87)\n\n| Section | Content |\n|---------|---------|\n| Cover Letter | Submission type, device ID, contact info |\n| Form 3514 | CDRH premarket review cover sheet |\n| Device Description | Physical description, principles of operation |\n| Indications for Use | Form 3881, patient population, use environment |\n| SE Comparison | Side-by-side comparison with predicate |\n| Performance Testing | Bench, biocompatibility, electrical safety |\n| Software Documentation | Level of concern, hazard analysis (IEC 62304) |\n| Labeling | IFU, package labels, warnings |\n| 510(k) Summary | Public summary of submission |\n\n### Common RTA Issues\n\n| Issue | Prevention |\n|-------|------------|\n| Missing user fee | Verify payment before submission |\n| Incomplete Form 3514 | Review all fields, ensure signature |\n| No predicate identified | Confirm K-number in FDA database |\n| Inadequate SE comparison | Address all technological characteristics |\n\n---\n\n## QSR Compliance\n\nQuality System Regulation (21 CFR Part 820) requirements for medical device manufacturers.\n\n### Key Subsystems\n\n| Section | Title | Focus |\n|---------|-------|-------|\n| 820.20 | Management Responsibility | Quality policy, org structure, management review |\n| 820.30 | Design Controls | Input, output, review, verification, validation |\n| 820.40 | Document Controls | Approval, distribution, change control |\n| 820.50 | Purchasing Controls | Supplier qualification, purchasing data |\n| 820.70 | Production Controls | Process validation, environmental controls |\n| 820.100 | CAPA | Root cause analysis, corrective actions |\n| 820.181 | Device Master Record | Specifications, procedures, acceptance criteria |\n\n### Design Controls Workflow (820.30)\n\n```\nStep 1: Design Input\n└── Capture user needs, intended use, regulatory requirements\n    Verification: Inputs reviewed and approved?\n\nStep 2: Design Output\n└── Create specifications, drawings, software architecture\n    Verification: Outputs traceable to inputs?\n\nStep 3: Design Review\n└── Conduct reviews at each phase milestone\n    Verification: Review records with signatures?\n\nStep 4: Design Verification\n└── Perform testing against specifications\n    Verification: All tests pass acceptance criteria?\n\nStep 5: Design Validation\n└── Confirm device meets user needs in actual use conditions\n    Verification: Validation report approved?\n\nStep 6: Design Transfer\n└── Release to production with DMR complete\n    Verification: Transfer checklist complete?\n```\n\n### CAPA Process (820.100)\n\n1. **Identify**: Document nonconformity or potential problem\n2. **Investigate**: Perform root cause analysis (5 Whys, Fishbone)\n3. **Plan**: Define corrective\u002Fpreventive actions\n4. **Implement**: Execute actions, update documentation\n5. **Verify**: Confirm implementation complete\n6. **Effectiveness**: Monitor for recurrence (30-90 days)\n7. **Close**: Management approval and closure\n\n**Reference:** See [qsr_compliance_requirements.md](references\u002Fqsr_compliance_requirements.md) for detailed QSR implementation guidance.\n\n---\n\n## HIPAA for Medical Devices\n\nHIPAA requirements for devices that create, store, transmit, or access Protected Health Information (PHI).\n\n### Applicability\n\n| Device Type | HIPAA Applies |\n|-------------|---------------|\n| Standalone diagnostic (no data transmission) | No |\n| Connected device transmitting patient data | Yes |\n| Device with EHR integration | Yes |\n| SaMD storing patient information | Yes |\n| Wellness app (no diagnosis) | Only if stores PHI |\n\n### Required Safeguards\n\n```\nAdministrative (§164.308)\n├── Security officer designation\n├── Risk analysis and management\n├── Workforce training\n├── Incident response procedures\n└── Business associate agreements\n\nPhysical (§164.310)\n├── Facility access controls\n├── Workstation security\n└── Device disposal procedures\n\nTechnical (§164.312)\n├── Access control (unique IDs, auto-logoff)\n├── Audit controls (logging)\n├── Integrity controls (checksums, hashes)\n├── Authentication (MFA recommended)\n└── Transmission security (TLS 1.2+)\n```\n\n### Risk Assessment Steps\n\n1. Inventory all systems handling ePHI\n2. Document data flows (collection, storage, transmission)\n3. Identify threats and vulnerabilities\n4. Assess likelihood and impact\n5. Determine risk levels\n6. Implement controls\n7. Document residual risk\n\n**Reference:** See [hipaa_compliance_framework.md](references\u002Fhipaa_compliance_framework.md) for implementation checklists and BAA templates.\n\n---\n\n## Device Cybersecurity\n\nFDA cybersecurity requirements for connected medical devices.\n\n### Premarket Requirements\n\n| Element | Description |\n|---------|-------------|\n| Threat Model | STRIDE analysis, attack trees, trust boundaries |\n| Security Controls | Authentication, encryption, access control |\n| SBOM | Software Bill of Materials (CycloneDX or SPDX) |\n| Security Testing | Penetration testing, vulnerability scanning |\n| Vulnerability Plan | Disclosure process, patch management |\n\n### Device Tier Classification\n\n**Tier 1 (Higher Risk):**\n- Connects to network\u002Finternet\n- Cybersecurity incident could cause patient harm\n\n**Tier 2 (Standard Risk):**\n- All other connected devices\n\n### Postmarket Obligations\n\n1. Monitor NVD and ICS-CERT for vulnerabilities\n2. Assess applicability to device components\n3. Develop and test patches\n4. Communicate with customers\n5. Report to FDA per guidance\n\n### Coordinated Vulnerability Disclosure\n\n```\nResearcher Report\n    ↓\nAcknowledgment (48 hours)\n    ↓\nInitial Assessment (5 days)\n    ↓\nFix Development\n    ↓\nCoordinated Public Disclosure\n```\n\n**Reference:** See [device_cybersecurity_guidance.md](references\u002Fdevice_cybersecurity_guidance.md) for SBOM format examples and threat modeling templates.\n\n---\n\n## Resources\n\n### scripts\u002F\n\n| Script | Purpose |\n|--------|---------|\n| `fda_submission_tracker.py` | Track 510(k)\u002FPMA\u002FDe Novo submission milestones and timelines |\n| `qsr_compliance_checker.py` | Assess 21 CFR 820 compliance against project documentation |\n| `hipaa_risk_assessment.py` | Evaluate HIPAA safeguards in medical device software |\n\n### references\u002F\n\n| File | Content |\n|------|---------|\n| `fda_submission_guide.md` | 510(k), De Novo, PMA submission requirements and checklists |\n| `qsr_compliance_requirements.md` | 21 CFR 820 implementation guide with templates |\n| `hipaa_compliance_framework.md` | HIPAA Security Rule safeguards and BAA requirements |\n| `device_cybersecurity_guidance.md` | FDA cybersecurity requirements, SBOM, threat modeling |\n| `fda_capa_requirements.md` | CAPA process, root cause analysis, effectiveness verification |\n\n### Usage Examples\n\n```bash\n# Track FDA submission status\npython scripts\u002Ffda_submission_tracker.py \u002Fpath\u002Fto\u002Fproject --type 510k\n\n# Assess QSR compliance\npython scripts\u002Fqsr_compliance_checker.py \u002Fpath\u002Fto\u002Fproject --section 820.30\n\n# Run HIPAA risk assessment\npython scripts\u002Fhipaa_risk_assessment.py \u002Fpath\u002Fto\u002Fproject --category technical\n```\n","# FDA Consultant Specialist\n\nFDA regulatory consulting for medical device manufacturers covering submission pathways, Quality System Regulation (QSR), HIPAA compliance, and device cybersecurity requirements.\n\n## Table of Contents\n\n- [FDA Pathway Selection](#fda-pathway-selection)\n- [510(k) Submission Process](#510k-submission-process)\n- [QSR Compliance](#qsr-compliance)\n- [HIPAA for Medical Devices](#hipaa-for-medical-devices)\n- [Device Cybersecurity](#device-cybersecurity)\n- [Resources](#resources)\n\n---\n\n## FDA Pathway Selection\n\nDetermine the appropriate FDA regulatory pathway based on device classification and predicate availability.\n\n### Decision Framework\n\n```\nPredicate device exists?\n├── YES → Substantially equivalent?\n│   ├── YES → 510(k) Pathway\n│   │   ├── No design changes → Abbreviated 510(k)\n│   │   ├── Manufacturing only → Special 510(k)\n│   │   └── Design\u002Fperformance → Traditional 510(k)\n│   └── NO → PMA or De Novo\n└── NO → Novel device?\n    ├── Low-to-moderate risk → De Novo\n    └── High risk (Class III) → PMA\n```\n\n### Pathway Comparison\n\n| Pathway | When to Use | Timeline | Cost |\n|---------|-------------|----------|------|\n| 510(k) Traditional | Predicate exists, design changes | 90 days | $21,760 |\n| 510(k) Special | Manufacturing changes only | 30 days | $21,760 |\n| 510(k) Abbreviated | Guidance\u002Fstandard conformance | 30 days | $21,760 |\n| De Novo | Novel, low-moderate risk | 150 days | $134,676 |\n| PMA | Class III, no predicate | 180+ days | $425,000+ |\n\n### Pre-Submission Strategy\n\n1. Identify product code and classification\n2. Search 510(k) database for predicates\n3. Assess substantial equivalence feasibility\n4. Prepare Q-Sub questions for FDA\n5. Schedule Pre-Sub meeting if needed\n\n**Reference:** See [fda_submission_guide.md](references\u002Ffda_submission_guide.md) for pathway decision matrices and submission requirements.\n\n---\n\n## 510(k) Submission Process\n\n### Workflow\n\n```\nPhase 1: Planning\n├── Step 1: Identify predicate device(s)\n├── Step 2: Compare intended use and technology\n├── Step 3: Determine testing requirements\n└── Checkpoint: SE argument feasible?\n\nPhase 2: Preparation\n├── Step 4: Complete performance testing\n├── Step 5: Prepare device description\n├── Step 6: Document SE comparison\n├── Step 7: Finalize labeling\n└── Checkpoint: All required sections complete?\n\nPhase 3: Submission\n├── Step 8: Assemble submission package\n├── Step 9: Submit via eSTAR\n├── Step 10: Track acknowledgment\n└── Checkpoint: Submission accepted?\n\nPhase 4: Review\n├── Step 11: Monitor review status\n├── Step 12: Respond to AI requests\n├── Step 13: Receive decision\n└── Verification: SE letter received?\n```\n\n### Required Sections (21 CFR 807.87)\n\n| Section | Content |\n|---------|---------|\n| Cover Letter | Submission type, device ID, contact info |\n| Form 3514 | CDRH premarket review cover sheet |\n| Device Description | Physical description, principles of operation |\n| Indications for Use | Form 3881, patient population, use environment |\n| SE Comparison | Side-by-side comparison with predicate |\n| Performance Testing | Bench, biocompatibility, electrical safety |\n| Software Documentation | Level of concern, hazard analysis (IEC 62304) |\n| Labeling | IFU, package labels, warnings |\n| 510(k) Summary | Public summary of submission |\n\n### Common RTA Issues\n\n| Issue | Prevention |\n|-------|------------|\n| Missing user fee | Verify payment before submission |\n| Incomplete Form 3514 | Review all fields, ensure signature |\n| No predicate identified | Confirm K-number in FDA database |\n| Inadequate SE comparison | Address all technological characteristics |\n\n---\n\n## QSR Compliance\n\nQuality System Regulation (21 CFR Part 820) requirements for medical device manufacturers.\n\n### Key Subsystems\n\n| Section | Title | Focus |\n|---------|-------|-------|\n| 820.20 | Management Responsibility | Quality policy, org structure, management review |\n| 820.30 | Design Controls | Input, output, review, verification, validation |\n| 820.40 | Document Controls | Approval, distribution, change control |\n| 820.50 | Purchasing Controls | Supplier qualification, purchasing data |\n| 820.70 | Production Controls | Process validation, environmental controls |\n| 820.100 | CAPA | Root cause analysis, corrective actions |\n| 820.181 | Device Master Record | Specifications, procedures, acceptance criteria |\n\n### Design Controls Workflow (820.30)\n\n```\nStep 1: Design Input\n└── Capture user needs, intended use, regulatory requirements\n    Verification: Inputs reviewed and approved?\n\nStep 2: Design Output\n└── Create specifications, drawings, software architecture\n    Verification: Outputs traceable to inputs?\n\nStep 3: Design Review\n└── Conduct reviews at each phase milestone\n    Verification: Review records with signatures?\n\nStep 4: Design Verification\n└── Perform testing against specifications\n    Verification: All tests pass acceptance criteria?\n\nStep 5: Design Validation\n└── Confirm device meets user needs in actual use conditions\n    Verification: Validation report approved?\n\nStep 6: Design Transfer\n└── Release to production with DMR complete\n    Verification: Transfer checklist complete?\n```\n\n### CAPA Process (820.100)\n\n1. **Identify**: Document nonconformity or potential problem\n2. **Investigate**: Perform root cause analysis (5 Whys, Fishbone)\n3. **Plan**: Define corrective\u002Fpreventive actions\n4. **Implement**: Execute actions, update documentation\n5. **Verify**: Confirm implementation complete\n6. **Effectiveness**: Monitor for recurrence (30-90 days)\n7. **Close**: Management approval and closure\n\n**Reference:** See [qsr_compliance_requirements.md](references\u002Fqsr_compliance_requirements.md) for detailed QSR implementation guidance.\n\n---\n\n## HIPAA for Medical Devices\n\nHIPAA requirements for devices that create, store, transmit, or access Protected Health Information (PHI).\n\n### Applicability\n\n| Device Type | HIPAA Applies |\n|-------------|---------------|\n| Standalone diagnostic (no data transmission) | No |\n| Connected device transmitting patient data | Yes |\n| Device with EHR integration | Yes |\n| SaMD storing patient information | Yes |\n| Wellness app (no diagnosis) | Only if stores PHI |\n\n### Required Safeguards\n\n```\nAdministrative (§164.308)\n├── Security officer designation\n├── Risk analysis and management\n├── Workforce training\n├── Incident response procedures\n└── Business associate agreements\n\nPhysical (§164.310)\n├── Facility access controls\n├── Workstation security\n└── Device disposal procedures\n\nTechnical (§164.312)\n├── Access control (unique IDs, auto-logoff)\n├── Audit controls (logging)\n├── Integrity controls (checksums, hashes)\n├── Authentication (MFA recommended)\n└── Transmission security (TLS 1.2+)\n```\n\n### Risk Assessment Steps\n\n1. Inventory all systems handling ePHI\n2. Document data flows (collection, storage, transmission)\n3. Identify threats and vulnerabilities\n4. Assess likelihood and impact\n5. Determine risk levels\n6. Implement controls\n7. Document residual risk\n\n**Reference:** See [hipaa_compliance_framework.md](references\u002Fhipaa_compliance_framework.md) for implementation checklists and BAA templates.\n\n---\n\n## Device Cybersecurity\n\nFDA cybersecurity requirements for connected medical devices.\n\n### Premarket Requirements\n\n| Element | Description |\n|---------|-------------|\n| Threat Model | STRIDE analysis, attack trees, trust boundaries |\n| Security Controls | Authentication, encryption, access control |\n| SBOM | Software Bill of Materials (CycloneDX or SPDX) |\n| Security Testing | Penetration testing, vulnerability scanning |\n| Vulnerability Plan | Disclosure process, patch management |\n\n### Device Tier Classification\n\n**Tier 1 (Higher Risk):**\n- Connects to network\u002Finternet\n- Cybersecurity incident could cause patient harm\n\n**Tier 2 (Standard Risk):**\n- All other connected devices\n\n### Postmarket Obligations\n\n1. Monitor NVD and ICS-CERT for vulnerabilities\n2. Assess applicability to device components\n3. Develop and test patches\n4. Communicate with customers\n5. Report to FDA per guidance\n\n### Coordinated Vulnerability Disclosure\n\n```\nResearcher Report\n    ↓\nAcknowledgment (48 hours)\n    ↓\nInitial Assessment (5 days)\n    ↓\nFix Development\n    ↓\nCoordinated Public Disclosure\n```\n\n**Reference:** See [device_cybersecurity_guidance.md](references\u002Fdevice_cybersecurity_guidance.md) for SBOM format examples and threat modeling templates.\n\n---\n\n## Resources\n\n### scripts\u002F\n\n| Script | Purpose |\n|--------|---------|\n| `fda_submission_tracker.py` | Track 510(k)\u002FPMA\u002FDe Novo submission milestones and timelines |\n| `qsr_compliance_checker.py` | Assess 21 CFR 820 compliance against project documentation |\n| `hipaa_risk_assessment.py` | Evaluate HIPAA safeguards in medical device software |\n\n### references\u002F\n\n| File | Content |\n|------|---------|\n| `fda_submission_guide.md` | 510(k), De Novo, PMA submission requirements and checklists |\n| `qsr_compliance_requirements.md` | 21 CFR 820 implementation guide with templates |\n| `hipaa_compliance_framework.md` | HIPAA Security Rule safeguards and BAA requirements |\n| `device_cybersecurity_guidance.md` | FDA cybersecurity requirements, SBOM, threat modeling |\n| `fda_capa_requirements.md` | CAPA process, root cause analysis, effectiveness verification |\n\n### Usage Examples\n\n```bash\n# Track FDA submission status\npython scripts\u002Ffda_submission_tracker.py \u002Fpath\u002Fto\u002Fproject --type 510k\n\n# Assess QSR compliance\npython scripts\u002Fqsr_compliance_checker.py \u002Fpath\u002Fto\u002Fproject --section 820.30\n\n# Run HIPAA risk assessment\npython scripts\u002Fhipaa_risk_assessment.py \u002Fpath\u002Fto\u002Fproject --category technical\n```\n",{"name":5,"description":7},"devin\u002F1780503568-install-devin-skills","c1c6a7ac191f1fb795ae7f57f2fbfa600d3ef56b","ra-qm-team\u002Fskills\u002Ffda-consultant-specialist",0,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin","https:\u002F\u002Fgithub.com\u002Fkruxshnx","https:\u002F\u002Fgovinda-krishna.vercel.app\u002F","2026-06-04 00:21:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kruxshnx\u002Fclaude-skills-devin --skill fda-consultant-specialist",{"tool":38,"command":39},"bunx","bunx skills add kruxshnx\u002Fclaude-skills-devin --skill fda-consultant-specialist",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kruxshnx\u002Fclaude-skills-devin --skill fda-consultant-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002FSKILL.md",true,[46,52,56,60,64,68,74,78],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdevice_cybersecurity_guidance.md","REFERENCE","参考文档",18342,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Freferences\u002Fdevice_cybersecurity_guidance.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Ffda_capa_requirements.md",22415,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Freferences\u002Ffda_capa_requirements.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Ffda_submission_guide.md",11793,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Freferences\u002Ffda_submission_guide.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fhipaa_compliance_framework.md",19254,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Freferences\u002Fhipaa_compliance_framework.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fqsr_compliance_requirements.md",18822,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Freferences\u002Fqsr_compliance_requirements.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Ffda_submission_tracker.py","SCRIPT","脚本",19656,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Ffda_submission_tracker.py",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fhipaa_risk_assessment.py",23184,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fhipaa_risk_assessment.py",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fqsr_compliance_checker.py",24657,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fqsr_compliance_checker.py",[83,90,97,104,111,118],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M779G0P3W78CJF700K9AHJ6M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M779FBBF54JKVQAGBAYHWE0B","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M779EQ39CGK5Q4V78KC0HNMV","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M779EDS05MYFXBF7PGTVSDMA","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M779DVA52T5F0YC5HSM9BW4Z","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M779D3SGW8FM1N8G0HK860WT","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]