[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75NABEXQRTT86FD257GCG71":3,"skill-same:01M75NABEXQRTT86FD257GCG71":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},"01M75NABEXQRTT86FD257GCG71","dual-lens",null,"The binding gate for architectural and design decisions — runs BOTH hive lenses in the doctrine's own order (devils-advocate interrogates what could break, then childlike-wonder expands what it could become) and refuses to pass a decision reviewed by only one. Use before committing to any structural choice: a new subsystem, a schema change, an agent or capability, a change to how the hive governs or spends, or any founder proposal being evaluated. When the subject is source material — a document, external research, a founder- shared PDF — rather than the hive's own design, a third stage (fabrication-mining) runs after the first two whenever devils-advocate found something false along the way; skip it when there is no discard pile to mine. Explicitly NOT for routine bug fixes, verification passes, or mechanical work where the answer is known and just needs doing — running both lenses on a typo is pure overhead. This is the enforcement wrapper for memory\u002Fphilosophy\u002Fdual-lens-framework.md, which declared both lenses non-negotiable and had no mechanism behind it.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdual-lens\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: dual-lens\ndescription: >\n  The binding gate for architectural and design decisions — runs BOTH hive lenses in the\n  doctrine's own order (devils-advocate interrogates what could break, then childlike-wonder\n  expands what it could become) and refuses to pass a decision reviewed by only one. Use\n  before committing to any structural choice: a new subsystem, a schema change, an agent or\n  capability, a change to how the hive governs or spends, or any founder proposal being\n  evaluated. When the subject is source material — a document, external research, a founder-\n  shared PDF — rather than the hive's own design, a third stage (fabrication-mining) runs\n  after the first two whenever devils-advocate found something false along the way; skip it\n  when there is no discard pile to mine. Explicitly NOT for routine bug fixes, verification\n  passes, or mechanical work where the answer is known and just needs doing — running both\n  lenses on a typo is pure overhead. This is the enforcement wrapper for\n  memory\u002Fphilosophy\u002Fdual-lens-framework.md, which declared both lenses non-negotiable and had\n  no mechanism behind it.\n---\n\n# dual-lens — neither lens is optional\n\n## The doctrine this enforces\n\n`memory\u002Fphilosophy\u002Fdual-lens-framework.md`, verbatim:\n\n> *\"Every architectural choice passes through both lenses before implementation:\n> **devils-advocate** — interrogates what we've built (risk, failure, attack surface);\n> **childlike-wonder** — asks what it could become (possibility, emergence, delight).\n> Neither lens is optional. A decision made with only one lens is incomplete.\"*\n\n**That was true on paper and false in practice.** `devils-advocate-audit` existed as a real\nskill; `childlike-wonder` did not exist at all until 2026-08-07. Every decision made \"under\nthe framework\" before then was single-lens by construction. This skill is the gate that was\nmissing.\n\n## Order matters — interrogate first, then expand\n\nThe doctrine specifies it, and the reason is real: **wonder applied before criticism\nproduces advocacy, not design.** Once you have described how wonderful something could be,\nyou are motivated to find its risks survivable. Reversing the order is the single most\ncommon way this gate gets quietly defeated.\n\n### Stage 1 — Devil's advocate: what could break?\n\nFull method: `devils-advocate-audit`. Minimum for this gate:\n- What fails, and what does that failure cost?\n- What does this let someone (or some agent) do that they should not?\n- What does it couple that was previously independent?\n- What claim does it make that is not yet evidenced (`wired-or-not`)?\n\n### Stage 2 — Childlike wonder: what could it become?\n\nFull method: `childlike-wonder`. Minimum for this gate:\n- If it worked perfectly, what becomes possible that could not before?\n- What named constraint, if removed, changes the answer?\n- What cross-domain connection is invisible from inside this problem?\n\n### Stage 3 — Fabrication-mining: conditional, source material only\n\n**Runs only when the subject under review is source material** — a document, a founder-shared\nPDF, external research, a proposal built from outside claims — **not** when it is one of the\nhive's own design decisions. A new subsystem or schema change has no discard pile to mine;\nforcing this stage onto routine architectural decisions is exactly the kind of theatre \"Don't\"\nbelow warns against.\n\n**Trigger condition:** Stage 1 found one or more claims in the source material that are false,\nfabricated, or unverifiable — not merely risky, actually false. If Stage 1 found the material\nentirely sound, or found risks in a genuine design rather than falsehoods in a document, this\nstage does not run — say so, rather than forcing a mining pass with nothing to mine.\n\nWhen triggered: run `fabrication-mining` on each false claim Stage 1 identified. That skill's\nfive-verdict method (`POINTS-AT-A-REAL-GAP` \u002F `INDEPENDENT-REDERIVATION` \u002F `LIVE-FIXTURE` \u002F\n`MIRROR` \u002F `NO-SIGNAL`) produces what Stage 1 alone cannot: not just \"this is false,\" but what\nthe falsehood was reaching for, checked against what the hive actually has. See\n`fabrication-mining\u002FSKILL.md` for the full method — it is not reproduced here.\n\n**Worked example:** `VISION\u002F2026-08-08-vision-arithmancer-thermodynamics-audit-010.md`\n(Stages 1–2, source-material decisions) and\n`VISION\u002F2026-08-08-vision-arithmancer-full-dissection-011.md` (Stage 3, added after the\nfounder's own correction that a fabrication-only-discarded pass had missed the actual ask).\n\n### The verdict\n\nEvery lens that ran reports. **None cancels another.** A real risk is not erased by a\nbeautiful possibility, a real possibility is not erased by a manageable risk, and a mined\nfinding from Stage 3 does not soften a risk Stage 1 found — `fabrication-mining`'s own hard\nboundary says the same thing from the other direction. Say what each found, then state the\ndecision and which lens it favours and why.\n\n## The refusal — the actual gate\n\n**A decision reviewed by only one lens does not pass.** If only one has run, the honest\noutput is *\"single-lens, incomplete\"* plus what the missing lens still needs to answer —\nnever a verdict dressed as complete.\n\nThis includes the tempting cases:\n- The risk is obvious and severe → **still run wonder.** It often reveals that the valuable\n  part can be kept while the dangerous part is dropped.\n- The idea is obviously good → **still run devils-advocate.** This is where the expensive\n  mistakes live.\n- Time is short → then say the gate was skipped. **Skipping it and not saying so is the one\n  outcome this skill exists to prevent.**\n\n## Do\n\n- Run this on **founder proposals too**, not only on your own designs. A founder idea\n  deserves both lenses — that is respect, not obstruction. `MANDATE_TRIAGE.md` already says\n  nothing gets rubber-stamped.\n- Check **resonance** before batching decisions together\n  (`memory\u002Fphilosophy\u002Fresonance-interference.md`): two decisions that cancel each other must\n  be sequenced, not merged.\n- Name what you **could not evaluate** and why.\n\n## Don't\n\n- **Don't run wonder first.** See above.\n- **Don't let either lens become theatre** — a risk section listing generic risks nobody\n  will act on, or a wonder section listing everything imaginable, both defeat the gate while\n  appearing to satisfy it.\n- **Don't treat the verdict as permission.** Anything irreversible or founder-gated stays\n  gated regardless of how well it passed.\n- **Don't invent Codex mythology** in the wonder pass (`FABLE_DNA.md` Chromosome V).\n\n## Honest limits — stated because this repo has a history\n\n**This gate is procedural. Nothing machine-enforces it.** No CI check can detect a decision\nthat skipped a lens.\n\nThat matters here specifically: a founder-ordered audit (2026-08-07) found 34 of 36 `done`\ntasks never verified against production, and the root cause was doctrine with no mechanism —\nwhich is exactly what `dual-lens-framework.md` was. Writing a skill about it improves the\nodds; it does not make it enforced. **Anyone reading this should assume it can be skipped,\nand treat \"did both lenses actually run?\" as a live question rather than a settled one.**\n\nThe one durable artifact: when a decision passes this gate, **write both lenses' findings\ninto the plan or task record**, not just the verdict. Findings in a file survive a context\ncutoff; findings in a session's head do not.\n\n## Links\n\n`devils-advocate-audit` · `childlike-wonder` · `fabrication-mining` (conditional Stage 3, source\nmaterial only) · `wired-or-not` (claim levels) ·\n`hive-conductor` (invokes this gate when routing decisions) ·\n`memory\u002Fphilosophy\u002Fdual-lens-framework.md` (source doctrine) ·\n`memory\u002Fphilosophy\u002Fresonance-interference.md`\n","# dual-lens — neither lens is optional\n\n## The doctrine this enforces\n\n`memory\u002Fphilosophy\u002Fdual-lens-framework.md`, verbatim:\n\n> *\"Every architectural choice passes through both lenses before implementation:\n> **devils-advocate** — interrogates what we've built (risk, failure, attack surface);\n> **childlike-wonder** — asks what it could become (possibility, emergence, delight).\n> Neither lens is optional. A decision made with only one lens is incomplete.\"*\n\n**That was true on paper and false in practice.** `devils-advocate-audit` existed as a real\nskill; `childlike-wonder` did not exist at all until 2026-08-07. Every decision made \"under\nthe framework\" before then was single-lens by construction. This skill is the gate that was\nmissing.\n\n## Order matters — interrogate first, then expand\n\nThe doctrine specifies it, and the reason is real: **wonder applied before criticism\nproduces advocacy, not design.** Once you have described how wonderful something could be,\nyou are motivated to find its risks survivable. Reversing the order is the single most\ncommon way this gate gets quietly defeated.\n\n### Stage 1 — Devil's advocate: what could break?\n\nFull method: `devils-advocate-audit`. Minimum for this gate:\n- What fails, and what does that failure cost?\n- What does this let someone (or some agent) do that they should not?\n- What does it couple that was previously independent?\n- What claim does it make that is not yet evidenced (`wired-or-not`)?\n\n### Stage 2 — Childlike wonder: what could it become?\n\nFull method: `childlike-wonder`. Minimum for this gate:\n- If it worked perfectly, what becomes possible that could not before?\n- What named constraint, if removed, changes the answer?\n- What cross-domain connection is invisible from inside this problem?\n\n### Stage 3 — Fabrication-mining: conditional, source material only\n\n**Runs only when the subject under review is source material** — a document, a founder-shared\nPDF, external research, a proposal built from outside claims — **not** when it is one of the\nhive's own design decisions. A new subsystem or schema change has no discard pile to mine;\nforcing this stage onto routine architectural decisions is exactly the kind of theatre \"Don't\"\nbelow warns against.\n\n**Trigger condition:** Stage 1 found one or more claims in the source material that are false,\nfabricated, or unverifiable — not merely risky, actually false. If Stage 1 found the material\nentirely sound, or found risks in a genuine design rather than falsehoods in a document, this\nstage does not run — say so, rather than forcing a mining pass with nothing to mine.\n\nWhen triggered: run `fabrication-mining` on each false claim Stage 1 identified. That skill's\nfive-verdict method (`POINTS-AT-A-REAL-GAP` \u002F `INDEPENDENT-REDERIVATION` \u002F `LIVE-FIXTURE` \u002F\n`MIRROR` \u002F `NO-SIGNAL`) produces what Stage 1 alone cannot: not just \"this is false,\" but what\nthe falsehood was reaching for, checked against what the hive actually has. See\n`fabrication-mining\u002FSKILL.md` for the full method — it is not reproduced here.\n\n**Worked example:** `VISION\u002F2026-08-08-vision-arithmancer-thermodynamics-audit-010.md`\n(Stages 1–2, source-material decisions) and\n`VISION\u002F2026-08-08-vision-arithmancer-full-dissection-011.md` (Stage 3, added after the\nfounder's own correction that a fabrication-only-discarded pass had missed the actual ask).\n\n### The verdict\n\nEvery lens that ran reports. **None cancels another.** A real risk is not erased by a\nbeautiful possibility, a real possibility is not erased by a manageable risk, and a mined\nfinding from Stage 3 does not soften a risk Stage 1 found — `fabrication-mining`'s own hard\nboundary says the same thing from the other direction. Say what each found, then state the\ndecision and which lens it favours and why.\n\n## The refusal — the actual gate\n\n**A decision reviewed by only one lens does not pass.** If only one has run, the honest\noutput is *\"single-lens, incomplete\"* plus what the missing lens still needs to answer —\nnever a verdict dressed as complete.\n\nThis includes the tempting cases:\n- The risk is obvious and severe → **still run wonder.** It often reveals that the valuable\n  part can be kept while the dangerous part is dropped.\n- The idea is obviously good → **still run devils-advocate.** This is where the expensive\n  mistakes live.\n- Time is short → then say the gate was skipped. **Skipping it and not saying so is the one\n  outcome this skill exists to prevent.**\n\n## Do\n\n- Run this on **founder proposals too**, not only on your own designs. A founder idea\n  deserves both lenses — that is respect, not obstruction. `MANDATE_TRIAGE.md` already says\n  nothing gets rubber-stamped.\n- Check **resonance** before batching decisions together\n  (`memory\u002Fphilosophy\u002Fresonance-interference.md`): two decisions that cancel each other must\n  be sequenced, not merged.\n- Name what you **could not evaluate** and why.\n\n## Don't\n\n- **Don't run wonder first.** See above.\n- **Don't let either lens become theatre** — a risk section listing generic risks nobody\n  will act on, or a wonder section listing everything imaginable, both defeat the gate while\n  appearing to satisfy it.\n- **Don't treat the verdict as permission.** Anything irreversible or founder-gated stays\n  gated regardless of how well it passed.\n- **Don't invent Codex mythology** in the wonder pass (`FABLE_DNA.md` Chromosome V).\n\n## Honest limits — stated because this repo has a history\n\n**This gate is procedural. Nothing machine-enforces it.** No CI check can detect a decision\nthat skipped a lens.\n\nThat matters here specifically: a founder-ordered audit (2026-08-07) found 34 of 36 `done`\ntasks never verified against production, and the root cause was doctrine with no mechanism —\nwhich is exactly what `dual-lens-framework.md` was. Writing a skill about it improves the\nodds; it does not make it enforced. **Anyone reading this should assume it can be skipped,\nand treat \"did both lenses actually run?\" as a live question rather than a settled one.**\n\nThe one durable artifact: when a decision passes this gate, **write both lenses' findings\ninto the plan or task record**, not just the verdict. Findings in a file survive a context\ncutoff; findings in a session's head do not.\n\n## Links\n\n`devils-advocate-audit` · `childlike-wonder` · `fabrication-mining` (conditional Stage 3, source\nmaterial only) · `wired-or-not` (claim levels) ·\n`hive-conductor` (invokes this gate when routing decisions) ·\n`memory\u002Fphilosophy\u002Fdual-lens-framework.md` (source doctrine) ·\n`memory\u002Fphilosophy\u002Fresonance-interference.md`\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1",".claude\u002Fskills\u002Fdual-lens","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 dual-lens",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill dual-lens",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill dual-lens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdual-lens\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",[],[]]