[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASB2HVR4MDFBX07FDGZD6Z":3,"skill-same:01M7ASB2HVR4MDFBX07FDGZD6Z":86},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M7ASB2HVR4MDFBX07FDGZD6Z","regulatory-affairs-head",null,"Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","GongYuanCaiJi\u002Fdsh-claude-skills","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7APPQ7AEZTDQB0N6HCPTR2X",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fregulatory-affairs-head\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"regulatory-affairs-head\"\ndescription: Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.\ntriggers:\n  - regulatory strategy\n  - FDA submission\n  - EU MDR\n  - 510(k)\n  - PMA approval\n  - CE marking\n  - regulatory pathway\n  - market access\n  - clinical evidence\n  - regulatory intelligence\n  - submission planning\n  - notified body\n---\n\n# Head of Regulatory Affairs\n\nRegulatory strategy development, submission management, and global market access for medical device organizations.\n\n---\n\n## Table of Contents\n\n- [Regulatory Strategy Workflow](#regulatory-strategy-workflow)\n- [FDA Submission Workflow](#fda-submission-workflow)\n- [EU MDR Submission Workflow](#eu-mdr-submission-workflow)\n- [Global Market Access Workflow](#global-market-access-workflow)\n- [Regulatory Intelligence Workflow](#regulatory-intelligence-workflow)\n- [Decision Frameworks](#decision-frameworks)\n- [Tools and References](#tools-and-references)\n\n---\n\n## Regulatory Strategy Workflow\n\nDevelop regulatory strategy aligned with business objectives and product characteristics.\n\n### Workflow: New Product Regulatory Strategy\n\n1. Gather product information:\n   - Intended use and indications\n   - Device classification (risk level)\n   - Technology platform\n   - Target markets and timeline\n2. Identify applicable regulations per target market:\n   - FDA (US): 21 CFR Part 820, 510(k)\u002FPMA\u002FDe Novo\n   - EU: MDR 2017\u002F745, Notified Body requirements\n   - Other markets: Health Canada, PMDA, NMPA, TGA\n3. Determine optimal regulatory pathway:\n   - Compare submission types (510(k) vs De Novo vs PMA)\n   - Assess predicate device availability\n   - Evaluate clinical evidence requirements\n4. Develop regulatory timeline with milestones\n5. Estimate resource requirements and budget\n6. Identify regulatory risks and mitigation strategies\n7. Obtain stakeholder alignment and approval\n8. **Validation:** Strategy document approved; timeline accepted; resources allocated\n\n### Regulatory Pathway Selection Matrix\n\n| Factor | 510(k) | De Novo | PMA |\n|--------|--------|---------|-----|\n| Predicate Available | Yes | No | N\u002FA |\n| Risk Level | Low-Moderate | Low-Moderate | High |\n| Clinical Data | Usually not required | May be required | Required |\n| Review Time | 90 days (MDUFA) | 150 days | 180 days |\n| User Fee | ~$22K (2024) | ~$135K | ~$440K |\n| Best For | Me-too devices | Novel low-risk | High-risk, novel |\n\n### Regulatory Strategy Document Template\n\n```\nREGULATORY STRATEGY\n\nProduct: [Name]   Version: [X.X]   Date: [Date]\n\n1. PRODUCT OVERVIEW\n   Intended use: [One-sentence statement of intended patient population, body site, and clinical purpose]\n   Device classification: [Class I \u002F II \u002F III]\n   Technology: [Brief description, e.g., \"AI-powered wound-imaging software, SaMD\"]\n\n2. TARGET MARKETS & TIMELINE\n   | Market | Pathway        | Priority | Target Date |\n   |--------|----------------|----------|-------------|\n   | USA    | 510(k) \u002F PMA   | 1        | Q1 20XX     |\n   | EU     | Class [X] MDR  | 2        | Q2 20XX     |\n\n3. REGULATORY PATHWAY RATIONALE\n   FDA: [510(k) \u002F De Novo \u002F PMA] — Predicate: [K-number or \"none\"]\n   EU:  Class [X] via [Annex IX \u002F X \u002F XI] — NB: [Name or TBD]\n   Rationale: [2–3 sentences on key factors driving pathway choice]\n\n4. CLINICAL EVIDENCE STRATEGY\n   Requirements: [Summarize what each market needs, e.g., \"510(k): bench + usability; EU Class IIb: PMCF study\"]\n   Approach: [Literature review \u002F Prospective study \u002F Combination]\n\n5. RISKS AND MITIGATION\n   | Risk                         | Prob | Impact | Mitigation                        |\n   |------------------------------|------|--------|-----------------------------------|\n   | Predicate delisted by FDA    | Low  | High   | Identify secondary predicate now  |\n   | NB audit backlog             | Med  | Med    | Engage NB 6 months before target  |\n\n6. RESOURCE REQUIREMENTS\n   Budget: $[Amount]   Personnel: [FTEs]   External: [Consultants \u002F CRO]\n```\n\n---\n\n## FDA Submission Workflow\n\nPrepare and submit FDA regulatory applications.\n\n### Workflow: 510(k) Submission\n\n1. Confirm 510(k) pathway suitability:\n   - Predicate device identified (note K-number, e.g., K213456)\n   - Substantial equivalence (SE) argument supportable on intended use and technological characteristics\n   - No new intended use or technology concerns triggering De Novo\n2. Schedule and conduct Pre-Submission (Q-Sub) meeting if needed (see [Pre-Sub Decision](#pre-submission-meeting-decision))\n3. Compile submission package checklist:\n   - [ ] Cover letter with device name, product code, and predicate K-number\n   - [ ] Section 1: Administrative information (applicant, contact, 510(k) type)\n   - [ ] Section 2: Device description — include photos, dimensions, materials list\n   - [ ] Section 3: Intended use and indications for use\n   - [ ] Section 4: Substantial equivalence comparison table (see example below)\n   - [ ] Section 5: Performance testing — protocols, standards cited, pass\u002Ffail results\n   - [ ] Section 6: Biocompatibility summary (ISO 10993-1 risk assessment, if patient contact)\n   - [ ] Section 7: Software documentation (IEC 62304 level, cybersecurity per FDA guidance, if applicable)\n   - [ ] Section 8: Labeling — final draft IFU, device label\n   - [ ] Section 9: Summary and conclusion\n4. Conduct internal review and quality check against FDA RTA checklist\n5. Prepare eCopy per FDA format requirements (PDF bookmarked, eCopy cover page)\n6. Submit via FDA ESG portal with user fee payment\n7. Monitor MDUFA clock and respond to AI\u002FRTA requests within deadlines\n8. **Validation:** Submission accepted; MDUFA date received; tracking system updated\n\n#### Substantial Equivalence Comparison Example\n\n| Characteristic | Predicate (K213456) | Subject Device | Same? | Notes |\n|----------------|---------------------|----------------|-------|-------|\n| Intended use | Wound measurement | Wound measurement | ✓ | Identical |\n| Technology | 2D camera | 2D + AI analysis | ✗ | New TC; address below |\n| Energy type | Non-energized | Non-energized | ✓ | |\n| Patient contact | No | No | ✓ | |\n| SE conclusion | New TC does not raise new safety\u002Feffectiveness questions; bench data demonstrates equivalent accuracy (±2mm vs ±3mm predicate) |\n\n### Workflow: PMA Submission\n\n1. Confirm PMA pathway:\n   - Class III device or no suitable predicate\n   - Clinical data strategy defined\n2. Complete IDE clinical study if required:\n   - IDE approval\n   - Clinical protocol execution\n   - Study report completion\n3. Conduct Pre-Submission meeting\n4. Compile PMA submission checklist:\n   - [ ] Volume I: Administrative, device description, manufacturing\n   - [ ] Volume II: Nonclinical studies (bench, animal, biocompatibility)\n   - [ ] Volume III: Clinical studies (IDE protocol, data, statistical analysis)\n   - [ ] Volume IV: Labeling\n   - [ ] Volume V: Manufacturing information, sterilization\n5. Submit original PMA application\n6. Address FDA questions and deficiencies\n7. Prepare for FDA facility inspection\n8. **Validation:** PMA approved; approval letter received; post-approval requirements documented\n\n### FDA Submission Timeline\n\n| Milestone | 510(k) | De Novo | PMA |\n|-----------|--------|---------|-----|\n| Pre-Sub Meeting | Day -90 | Day -90 | Day -120 |\n| Submission | Day 0 | Day 0 | Day 0 |\n| RTA Review | Day 15 | Day 15 | Day 45 |\n| Substantive Review | Days 15–90 | Days 15–150 | Days 45–180 |\n| Decision | Day 90 | Day 150 | Day 180 |\n\n### Common FDA Deficiencies and Prevention\n\n| Category | Common Issues | Prevention |\n|----------|---------------|------------|\n| Substantial Equivalence | Weak predicate comparison; no performance data | Build SE table with data column; cite recognized standards |\n| Performance Testing | Incomplete protocols; missing worst-case rationale | Follow FDA-recognized standards; document worst-case justification |\n| Biocompatibility | Missing endpoints; no ISO 10993-1 risk assessment | Complete ISO 10993-1 matrix before testing |\n| Software | Inadequate hazard analysis; no cybersecurity bill of materials | IEC 62304 compliance + FDA cybersecurity guidance checklist |\n| Labeling | Inconsistent claims vs. IFU; missing symbols standard | Cross-check label against IFU; cite ISO 15223-1 for symbols |\n\nSee: [references\u002Ffda-submission-guide.md](references\u002Ffda-submission-guide.md)\n\n---\n\n## EU MDR Submission Workflow\n\nAchieve CE marking under EU MDR 2017\u002F745.\n\n### Workflow: MDR Technical Documentation\n\n1. Confirm device classification per MDR Annex VIII\n2. Select conformity assessment route based on class:\n   - Class I: Self-declaration\n   - Class IIa\u002FIIb: Notified Body involvement\n   - Class III: Full NB assessment\n3. Select and engage Notified Body (for Class IIa+) — see selection criteria below\n4. Compile Technical Documentation per Annex II checklist:\n   - [ ] Annex II §1: Device description, intended purpose, UDI\n   - [ ] Annex II §2: Design and manufacturing information (drawings, BoM, process flows)\n   - [ ] Annex II §3: GSPR checklist — each requirement mapped to evidence (standard, test report, or justification)\n   - [ ] Annex II §4: Benefit-risk analysis and risk management file (ISO 14971)\n   - [ ] Annex II §5: Product verification and validation (test reports)\n   - [ ] Annex II §6: Post-market surveillance plan\n   - [ ] Annex XIV: Clinical evaluation report (CER) — literature, clinical data, equivalence justification\n5. Establish and document QMS per ISO 13485\n6. Submit application to Notified Body\n7. Address NB questions and coordinate audit\n8. **Validation:** CE certificate issued; Declaration of Conformity signed; EUDAMED registration complete\n\n#### GSPR Checklist Row Example\n\n| GSPR Ref | Requirement | Standard \u002F Guidance | Evidence Document | Status |\n|----------|-------------|---------------------|-------------------|--------|\n| Annex I §1 | Safe design and manufacture | ISO 14971:2019 | Risk Management File v2.1 | Complete |\n| Annex I §11.1 | Devices with measuring function ±accuracy | EN ISO 15223-1 | Performance Test Report PT-003 | Complete |\n| Annex I §17 | Cybersecurity | MDCG 2019-16 | Cybersecurity Assessment CS-001 | In progress |\n\n### Clinical Evidence Requirements by Class\n\n| Class | Clinical Requirement | Documentation |\n|-------|---------------------|---------------|\n| I | Clinical evaluation (CE) | CE report |\n| IIa | CE with literature focus | CE report + PMCF plan |\n| IIb | CE with clinical data | CE report + PMCF + clinical study (some) |\n| III | CE with clinical investigation | CE report + PMCF + clinical investigation |\n\n### Notified Body Selection Criteria\n\n- **Scope:** Designated for your specific device category\n- **Capacity:** Confirmed availability within target timeline\n- **Experience:** Track record with your technology type\n- **Geography:** Proximity for on-site audits\n- **Cost:** Fee structure transparency\n- **Communication:** Responsiveness and query turnaround\n\nSee: [references\u002Feu-mdr-submission-guide.md](references\u002Feu-mdr-submission-guide.md)\n\n---\n\n## Global Market Access Workflow\n\nCoordinate regulatory approvals across international markets.\n\n### Workflow: Multi-Market Submission Strategy\n\n1. Define target markets based on business priorities\n2. Sequence markets for efficient evidence leverage:\n   - Phase 1: FDA + EU (reference markets)\n   - Phase 2: Recognition markets (Canada, Australia)\n   - Phase 3: Major markets (Japan, China)\n   - Phase 4: Emerging markets\n3. Identify local requirements per market:\n   - Clinical data acceptability\n   - Local agent\u002Frepresentative needs\n   - Language and labeling requirements\n4. Develop master technical file with localization plan\n5. Establish in-country regulatory support\n6. Execute parallel or sequential submissions\n7. Track approvals and coordinate launches\n8. **Validation:** All target market approvals obtained; registration database updated\n\n### Market Priority Matrix\n\n| Market | Size | Complexity | Recognition | Priority |\n|--------|------|------------|-------------|----------|\n| USA | Large | High | N\u002FA | 1 |\n| EU | Large | High | N\u002FA | 1–2 |\n| Canada | Medium | Medium | MDSAP | 2 |\n| Australia | Medium | Low | EU accepted | 2 |\n| Japan | Large | High | Local clinical | 3 |\n| China | Large | Very High | Local testing | 3 |\n| Brazil | Medium | High | GMP inspection | 3–4 |\n\n### Documentation Efficiency Strategy\n\n| Document Type | Single Source | Localization Required |\n|---------------|---------------|----------------------|\n| Technical file core | Yes | Format adaptation |\n| Risk management | Yes | None |\n| Clinical data | Yes | Bridging assessment |\n| QMS certificate | Yes (ISO 13485) | Market-specific audit |\n| Labeling | Master label | Translation, local requirements |\n| IFU | Master content | Translation, local symbols |\n\nSee: [references\u002Fglobal-regulatory-pathways.md](references\u002Fglobal-regulatory-pathways.md)\n\n---\n\n## Regulatory Intelligence Workflow\n\nMonitor and respond to regulatory changes affecting product portfolio.\n\n### Workflow: Regulatory Change Management\n\n1. Monitor regulatory sources:\n   - FDA Federal Register, guidance documents\n   - EU Official Journal, MDCG guidance\n   - Notified Body communications\n   - Industry associations (AdvaMed, MedTech Europe)\n2. Assess relevance to product portfolio\n3. Evaluate impact:\n   - Timeline to compliance\n   - Resource requirements\n   - Product changes needed\n4. Develop compliance action plan\n5. Communicate to affected stakeholders\n6. Implement required changes\n7. Document compliance status\n8. **Validation:** Compliance action plan approved; changes implemented on schedule\n\n### Regulatory Monitoring Sources\n\n| Source | Type | Frequency |\n|--------|------|-----------|\n| FDA Federal Register | Regulations, guidance | Daily |\n| FDA Device Database | 510(k), PMA, recalls | Weekly |\n| EU Official Journal | MDR\u002FIVDR updates | Weekly |\n| MDCG Guidance | EU implementation | As published |\n| ISO\u002FIEC | Standards updates | Quarterly |\n| Notified Body | Audit findings, trends | Per interaction |\n\n### Impact Assessment Template\n\n```\nREGULATORY CHANGE IMPACT ASSESSMENT\n\nChange: [Description]   Source: [Regulation\u002FGuidance]\nEffective Date: [Date]  Assessment Date: [Date]  Assessed By: [Name]\n\nAFFECTED PRODUCTS\n| Product | Impact (H\u002FM\u002FL) | Action Required        | Due Date |\n|---------|----------------|------------------------|----------|\n| [Name]  | [H\u002FM\u002FL]        | [Specific action]      | [Date]   |\n\nCOMPLIANCE ACTIONS\n1. [Action] — Owner: [Name] — Due: [Date]\n2. [Action] — Owner: [Name] — Due: [Date]\n\nRESOURCE REQUIREMENTS: Budget $[X]  |  Personnel [X] hrs\n\nAPPROVAL: Regulatory _____________ Date _______ \u002F Management _____________ Date _______\n```\n\n---\n\n## Decision Frameworks\n\n### Pathway Selection and Classification Reference\n\n**FDA Pathway Selection**\n\n```\nIs predicate device available?\n            │\n        Yes─┴─No\n         │     │\n         ▼     ▼\n    Is device   Is risk level\n    substantially  Low-Moderate?\n    equivalent?       │\n         │        Yes─┴─No\n     Yes─┴─No      │     │\n      │     │      ▼     ▼\n      ▼     ▼   De Novo  PMA\n    510(k)  Consider      required\n           De Novo\n           or PMA\n```\n\n**EU MDR Classification**\n\n```\nIs the device active?\n        │\n    Yes─┴─No\n     │     │\n     ▼     ▼\nIs it an   Does it contact\nimplant?   the body?\n  │            │\nYes─┴─No   Yes─┴─No\n │    │     │     │\n ▼    ▼     ▼     ▼\nIII  IIb  Check   Class I\n         contact  (measuring\u002F\n         type     sterile if\n         and      applicable)\n         duration\n```\n\n### Pre-Submission Meeting Decision\n\n| Factor | Schedule Pre-Sub | Skip Pre-Sub |\n|--------|------------------|--------------|\n| Novel Technology | ✓ | |\n| New Intended Use | ✓ | |\n| Complex Testing | ✓ | |\n| Uncertain Predicate | ✓ | |\n| Clinical Data Needed | ✓ | |\n| Well-established | | ✓ |\n| Clear Predicate | | ✓ |\n| Standard Testing | | ✓ |\n\n### Regulatory Escalation Criteria\n\n| Situation | Escalation Level | Action |\n|-----------|------------------|--------|\n| Submission rejection | VP Regulatory | Root cause analysis, strategy revision |\n| Major deficiency | Director | Cross-functional response team |\n| Timeline at risk | Management | Resource reallocation review |\n| Regulatory change | VP Regulatory | Portfolio impact assessment |\n| Safety signal | Executive | Immediate containment and reporting |\n\n---\n\n## Tools and References\n\n### Scripts\n\n| Tool | Purpose | Usage |\n|------|---------|-------|\n| [regulatory_tracker.py](scripts\u002Fregulatory_tracker.py) | Track submission status and timelines | `python regulatory_tracker.py` |\n\n**Regulatory Tracker Features:**\n- Track multiple submissions across markets\n- Monitor status and target dates\n- Identify overdue submissions\n- Generate status reports\n\n**Example usage:**\n```bash\n$ python regulatory_tracker.py --report status\nSubmission Status Report — 2024-11-01\n┌──────────────────┬──────────┬────────────┬─────────────┬──────────┐\n│ Product          │ Market   │ Type       │ Target Date │ Status   │\n├──────────────────┼──────────┼────────────┼─────────────┼──────────┤\n│ WoundScan Pro    │ USA      │ 510(k)     │ 2024-12-01  │ On Track │\n│ WoundScan Pro    │ EU       │ MDR IIb    │ 2025-03-01  │ At Risk  │\n│ CardioMonitor X1 │ Canada   │ Class II   │ 2025-01-15  │ On Track │\n└──────────────────┴──────────┴────────────┴─────────────┴──────────┘\n1 submission at risk: WoundScan Pro EU — NB engagement not confirmed.\n```\n\n### References\n\n| Document | Content |\n|----------|---------|\n| [fda-submission-guide.md](references\u002Ffda-submission-guide.md) | FDA pathways, requirements, review process |\n| [eu-mdr-submission-guide.md](references\u002Feu-mdr-submission-guide.md) | MDR classification, technical documentation, clinical evidence |\n| [global-regulatory-pathways.md](references\u002Fglobal-regulatory-pathways.md) | Canada, Japan, China, Australia, Brazil requirements |\n| [iso-regulatory-requirements.md](references\u002Fiso-regulatory-requirements.md) | ISO 13485, 14971, 10993, IEC 62304, 62366 requirements |\n\n### Key Performance Indicators\n\n| KPI | Target | Calculation |\n|-----|--------|-------------|\n| First-time approval rate | >85% | (Approved without major deficiency \u002F Total submitted) × 100 |\n| On-time submission | >90% | (Submitted by target date \u002F Total submissions) × 100 |\n| Review cycle compliance | >95% | (Responses within deadline \u002F Total requests) × 100 |\n| Regulatory hold time | \u003C20% | (Days on hold \u002F Total review days) × 100 |\n\n---\n\n## Related Skills\n\n| Skill | Integration Point |\n|-------|-------------------|\n| [mdr-745-specialist](..\u002Fmdr-745-specialist\u002F) | Detailed EU MDR technical requirements |\n| [fda-consultant-specialist](..\u002Ffda-consultant-specialist\u002F) | FDA submission deep expertise |\n| [quality-manager-qms-iso13485](..\u002Fquality-manager-qms-iso13485\u002F) | QMS for regulatory compliance |\n| [risk-management-specialist](..\u002Frisk-management-specialist\u002F) | ISO 14971 risk management |\n","# Head of Regulatory Affairs\n\nRegulatory strategy development, submission management, and global market access for medical device organizations.\n\n---\n\n## Table of Contents\n\n- [Regulatory Strategy Workflow](#regulatory-strategy-workflow)\n- [FDA Submission Workflow](#fda-submission-workflow)\n- [EU MDR Submission Workflow](#eu-mdr-submission-workflow)\n- [Global Market Access Workflow](#global-market-access-workflow)\n- [Regulatory Intelligence Workflow](#regulatory-intelligence-workflow)\n- [Decision Frameworks](#decision-frameworks)\n- [Tools and References](#tools-and-references)\n\n---\n\n## Regulatory Strategy Workflow\n\nDevelop regulatory strategy aligned with business objectives and product characteristics.\n\n### Workflow: New Product Regulatory Strategy\n\n1. Gather product information:\n   - Intended use and indications\n   - Device classification (risk level)\n   - Technology platform\n   - Target markets and timeline\n2. Identify applicable regulations per target market:\n   - FDA (US): 21 CFR Part 820, 510(k)\u002FPMA\u002FDe Novo\n   - EU: MDR 2017\u002F745, Notified Body requirements\n   - Other markets: Health Canada, PMDA, NMPA, TGA\n3. Determine optimal regulatory pathway:\n   - Compare submission types (510(k) vs De Novo vs PMA)\n   - Assess predicate device availability\n   - Evaluate clinical evidence requirements\n4. Develop regulatory timeline with milestones\n5. Estimate resource requirements and budget\n6. Identify regulatory risks and mitigation strategies\n7. Obtain stakeholder alignment and approval\n8. **Validation:** Strategy document approved; timeline accepted; resources allocated\n\n### Regulatory Pathway Selection Matrix\n\n| Factor | 510(k) | De Novo | PMA |\n|--------|--------|---------|-----|\n| Predicate Available | Yes | No | N\u002FA |\n| Risk Level | Low-Moderate | Low-Moderate | High |\n| Clinical Data | Usually not required | May be required | Required |\n| Review Time | 90 days (MDUFA) | 150 days | 180 days |\n| User Fee | ~$22K (2024) | ~$135K | ~$440K |\n| Best For | Me-too devices | Novel low-risk | High-risk, novel |\n\n### Regulatory Strategy Document Template\n\n```\nREGULATORY STRATEGY\n\nProduct: [Name]   Version: [X.X]   Date: [Date]\n\n1. PRODUCT OVERVIEW\n   Intended use: [One-sentence statement of intended patient population, body site, and clinical purpose]\n   Device classification: [Class I \u002F II \u002F III]\n   Technology: [Brief description, e.g., \"AI-powered wound-imaging software, SaMD\"]\n\n2. TARGET MARKETS & TIMELINE\n   | Market | Pathway        | Priority | Target Date |\n   |--------|----------------|----------|-------------|\n   | USA    | 510(k) \u002F PMA   | 1        | Q1 20XX     |\n   | EU     | Class [X] MDR  | 2        | Q2 20XX     |\n\n3. REGULATORY PATHWAY RATIONALE\n   FDA: [510(k) \u002F De Novo \u002F PMA] — Predicate: [K-number or \"none\"]\n   EU:  Class [X] via [Annex IX \u002F X \u002F XI] — NB: [Name or TBD]\n   Rationale: [2–3 sentences on key factors driving pathway choice]\n\n4. CLINICAL EVIDENCE STRATEGY\n   Requirements: [Summarize what each market needs, e.g., \"510(k): bench + usability; EU Class IIb: PMCF study\"]\n   Approach: [Literature review \u002F Prospective study \u002F Combination]\n\n5. RISKS AND MITIGATION\n   | Risk                         | Prob | Impact | Mitigation                        |\n   |------------------------------|------|--------|-----------------------------------|\n   | Predicate delisted by FDA    | Low  | High   | Identify secondary predicate now  |\n   | NB audit backlog             | Med  | Med    | Engage NB 6 months before target  |\n\n6. RESOURCE REQUIREMENTS\n   Budget: $[Amount]   Personnel: [FTEs]   External: [Consultants \u002F CRO]\n```\n\n---\n\n## FDA Submission Workflow\n\nPrepare and submit FDA regulatory applications.\n\n### Workflow: 510(k) Submission\n\n1. Confirm 510(k) pathway suitability:\n   - Predicate device identified (note K-number, e.g., K213456)\n   - Substantial equivalence (SE) argument supportable on intended use and technological characteristics\n   - No new intended use or technology concerns triggering De Novo\n2. Schedule and conduct Pre-Submission (Q-Sub) meeting if needed (see [Pre-Sub Decision](#pre-submission-meeting-decision))\n3. Compile submission package checklist:\n   - [ ] Cover letter with device name, product code, and predicate K-number\n   - [ ] Section 1: Administrative information (applicant, contact, 510(k) type)\n   - [ ] Section 2: Device description — include photos, dimensions, materials list\n   - [ ] Section 3: Intended use and indications for use\n   - [ ] Section 4: Substantial equivalence comparison table (see example below)\n   - [ ] Section 5: Performance testing — protocols, standards cited, pass\u002Ffail results\n   - [ ] Section 6: Biocompatibility summary (ISO 10993-1 risk assessment, if patient contact)\n   - [ ] Section 7: Software documentation (IEC 62304 level, cybersecurity per FDA guidance, if applicable)\n   - [ ] Section 8: Labeling — final draft IFU, device label\n   - [ ] Section 9: Summary and conclusion\n4. Conduct internal review and quality check against FDA RTA checklist\n5. Prepare eCopy per FDA format requirements (PDF bookmarked, eCopy cover page)\n6. Submit via FDA ESG portal with user fee payment\n7. Monitor MDUFA clock and respond to AI\u002FRTA requests within deadlines\n8. **Validation:** Submission accepted; MDUFA date received; tracking system updated\n\n#### Substantial Equivalence Comparison Example\n\n| Characteristic | Predicate (K213456) | Subject Device | Same? | Notes |\n|----------------|---------------------|----------------|-------|-------|\n| Intended use | Wound measurement | Wound measurement | ✓ | Identical |\n| Technology | 2D camera | 2D + AI analysis | ✗ | New TC; address below |\n| Energy type | Non-energized | Non-energized | ✓ | |\n| Patient contact | No | No | ✓ | |\n| SE conclusion | New TC does not raise new safety\u002Feffectiveness questions; bench data demonstrates equivalent accuracy (±2mm vs ±3mm predicate) |\n\n### Workflow: PMA Submission\n\n1. Confirm PMA pathway:\n   - Class III device or no suitable predicate\n   - Clinical data strategy defined\n2. Complete IDE clinical study if required:\n   - IDE approval\n   - Clinical protocol execution\n   - Study report completion\n3. Conduct Pre-Submission meeting\n4. Compile PMA submission checklist:\n   - [ ] Volume I: Administrative, device description, manufacturing\n   - [ ] Volume II: Nonclinical studies (bench, animal, biocompatibility)\n   - [ ] Volume III: Clinical studies (IDE protocol, data, statistical analysis)\n   - [ ] Volume IV: Labeling\n   - [ ] Volume V: Manufacturing information, sterilization\n5. Submit original PMA application\n6. Address FDA questions and deficiencies\n7. Prepare for FDA facility inspection\n8. **Validation:** PMA approved; approval letter received; post-approval requirements documented\n\n### FDA Submission Timeline\n\n| Milestone | 510(k) | De Novo | PMA |\n|-----------|--------|---------|-----|\n| Pre-Sub Meeting | Day -90 | Day -90 | Day -120 |\n| Submission | Day 0 | Day 0 | Day 0 |\n| RTA Review | Day 15 | Day 15 | Day 45 |\n| Substantive Review | Days 15–90 | Days 15–150 | Days 45–180 |\n| Decision | Day 90 | Day 150 | Day 180 |\n\n### Common FDA Deficiencies and Prevention\n\n| Category | Common Issues | Prevention |\n|----------|---------------|------------|\n| Substantial Equivalence | Weak predicate comparison; no performance data | Build SE table with data column; cite recognized standards |\n| Performance Testing | Incomplete protocols; missing worst-case rationale | Follow FDA-recognized standards; document worst-case justification |\n| Biocompatibility | Missing endpoints; no ISO 10993-1 risk assessment | Complete ISO 10993-1 matrix before testing |\n| Software | Inadequate hazard analysis; no cybersecurity bill of materials | IEC 62304 compliance + FDA cybersecurity guidance checklist |\n| Labeling | Inconsistent claims vs. IFU; missing symbols standard | Cross-check label against IFU; cite ISO 15223-1 for symbols |\n\nSee: [references\u002Ffda-submission-guide.md](references\u002Ffda-submission-guide.md)\n\n---\n\n## EU MDR Submission Workflow\n\nAchieve CE marking under EU MDR 2017\u002F745.\n\n### Workflow: MDR Technical Documentation\n\n1. Confirm device classification per MDR Annex VIII\n2. Select conformity assessment route based on class:\n   - Class I: Self-declaration\n   - Class IIa\u002FIIb: Notified Body involvement\n   - Class III: Full NB assessment\n3. Select and engage Notified Body (for Class IIa+) — see selection criteria below\n4. Compile Technical Documentation per Annex II checklist:\n   - [ ] Annex II §1: Device description, intended purpose, UDI\n   - [ ] Annex II §2: Design and manufacturing information (drawings, BoM, process flows)\n   - [ ] Annex II §3: GSPR checklist — each requirement mapped to evidence (standard, test report, or justification)\n   - [ ] Annex II §4: Benefit-risk analysis and risk management file (ISO 14971)\n   - [ ] Annex II §5: Product verification and validation (test reports)\n   - [ ] Annex II §6: Post-market surveillance plan\n   - [ ] Annex XIV: Clinical evaluation report (CER) — literature, clinical data, equivalence justification\n5. Establish and document QMS per ISO 13485\n6. Submit application to Notified Body\n7. Address NB questions and coordinate audit\n8. **Validation:** CE certificate issued; Declaration of Conformity signed; EUDAMED registration complete\n\n#### GSPR Checklist Row Example\n\n| GSPR Ref | Requirement | Standard \u002F Guidance | Evidence Document | Status |\n|----------|-------------|---------------------|-------------------|--------|\n| Annex I §1 | Safe design and manufacture | ISO 14971:2019 | Risk Management File v2.1 | Complete |\n| Annex I §11.1 | Devices with measuring function ±accuracy | EN ISO 15223-1 | Performance Test Report PT-003 | Complete |\n| Annex I §17 | Cybersecurity | MDCG 2019-16 | Cybersecurity Assessment CS-001 | In progress |\n\n### Clinical Evidence Requirements by Class\n\n| Class | Clinical Requirement | Documentation |\n|-------|---------------------|---------------|\n| I | Clinical evaluation (CE) | CE report |\n| IIa | CE with literature focus | CE report + PMCF plan |\n| IIb | CE with clinical data | CE report + PMCF + clinical study (some) |\n| III | CE with clinical investigation | CE report + PMCF + clinical investigation |\n\n### Notified Body Selection Criteria\n\n- **Scope:** Designated for your specific device category\n- **Capacity:** Confirmed availability within target timeline\n- **Experience:** Track record with your technology type\n- **Geography:** Proximity for on-site audits\n- **Cost:** Fee structure transparency\n- **Communication:** Responsiveness and query turnaround\n\nSee: [references\u002Feu-mdr-submission-guide.md](references\u002Feu-mdr-submission-guide.md)\n\n---\n\n## Global Market Access Workflow\n\nCoordinate regulatory approvals across international markets.\n\n### Workflow: Multi-Market Submission Strategy\n\n1. Define target markets based on business priorities\n2. Sequence markets for efficient evidence leverage:\n   - Phase 1: FDA + EU (reference markets)\n   - Phase 2: Recognition markets (Canada, Australia)\n   - Phase 3: Major markets (Japan, China)\n   - Phase 4: Emerging markets\n3. Identify local requirements per market:\n   - Clinical data acceptability\n   - Local agent\u002Frepresentative needs\n   - Language and labeling requirements\n4. Develop master technical file with localization plan\n5. Establish in-country regulatory support\n6. Execute parallel or sequential submissions\n7. Track approvals and coordinate launches\n8. **Validation:** All target market approvals obtained; registration database updated\n\n### Market Priority Matrix\n\n| Market | Size | Complexity | Recognition | Priority |\n|--------|------|------------|-------------|----------|\n| USA | Large | High | N\u002FA | 1 |\n| EU | Large | High | N\u002FA | 1–2 |\n| Canada | Medium | Medium | MDSAP | 2 |\n| Australia | Medium | Low | EU accepted | 2 |\n| Japan | Large | High | Local clinical | 3 |\n| China | Large | Very High | Local testing | 3 |\n| Brazil | Medium | High | GMP inspection | 3–4 |\n\n### Documentation Efficiency Strategy\n\n| Document Type | Single Source | Localization Required |\n|---------------|---------------|----------------------|\n| Technical file core | Yes | Format adaptation |\n| Risk management | Yes | None |\n| Clinical data | Yes | Bridging assessment |\n| QMS certificate | Yes (ISO 13485) | Market-specific audit |\n| Labeling | Master label | Translation, local requirements |\n| IFU | Master content | Translation, local symbols |\n\nSee: [references\u002Fglobal-regulatory-pathways.md](references\u002Fglobal-regulatory-pathways.md)\n\n---\n\n## Regulatory Intelligence Workflow\n\nMonitor and respond to regulatory changes affecting product portfolio.\n\n### Workflow: Regulatory Change Management\n\n1. Monitor regulatory sources:\n   - FDA Federal Register, guidance documents\n   - EU Official Journal, MDCG guidance\n   - Notified Body communications\n   - Industry associations (AdvaMed, MedTech Europe)\n2. Assess relevance to product portfolio\n3. Evaluate impact:\n   - Timeline to compliance\n   - Resource requirements\n   - Product changes needed\n4. Develop compliance action plan\n5. Communicate to affected stakeholders\n6. Implement required changes\n7. Document compliance status\n8. **Validation:** Compliance action plan approved; changes implemented on schedule\n\n### Regulatory Monitoring Sources\n\n| Source | Type | Frequency |\n|--------|------|-----------|\n| FDA Federal Register | Regulations, guidance | Daily |\n| FDA Device Database | 510(k), PMA, recalls | Weekly |\n| EU Official Journal | MDR\u002FIVDR updates | Weekly |\n| MDCG Guidance | EU implementation | As published |\n| ISO\u002FIEC | Standards updates | Quarterly |\n| Notified Body | Audit findings, trends | Per interaction |\n\n### Impact Assessment Template\n\n```\nREGULATORY CHANGE IMPACT ASSESSMENT\n\nChange: [Description]   Source: [Regulation\u002FGuidance]\nEffective Date: [Date]  Assessment Date: [Date]  Assessed By: [Name]\n\nAFFECTED PRODUCTS\n| Product | Impact (H\u002FM\u002FL) | Action Required        | Due Date |\n|---------|----------------|------------------------|----------|\n| [Name]  | [H\u002FM\u002FL]        | [Specific action]      | [Date]   |\n\nCOMPLIANCE ACTIONS\n1. [Action] — Owner: [Name] — Due: [Date]\n2. [Action] — Owner: [Name] — Due: [Date]\n\nRESOURCE REQUIREMENTS: Budget $[X]  |  Personnel [X] hrs\n\nAPPROVAL: Regulatory _____________ Date _______ \u002F Management _____________ Date _______\n```\n\n---\n\n## Decision Frameworks\n\n### Pathway Selection and Classification Reference\n\n**FDA Pathway Selection**\n\n```\nIs predicate device available?\n            │\n        Yes─┴─No\n         │     │\n         ▼     ▼\n    Is device   Is risk level\n    substantially  Low-Moderate?\n    equivalent?       │\n         │        Yes─┴─No\n     Yes─┴─No      │     │\n      │     │      ▼     ▼\n      ▼     ▼   De Novo  PMA\n    510(k)  Consider      required\n           De Novo\n           or PMA\n```\n\n**EU MDR Classification**\n\n```\nIs the device active?\n        │\n    Yes─┴─No\n     │     │\n     ▼     ▼\nIs it an   Does it contact\nimplant?   the body?\n  │            │\nYes─┴─No   Yes─┴─No\n │    │     │     │\n ▼    ▼     ▼     ▼\nIII  IIb  Check   Class I\n         contact  (measuring\u002F\n         type     sterile if\n         and      applicable)\n         duration\n```\n\n### Pre-Submission Meeting Decision\n\n| Factor | Schedule Pre-Sub | Skip Pre-Sub |\n|--------|------------------|--------------|\n| Novel Technology | ✓ | |\n| New Intended Use | ✓ | |\n| Complex Testing | ✓ | |\n| Uncertain Predicate | ✓ | |\n| Clinical Data Needed | ✓ | |\n| Well-established | | ✓ |\n| Clear Predicate | | ✓ |\n| Standard Testing | | ✓ |\n\n### Regulatory Escalation Criteria\n\n| Situation | Escalation Level | Action |\n|-----------|------------------|--------|\n| Submission rejection | VP Regulatory | Root cause analysis, strategy revision |\n| Major deficiency | Director | Cross-functional response team |\n| Timeline at risk | Management | Resource reallocation review |\n| Regulatory change | VP Regulatory | Portfolio impact assessment |\n| Safety signal | Executive | Immediate containment and reporting |\n\n---\n\n## Tools and References\n\n### Scripts\n\n| Tool | Purpose | Usage |\n|------|---------|-------|\n| [regulatory_tracker.py](scripts\u002Fregulatory_tracker.py) | Track submission status and timelines | `python regulatory_tracker.py` |\n\n**Regulatory Tracker Features:**\n- Track multiple submissions across markets\n- Monitor status and target dates\n- Identify overdue submissions\n- Generate status reports\n\n**Example usage:**\n```bash\n$ python regulatory_tracker.py --report status\nSubmission Status Report — 2024-11-01\n┌──────────────────┬──────────┬────────────┬─────────────┬──────────┐\n│ Product          │ Market   │ Type       │ Target Date │ Status   │\n├──────────────────┼──────────┼────────────┼─────────────┼──────────┤\n│ WoundScan Pro    │ USA      │ 510(k)     │ 2024-12-01  │ On Track │\n│ WoundScan Pro    │ EU       │ MDR IIb    │ 2025-03-01  │ At Risk  │\n│ CardioMonitor X1 │ Canada   │ Class II   │ 2025-01-15  │ On Track │\n└──────────────────┴──────────┴────────────┴─────────────┴──────────┘\n1 submission at risk: WoundScan Pro EU — NB engagement not confirmed.\n```\n\n### References\n\n| Document | Content |\n|----------|---------|\n| [fda-submission-guide.md](references\u002Ffda-submission-guide.md) | FDA pathways, requirements, review process |\n| [eu-mdr-submission-guide.md](references\u002Feu-mdr-submission-guide.md) | MDR classification, technical documentation, clinical evidence |\n| [global-regulatory-pathways.md](references\u002Fglobal-regulatory-pathways.md) | Canada, Japan, China, Australia, Brazil requirements |\n| [iso-regulatory-requirements.md](references\u002Fiso-regulatory-requirements.md) | ISO 13485, 14971, 10993, IEC 62304, 62366 requirements |\n\n### Key Performance Indicators\n\n| KPI | Target | Calculation |\n|-----|--------|-------------|\n| First-time approval rate | >85% | (Approved without major deficiency \u002F Total submitted) × 100 |\n| On-time submission | >90% | (Submitted by target date \u002F Total submissions) × 100 |\n| Review cycle compliance | >95% | (Responses within deadline \u002F Total requests) × 100 |\n| Regulatory hold time | \u003C20% | (Days on hold \u002F Total review days) × 100 |\n\n---\n\n## Related Skills\n\n| Skill | Integration Point |\n|-------|-------------------|\n| [mdr-745-specialist](..\u002Fmdr-745-specialist\u002F) | Detailed EU MDR technical requirements |\n| [fda-consultant-specialist](..\u002Ffda-consultant-specialist\u002F) | FDA submission deep expertise |\n| [quality-manager-qms-iso13485](..\u002Fquality-manager-qms-iso13485\u002F) | QMS for regulatory compliance |\n| [risk-management-specialist](..\u002Frisk-management-specialist\u002F) | ISO 14971 risk management |\n",{"name":5,"triggers":24,"description":7},[25,26,27,28,29,30,31,32,33,34,35,36],"regulatory strategy","FDA submission","EU MDR","510(k)","PMA approval","CE marking","regulatory pathway","market access","clinical evidence","regulatory intelligence","submission planning","notified body","main","992d25a425dee442a1f6a628d00a4fed33efe839","ra-qm-team\u002Fskills\u002Fregulatory-affairs-head","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 04:26:20",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill regulatory-affairs-head",{"tool":50,"command":51},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill regulatory-affairs-head",{"tool":53,"command":54},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill regulatory-affairs-head","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fregulatory-affairs-head\u002FSKILL.md",true,[58,64,68,72,76,82],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Feu-mdr-submission-guide.md","REFERENCE","参考文档",3272,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fregulatory-affairs-head\u002Freferences\u002Feu-mdr-submission-guide.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Ffda-submission-guide.md",4442,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fregulatory-affairs-head\u002Freferences\u002Ffda-submission-guide.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fglobal-regulatory-pathways.md",9806,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fregulatory-affairs-head\u002Freferences\u002Fglobal-regulatory-pathways.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fiso-regulatory-requirements.md",14171,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fregulatory-affairs-head\u002Freferences\u002Fiso-regulatory-requirements.md",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fregulatory_pathway_analyzer.py","SCRIPT","脚本",23077,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fregulatory-affairs-head\u002Fscripts\u002Fregulatory_pathway_analyzer.py",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Fregulatory_tracker.py",8223,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fregulatory-affairs-head\u002Fscripts\u002Fregulatory_tracker.py",[87,94,101,108,115,122],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7ASG5XZVP67CMMRENYFQWPW","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. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7ASFSGJF6G9KM40S1QJPR57","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. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"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]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7ASFFNCMS1X5X276VE277KW","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. Use when the user requests multi-source recency intelligence on a topic (e.g., '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]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7ASF2BM8D9CDRQV1VBV7FV6","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. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). 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\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7ASERRV1ES4S7QJRTTYWK0H","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7ASEANH3H547WQBZ7X8W5CX","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.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' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., '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 use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]