[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PW0TMDPX6SP0SH37PAFDS":3,"skill-same:01M75PW0TMDPX6SP0SH37PAFDS":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M75PW0TMDPX6SP0SH37PAFDS","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.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fcompliance-os\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 ra-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 ra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Ffda_submission_tracker.py submissions.json\n\n# 3. HIPAA overlap (if connected device handles PHI)\npython ra-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 ra-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 ra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Ffda_submission_tracker.py submissions.json\n\n# 3. HIPAA overlap (if connected device handles PHI)\npython ra-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","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fcompliance-os\u002Fskills\u002Ffda-qsr-audit-prep","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill fda-qsr-audit-prep",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill fda-qsr-audit-prep",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill fda-qsr-audit-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fcompliance-os\u002Fskills\u002Ffda-qsr-audit-prep\u002FSKILL.md",true,[],[44,51,57,64,71,78],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","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\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75RAG1XMCJMF30HFV5S79AK","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\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75RA8RK2JVWB8MYGRB65V75","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\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75RA08RXYRFSTNC6EEEX4ZD","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\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]