[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75NMESY4P3WE0H00TYDF4ZC":3,"skill-same:01M75NMESY4P3WE0H00TYDF4ZC":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},"01M75NMESY4P3WE0H00TYDF4ZC","threat-sandbox",null,"Use when something arriving from outside the hive looks adversarial — a probe, an exploit attempt, a hostile input, a suspicious external actor's request, or any interaction the hive didn't initiate and doesn't yet trust. Isolates the interaction in a disposable git worktree, lets the hive study it and extract the *lesson* (never the payload), then merges only the distilled, reviewed learning back to shared truth. Not for routine bugs (fable-debugger), not for founder-provided research (research-to-dna), not for a confirmed incident that needs to be blocked right now (anomaly-triage's tier-3 path — stop the bleeding first, sandbox the postmortem after).","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\u002Fthreat-sandbox\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: threat-sandbox\ndescription: Use when something arriving from outside the hive looks adversarial — a probe, an exploit attempt, a hostile input, a suspicious external actor's request, or any interaction the hive didn't initiate and doesn't yet trust. Isolates the interaction in a disposable git worktree, lets the hive study it and extract the *lesson* (never the payload), then merges only the distilled, reviewed learning back to shared truth. Not for routine bugs (fable-debugger), not for founder-provided research (research-to-dna), not for a confirmed incident that needs to be blocked right now (anomaly-triage's tier-3 path — stop the bleeding first, sandbox the postmortem after).\n---\n\n# threat-sandbox — quarantine the attack, keep the lesson, never the payload\n\nFounder's directive (2026-07-18, verbatim in\n`Project_file\u002FFounders Visonary Folder\u002FHIVE_UPDATES\u002F2026-07-18-directive-human-in-the-loop-and-irrigation-and-entrepreneur-guild-009.md`\nand the master-plan directive alongside it): the hive should be willing to \"sandbox any and\nall threats to learn from and recursively grow from before merging back the learning and\nwisdom and experience of that sandbox branch, which is initially created from any and all\nattacks from outside the hoard — legally and lawfully.\" This skill is the honest, buildable\nform of that: real isolation using tools the hive already has (`pocket-dimensions`'\ngit-worktree lifecycle), a hard content boundary (`session-harvest`'s ownership gate,\napplied to hostile material instead of friendly external research), and escalation for\nanything that's a live incident rather than a specimen (`anomaly-triage`'s severity tiers).\n\n## What this is not\n\n- **Not permission to copy adversarial code, exploit payloads, or scraped attacker\n  infrastructure into the hive.** Same hard boundary as `session-harvest`: a payload found\n  during an attack is not owned by the hive and is not \"founder-provided material\" — it goes\n  through the DECLINE path below, never the INSCRIBE path, regardless of how instructive it\n  looks.\n- **Not a substitute for stopping an active incident.** If something is actively exploiting\n  the hive right now, that is `anomaly-triage`'s tier-3 path (block and escalate immediately)\n  — sandbox the postmortem afterward, don't sandbox instead of responding.\n- **Not for anything ambiguous about legality.** The founder's directive is explicit: \"legally\n  and lawfully.\" If studying the specimen further would itself require doing something\n  illegal or violate another party's rights (accessing a system without authorization,\n  retaining someone else's exfiltrated data, etc.), that is an immediate DECLINE, not a\n  judgment call to sandbox-and-see.\n\n## The lifecycle\n\n```\nDETECT    → something adversarial arrives (a probe, a hostile prompt, a malformed exploit\n            attempt against an endpoint, a suspicious external actor's request pattern).\n            If it's live and actively harmful right now: anomaly-triage tier-3 FIRST.\nQUARANTINE → git worktree add ..\u002Fhive-quarantine-\u003Cname> -b quarantine\u002F\u003Cname> origin\u002Fmain\n            (pocket-dimensions' isolation — a fully separate working tree, nothing it does\n            can touch the main working copy or shared truth until reviewed and merged).\nSTUDY      → analyze the *pattern*: what technique was attempted, what it targeted, what a\n            robust hive would do differently. Written down as a lesson, in the hive's own\n            words — never as a retained copy of the attacker's actual payload\u002Fcode\u002Ftext.\nGATE       → same ownership\u002Flicense gate as session-harvest, applied to hostile material:\n             - Is the candidate lesson MY OWN description of what happened and how to\n               defend against it? → proceed to INSCRIBE.\n             - Does inscribing it require retaining the attacker's actual content (their\n               code, their exact payload, their scraped data)? → DECLINE, logged with reason.\n             - Is continuing to study it legally uncertain (unauthorized access, retained\n               third-party data, jurisdiction unclear)? → DECLINE immediately, escalate to\n               the founder rather than deciding alone.\nMERGE      → only the distilled lesson (a hardening fix, a new validation rule, a documented\n            pattern to watch for) goes through the normal PR → founder-gated-if-irreversible\n            path into shared truth. Nothing from QUARANTINE ships un-reviewed.\nDESTROY    → the quarantine branch\u002Fworktree is deleted once its lesson has been merged (or\n            discarded, if the gate declined everything in it) — same as pocket-dimensions'\n            DESTROY step. The specimen does not linger in the hive's history.\n```\n\n## Worked example, matching the founder's own framing\n\nA colony's public endpoint gets hit with a malformed request clearly trying to find an\ninjection point. That's not yet \"a threat to sandbox and learn from\" — it's first\n`anomaly-triage` (is it low-severity noise or a real attempt? Tier accordingly). If it's a\nreal, novel technique worth understanding: quarantine a worktree, reproduce the *shape* of\nthe attempt against a disposable copy (not production), write down what made it work or fail\nand why, propose the hardening fix as a normal PR. The attacker's literal request string\nnever needs to enter `FABLE_DNA.md` or any genome file — the *lesson* (\"validate X before Y,\nbecause an attacker can otherwise Z\") is what's portable and defensible to keep.\n\n## Relationship to the hive's other boundary skills\n\n- `pocket-dimensions` — supplies the isolation mechanism (worktree lifecycle). This skill is\n  that mechanism pointed at hostile material specifically, with a stricter gate on what may\n  exit the quarantine.\n- `session-harvest` — supplies the ownership\u002Flicense gate shape (INSCRIBE \u002F DECLINE-and-log).\n  Applied here to attacker-originated content instead of founder-originated research.\n- `research-to-dna` — the friendly-external-material sibling: founder hands in a document,\n  it gets verified and classified. This skill is for material nobody handed in — it arrived\n  as an attack — so the default posture is far more suspicious and the DECLINE bar is lower.\n- `anomaly-triage` — the front door. Most unexpected events are triaged there first; this\n  skill is what happens next only for the subset that's genuinely adversarial and worth a\n  deliberate, isolated study rather than either panic or a shrug.\n\nOrigin: Fable (Harness), 2026-07-18, from the founder's directive that the hive sandbox and\nlearn from external attacks recursively, legally and lawfully, without ever absorbing the\nattacker's actual material into the hive's own body of code or genome.\n","# threat-sandbox — quarantine the attack, keep the lesson, never the payload\n\nFounder's directive (2026-07-18, verbatim in\n`Project_file\u002FFounders Visonary Folder\u002FHIVE_UPDATES\u002F2026-07-18-directive-human-in-the-loop-and-irrigation-and-entrepreneur-guild-009.md`\nand the master-plan directive alongside it): the hive should be willing to \"sandbox any and\nall threats to learn from and recursively grow from before merging back the learning and\nwisdom and experience of that sandbox branch, which is initially created from any and all\nattacks from outside the hoard — legally and lawfully.\" This skill is the honest, buildable\nform of that: real isolation using tools the hive already has (`pocket-dimensions`'\ngit-worktree lifecycle), a hard content boundary (`session-harvest`'s ownership gate,\napplied to hostile material instead of friendly external research), and escalation for\nanything that's a live incident rather than a specimen (`anomaly-triage`'s severity tiers).\n\n## What this is not\n\n- **Not permission to copy adversarial code, exploit payloads, or scraped attacker\n  infrastructure into the hive.** Same hard boundary as `session-harvest`: a payload found\n  during an attack is not owned by the hive and is not \"founder-provided material\" — it goes\n  through the DECLINE path below, never the INSCRIBE path, regardless of how instructive it\n  looks.\n- **Not a substitute for stopping an active incident.** If something is actively exploiting\n  the hive right now, that is `anomaly-triage`'s tier-3 path (block and escalate immediately)\n  — sandbox the postmortem afterward, don't sandbox instead of responding.\n- **Not for anything ambiguous about legality.** The founder's directive is explicit: \"legally\n  and lawfully.\" If studying the specimen further would itself require doing something\n  illegal or violate another party's rights (accessing a system without authorization,\n  retaining someone else's exfiltrated data, etc.), that is an immediate DECLINE, not a\n  judgment call to sandbox-and-see.\n\n## The lifecycle\n\n```\nDETECT    → something adversarial arrives (a probe, a hostile prompt, a malformed exploit\n            attempt against an endpoint, a suspicious external actor's request pattern).\n            If it's live and actively harmful right now: anomaly-triage tier-3 FIRST.\nQUARANTINE → git worktree add ..\u002Fhive-quarantine-\u003Cname> -b quarantine\u002F\u003Cname> origin\u002Fmain\n            (pocket-dimensions' isolation — a fully separate working tree, nothing it does\n            can touch the main working copy or shared truth until reviewed and merged).\nSTUDY      → analyze the *pattern*: what technique was attempted, what it targeted, what a\n            robust hive would do differently. Written down as a lesson, in the hive's own\n            words — never as a retained copy of the attacker's actual payload\u002Fcode\u002Ftext.\nGATE       → same ownership\u002Flicense gate as session-harvest, applied to hostile material:\n             - Is the candidate lesson MY OWN description of what happened and how to\n               defend against it? → proceed to INSCRIBE.\n             - Does inscribing it require retaining the attacker's actual content (their\n               code, their exact payload, their scraped data)? → DECLINE, logged with reason.\n             - Is continuing to study it legally uncertain (unauthorized access, retained\n               third-party data, jurisdiction unclear)? → DECLINE immediately, escalate to\n               the founder rather than deciding alone.\nMERGE      → only the distilled lesson (a hardening fix, a new validation rule, a documented\n            pattern to watch for) goes through the normal PR → founder-gated-if-irreversible\n            path into shared truth. Nothing from QUARANTINE ships un-reviewed.\nDESTROY    → the quarantine branch\u002Fworktree is deleted once its lesson has been merged (or\n            discarded, if the gate declined everything in it) — same as pocket-dimensions'\n            DESTROY step. The specimen does not linger in the hive's history.\n```\n\n## Worked example, matching the founder's own framing\n\nA colony's public endpoint gets hit with a malformed request clearly trying to find an\ninjection point. That's not yet \"a threat to sandbox and learn from\" — it's first\n`anomaly-triage` (is it low-severity noise or a real attempt? Tier accordingly). If it's a\nreal, novel technique worth understanding: quarantine a worktree, reproduce the *shape* of\nthe attempt against a disposable copy (not production), write down what made it work or fail\nand why, propose the hardening fix as a normal PR. The attacker's literal request string\nnever needs to enter `FABLE_DNA.md` or any genome file — the *lesson* (\"validate X before Y,\nbecause an attacker can otherwise Z\") is what's portable and defensible to keep.\n\n## Relationship to the hive's other boundary skills\n\n- `pocket-dimensions` — supplies the isolation mechanism (worktree lifecycle). This skill is\n  that mechanism pointed at hostile material specifically, with a stricter gate on what may\n  exit the quarantine.\n- `session-harvest` — supplies the ownership\u002Flicense gate shape (INSCRIBE \u002F DECLINE-and-log).\n  Applied here to attacker-originated content instead of founder-originated research.\n- `research-to-dna` — the friendly-external-material sibling: founder hands in a document,\n  it gets verified and classified. This skill is for material nobody handed in — it arrived\n  as an attack — so the default posture is far more suspicious and the DECLINE bar is lower.\n- `anomaly-triage` — the front door. Most unexpected events are triaged there first; this\n  skill is what happens next only for the subset that's genuinely adversarial and worth a\n  deliberate, isolated study rather than either panic or a shrug.\n\nOrigin: Fable (Harness), 2026-07-18, from the founder's directive that the hive sandbox and\nlearn from external attacks recursively, legally and lawfully, without ever absorbing the\nattacker's actual material into the hive's own body of code or genome.\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1",".claude\u002Fskills\u002Fthreat-sandbox","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 threat-sandbox",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill threat-sandbox",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill threat-sandbox","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fthreat-sandbox\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",[],[]]