[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75NF5NA866CCJ09894JSY8C":3,"skill-same:01M75NF5NA866CCJ09894JSY8C":52},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":14,"categories":15,"keywords":16,"publishedAt":17,"linkOnly":18,"markdownContent":19,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":12,"repositoryHtmlUrl":25,"repositoryHomepageUrl":6,"ownerHtmlUrl":26,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":27,"install":28,"resources":41},"01M75NF5NA866CCJ09894JSY8C","recursive-growth",null,"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\u002Frecursive-growth\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: recursive-growth\ndescription: Invoke at the very start of every session, before planning anything — it reads the current master plan (memory\u002Fplanning\u002F2026-07-19-unified-forward-plan.md) so work picks up exactly where the last session left off, phase by phase. It also runs alongside fable-debugger: every verified fix gets folded back in as a lesson (LESSONS.md), and once a lesson genuinely recurs (not on a single occurrence) it gets promoted into this skill's own Recurring Patterns section — the skill grows itself. Separately, after any skill runs, it does one light pass over that skill's own files for a small, honest, logged correction (a stale example, a broken path, a fact the run just disproved) — never a rewrite, never touching a documented hard boundary. Not a replacement for hive-conductor's memory-RECALL (that queries the D1\u002FVectorize sovereign-memory backend) — this is the literal, always-available, no-network-required sibling: the plan file and the skill files themselves are the memory here.\n---\n\n# recursive-growth — session-start recall, and a skill that keeps correcting itself\n\nThree founder directives, one skill: (1) every session should be pointed straight at the\nmaster plan, not left to re-derive \"what's next\"; (2) whatever `fable-debugger` learns from\na real bug should make the hive smarter next time, not evaporate at session's end; (3) skills\nthemselves should get corrected, in their own files, as their own use turns up something\nstale — not just accumulate lessons in a side log nobody rereads.\n\n## Part 1 — Session-start recall (run this first, every session)\n\n```bash\ncat memory\u002Fplanning\u002FCLAUDE.md   # confirms the current pointer\ncat memory\u002Fplanning\u002F2026-07-19-unified-forward-plan.md   # the actual plan\n```\n\nReport back plainly, before doing anything else: which phase is next (per the plan's own\n\"Phase 0\" → \"Phase 7\" ordering), what's already closed, and what's explicitly founder-blocked\n(Phase 5 — never scheduled as a task, only tracked). This is the same discipline\n`hive-conductor`'s Phase 0 RECALL already applies to sovereign D1\u002FVectorize memory\n(`scripts\u002Frecall_context.py`) — this skill is that same idea pointed at the one committed\nplan file instead of a network-backed index, so it works even with zero egress, and it names\nthe concrete next phase rather than a fuzzy \"prior related work\" brief. Run both; they answer\ndifferent questions (RECALL: \"has the hive done something like this before anywhere in its\nhistory?\" — this skill: \"where exactly are we in the one plan we already agreed to?\").\n\nIf `memory\u002Fplanning\u002FCLAUDE.md`'s pointer and the Founders Visionary Folder's own pointer\n(`Project_file\u002FFounders Visonary Folder\u002FACTIVE\u002F2026-07-19-current-master-plan-pointer.md`)\never disagree about which file is current, that disagreement is itself the thing to fix\nfirst — the two lineages pointing at two different plans is exactly the reconciliation gap\nthis plan's own Phase 1c exists to close. Don't silently pick one; say so and fix the stale\npointer.\n\n## Part 2 — Growing from fable-debugger (recursive learning from bugs)\n\nEvery time `fable-debugger`'s loop reaches step 6\u002F7 (VERIFY-REAL, then CLOSE — a fix that\nactually proved itself against a real check, not an escalation) do two things:\n\n1. **Always**: append one entry to `LESSONS.md` in this skill's own directory — symptom,\n   root cause (one sentence, per fable-debugger's own step 3 discipline), the fix, and the\n   verification command that proved it. This is the raw, unfiltered log — append-only, never\n   pruned, never summarized away. Every entry should be real (a fix that actually shipped),\n   never a hypothetical \"here's a bug that could happen.\"\n2. **Only on genuine recurrence** (the same root-cause *shape* appears a second time,\n   possibly in a different file): promote it into this file's own **Recurring Patterns**\n   section below, generalized past the specific file\u002Fsymptom into the reusable lesson. This\n   is the actual \"recursively builds and grows\" mechanic — the skill's own body of knowledge\n   gets denser over time, but only with things that proved themselves twice, not every\n   one-off. A skill that grew by appending every single bug would become noise nobody reads;\n   a skill that only grows on real recurrence stays worth reading years in.\n\n### Recurring Patterns (empty until a lesson genuinely recurs — do not seed this with\nguesses; the first entries here should be real, already-observed repeats)\n\n*(none yet — see `LESSONS.md` for the raw log this section promotes from)*\n\n## Part 3 — Optimizing other skills' own files, after they run\n\nAfter any skill in `.claude\u002Fskills\u002F` completes a real run (not a dry read), do one light\npass, bounded by hard rules:\n\n1. **What counts as an optimization**: a stale example that no longer matches the repo (a\n   renamed file, a moved endpoint), a broken script path, a described behavior the run just\n   proved wrong or incomplete, a missing cross-reference to a skill that's clearly relevant\n   (the way this section itself should have existed the first time `fable-debugger` and\n   `hive-conductor` were written — see the changelog entries this skill added to both on\n   2026-07-19, the first real proof of this mechanic, not just a description of it).\n2. **What never counts**: rewriting a skill's core contract, loosening a documented hard\n   boundary (`threat-sandbox`'s \"never absorb the payload,\" `session-harvest`'s\n   ownership\u002Flicense gate, any `PERMISSIONS.md` tier boundary, `agent-harness`'s\n   never-adjudicate-your-own-verification rule), or any edit that isn't traceable to\n   something this run actually observed. When in doubt, don't edit — log it in `LESSONS.md`\n   as a candidate instead and let it recur before acting.\n3. **Every edit is small and logged**: one paragraph or one line changed, a one-line entry\n   appended to `SKILL_CHANGELOG.md` in this directory naming which skill, what changed, and\n   why (the observed evidence), and committed normally — never silent, uncommitted drift.\n   This is Tier 1 under `PERMISSIONS.md` (internal, reversible via git, no external party, no\n   money) — but the changelog is what keeps it honest under F-004 (explainability): anyone\n   can `git log`\u002F`git blame` a skill file and find the reason a line changed.\n4. **This skill is not exempt from itself**: when running `recursive-growth` itself turns up\n   something stale in this very file (a broken path, a Recurring Pattern that turns out\n   wrong), the same rule applies — small edit, changelog entry, no silent rewrite.\n\n## Relationship to the hive's other memory\u002Fgrowth mechanisms (so nothing here duplicates them)\n\n- **`hive-conductor`'s Phase 0 RECALL** — queries sovereign D1\u002FVectorize memory for \"has the\n  hive done something like this before, anywhere.\" Network-dependent, degrades gracefully.\n  This skill is its local, always-on sibling, scoped to one committed plan file.\n- **`fable-debugger`** — the method that produces the lessons this skill grows from. This\n  skill doesn't debug; it remembers what debugging taught, and corrects the skills involved.\n- **`pr-retrospective` \u002F `PR_LESSONS.md`** — PR-outcome-specific forward checks (what to\n  watch for on the *next* PR touching a risky surface). This skill's `LESSONS.md` is broader\n  (any verified fable-debugger fix, not just PR-shaped ones) and feeds skill-file corrections,\n  not just a pre-flight checklist.\n- **`session-harvest`** — distills a whole session's work into `HIVE_UPDATES\u002F` at close,\n  under an ownership\u002Flicense gate. This skill runs continuously *within* a session (every\n  fable-debugger close, every skill run), and writes to skill files and the lessons log, not\n  to the founder-facing updates channel.\n- **`skill-census`** — audits whether skills are wired\u002Forphaned, periodically. This skill is\n  what keeps a skill's *content* accurate between census runs, not what discovers whether a\n  skill is used at all.\n\n## Quick start\n\n```bash\n# 0. Session start — read the plan, report the next phase, before anything else:\ncat memory\u002Fplanning\u002FCLAUDE.md\ncat memory\u002Fplanning\u002F2026-07-19-unified-forward-plan.md\n\n# 1. After a fable-debugger close — append the raw lesson:\n#    (edit .claude\u002Fskills\u002Frecursive-growth\u002FLESSONS.md — symptom \u002F root cause \u002F fix \u002F verification)\n\n# 2. If that lesson's shape has appeared before — promote it into this file's\n#    \"Recurring Patterns\" section, generalized past the one instance.\n\n# 3. After any skill runs — if something in ITS OWN files is now stale, make one small,\n#    logged edit and append one line to SKILL_CHANGELOG.md naming what\u002Fwhy.\n```\n\nOrigin: founder directive, 2026-07-19 — \"refer directly to this plan at the beginning of\neach session,\" \"recursively builds and grows... any time fable 5 debugger is r[u]n,\"\n\"learn recursively from any and all the bugs,\" \"fully optimize any other skill... directly\ninto their file[s].\" Built the same way every other skill here was: a real, repeatable\nmethod, written down so any session can run it — not a promise, a discipline.\n","# recursive-growth — session-start recall, and a skill that keeps correcting itself\n\nThree founder directives, one skill: (1) every session should be pointed straight at the\nmaster plan, not left to re-derive \"what's next\"; (2) whatever `fable-debugger` learns from\na real bug should make the hive smarter next time, not evaporate at session's end; (3) skills\nthemselves should get corrected, in their own files, as their own use turns up something\nstale — not just accumulate lessons in a side log nobody rereads.\n\n## Part 1 — Session-start recall (run this first, every session)\n\n```bash\ncat memory\u002Fplanning\u002FCLAUDE.md   # confirms the current pointer\ncat memory\u002Fplanning\u002F2026-07-19-unified-forward-plan.md   # the actual plan\n```\n\nReport back plainly, before doing anything else: which phase is next (per the plan's own\n\"Phase 0\" → \"Phase 7\" ordering), what's already closed, and what's explicitly founder-blocked\n(Phase 5 — never scheduled as a task, only tracked). This is the same discipline\n`hive-conductor`'s Phase 0 RECALL already applies to sovereign D1\u002FVectorize memory\n(`scripts\u002Frecall_context.py`) — this skill is that same idea pointed at the one committed\nplan file instead of a network-backed index, so it works even with zero egress, and it names\nthe concrete next phase rather than a fuzzy \"prior related work\" brief. Run both; they answer\ndifferent questions (RECALL: \"has the hive done something like this before anywhere in its\nhistory?\" — this skill: \"where exactly are we in the one plan we already agreed to?\").\n\nIf `memory\u002Fplanning\u002FCLAUDE.md`'s pointer and the Founders Visionary Folder's own pointer\n(`Project_file\u002FFounders Visonary Folder\u002FACTIVE\u002F2026-07-19-current-master-plan-pointer.md`)\never disagree about which file is current, that disagreement is itself the thing to fix\nfirst — the two lineages pointing at two different plans is exactly the reconciliation gap\nthis plan's own Phase 1c exists to close. Don't silently pick one; say so and fix the stale\npointer.\n\n## Part 2 — Growing from fable-debugger (recursive learning from bugs)\n\nEvery time `fable-debugger`'s loop reaches step 6\u002F7 (VERIFY-REAL, then CLOSE — a fix that\nactually proved itself against a real check, not an escalation) do two things:\n\n1. **Always**: append one entry to `LESSONS.md` in this skill's own directory — symptom,\n   root cause (one sentence, per fable-debugger's own step 3 discipline), the fix, and the\n   verification command that proved it. This is the raw, unfiltered log — append-only, never\n   pruned, never summarized away. Every entry should be real (a fix that actually shipped),\n   never a hypothetical \"here's a bug that could happen.\"\n2. **Only on genuine recurrence** (the same root-cause *shape* appears a second time,\n   possibly in a different file): promote it into this file's own **Recurring Patterns**\n   section below, generalized past the specific file\u002Fsymptom into the reusable lesson. This\n   is the actual \"recursively builds and grows\" mechanic — the skill's own body of knowledge\n   gets denser over time, but only with things that proved themselves twice, not every\n   one-off. A skill that grew by appending every single bug would become noise nobody reads;\n   a skill that only grows on real recurrence stays worth reading years in.\n\n### Recurring Patterns (empty until a lesson genuinely recurs — do not seed this with\nguesses; the first entries here should be real, already-observed repeats)\n\n*(none yet — see `LESSONS.md` for the raw log this section promotes from)*\n\n## Part 3 — Optimizing other skills' own files, after they run\n\nAfter any skill in `.claude\u002Fskills\u002F` completes a real run (not a dry read), do one light\npass, bounded by hard rules:\n\n1. **What counts as an optimization**: a stale example that no longer matches the repo (a\n   renamed file, a moved endpoint), a broken script path, a described behavior the run just\n   proved wrong or incomplete, a missing cross-reference to a skill that's clearly relevant\n   (the way this section itself should have existed the first time `fable-debugger` and\n   `hive-conductor` were written — see the changelog entries this skill added to both on\n   2026-07-19, the first real proof of this mechanic, not just a description of it).\n2. **What never counts**: rewriting a skill's core contract, loosening a documented hard\n   boundary (`threat-sandbox`'s \"never absorb the payload,\" `session-harvest`'s\n   ownership\u002Flicense gate, any `PERMISSIONS.md` tier boundary, `agent-harness`'s\n   never-adjudicate-your-own-verification rule), or any edit that isn't traceable to\n   something this run actually observed. When in doubt, don't edit — log it in `LESSONS.md`\n   as a candidate instead and let it recur before acting.\n3. **Every edit is small and logged**: one paragraph or one line changed, a one-line entry\n   appended to `SKILL_CHANGELOG.md` in this directory naming which skill, what changed, and\n   why (the observed evidence), and committed normally — never silent, uncommitted drift.\n   This is Tier 1 under `PERMISSIONS.md` (internal, reversible via git, no external party, no\n   money) — but the changelog is what keeps it honest under F-004 (explainability): anyone\n   can `git log`\u002F`git blame` a skill file and find the reason a line changed.\n4. **This skill is not exempt from itself**: when running `recursive-growth` itself turns up\n   something stale in this very file (a broken path, a Recurring Pattern that turns out\n   wrong), the same rule applies — small edit, changelog entry, no silent rewrite.\n\n## Relationship to the hive's other memory\u002Fgrowth mechanisms (so nothing here duplicates them)\n\n- **`hive-conductor`'s Phase 0 RECALL** — queries sovereign D1\u002FVectorize memory for \"has the\n  hive done something like this before, anywhere.\" Network-dependent, degrades gracefully.\n  This skill is its local, always-on sibling, scoped to one committed plan file.\n- **`fable-debugger`** — the method that produces the lessons this skill grows from. This\n  skill doesn't debug; it remembers what debugging taught, and corrects the skills involved.\n- **`pr-retrospective` \u002F `PR_LESSONS.md`** — PR-outcome-specific forward checks (what to\n  watch for on the *next* PR touching a risky surface). This skill's `LESSONS.md` is broader\n  (any verified fable-debugger fix, not just PR-shaped ones) and feeds skill-file corrections,\n  not just a pre-flight checklist.\n- **`session-harvest`** — distills a whole session's work into `HIVE_UPDATES\u002F` at close,\n  under an ownership\u002Flicense gate. This skill runs continuously *within* a session (every\n  fable-debugger close, every skill run), and writes to skill files and the lessons log, not\n  to the founder-facing updates channel.\n- **`skill-census`** — audits whether skills are wired\u002Forphaned, periodically. This skill is\n  what keeps a skill's *content* accurate between census runs, not what discovers whether a\n  skill is used at all.\n\n## Quick start\n\n```bash\n# 0. Session start — read the plan, report the next phase, before anything else:\ncat memory\u002Fplanning\u002FCLAUDE.md\ncat memory\u002Fplanning\u002F2026-07-19-unified-forward-plan.md\n\n# 1. After a fable-debugger close — append the raw lesson:\n#    (edit .claude\u002Fskills\u002Frecursive-growth\u002FLESSONS.md — symptom \u002F root cause \u002F fix \u002F verification)\n\n# 2. If that lesson's shape has appeared before — promote it into this file's\n#    \"Recurring Patterns\" section, generalized past the one instance.\n\n# 3. After any skill runs — if something in ITS OWN files is now stale, make one small,\n#    logged edit and append one line to SKILL_CHANGELOG.md naming what\u002Fwhy.\n```\n\nOrigin: founder directive, 2026-07-19 — \"refer directly to this plan at the beginning of\neach session,\" \"recursively builds and grows... any time fable 5 debugger is r[u]n,\"\n\"learn recursively from any and all the bugs,\" \"fully optimize any other skill... directly\ninto their file[s].\" Built the same way every other skill here was: a real, repeatable\nmethod, written down so any session can run it — not a promise, a discipline.\n",{},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1",".claude\u002Fskills\u002Frecursive-growth","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":7,"skillName":5,"commands":29,"prompt":39,"zipAvailable":40},[30,33,36],{"tool":31,"command":32},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill recursive-growth",{"tool":34,"command":35},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill recursive-growth",{"tool":37,"command":38},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill recursive-growth","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frecursive-growth\u002FSKILL.md",true,[42,48],{"path":43,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":46,"sourceHtmlUrl":47},"LESSONS.md","REFERENCE","参考文档",781,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frecursive-growth\u002FLESSONS.md",{"path":49,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":50,"sourceHtmlUrl":51},"SKILL_CHANGELOG.md",1007,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frecursive-growth\u002FSKILL_CHANGELOG.md",[53,60,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":17},"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":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":17},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":17},"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":17},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":17},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":17},"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",[],[]]