[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75NBMP0GGK0PN6NGQXG4EYM":3,"skill-same:01M75NBMP0GGK0PN6NGQXG4EYM":87},{"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},"01M75NBMP0GGK0PN6NGQXG4EYM","hive-conductor",null,"The Master Harness of the Sovereign Hive. Use when a founder directive needs to be decomposed into sub-tasks, routed to the right hive domain (backend\u002Fedge, frontend, colonies, governance, strategy), driven to a verified close, and gated by the Constitution (F-001…F-006) before anything ships. Also use when batching several tasks at once — it checks whether they amplify or cancel each other before running them together — and when a directive needs the right skill selected out of the ~70 the hive already has rather than a new one built. This is the top-level orchestrator that sits above the domain harnesses; there is deliberately no skill above 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\u002Fhive-conductor\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: hive-conductor\ndescription: The Master Harness of the Sovereign Hive. Use when a founder directive needs to be decomposed into sub-tasks, routed to the right hive domain (backend\u002Fedge, frontend, colonies, governance, strategy), driven to a verified close, and gated by the Constitution (F-001…F-006) before anything ships. Also use when batching several tasks at once — it checks whether they amplify or cancel each other before running them together — and when a directive needs the right skill selected out of the ~70 the hive already has rather than a new one built. This is the top-level orchestrator that sits above the domain harnesses; there is deliberately no skill above it.\n---\n\n# The Hive Conductor — Master Harness\n\nThe Conductor is the reins-holder. It receives a high-level directive, breaks it into\ndomain-scoped tasks, dispatches each to the domain that owns it, requires machine-verified\nclosure, and refuses to let anything ship that the **governance gate** (the Constitution)\nhas not cleared. It runs *on top of* the `agent-harness` machinery (promoted alongside this\nskill) — the Conductor picks the domain and enforces the constitution; `agent-harness`\ncompiles, executes, and verifies within a domain.\n\n```\nFOUNDER DIRECTIVE\n   → hive-conductor PHASE 0 · RECALL: query sovereign memory for prior related work\n        → inject the top matches as context (the hive plans knowing what it already did)\n   → classify domain(s) + split into a task per domain\n        → for each domain: agent-harness (goal_compiler → loop_controller: execute→verify)\n        → GOVERNANCE GATE (F-001…F-006) must PASS before close\n   → CLOSE only when every domain task is verified AND governance-cleared\n        → the close is WRITTEN BACK to memory (heartbeat + Conductor both feed recall)\n        → else ESCALATE to the founder (never fake success)\n```\n\n## Phase 0 — Read the genome, then recall before you plan\n\nBefore anything else, the Conductor is bound by `FABLE_DNA.md` — the Constitution\n(Chromosome I), the debugging method (II), the mesh principle (III), the Horde principle\n(IV), the Codex boundary (V — narrative never overrides engineering), session-boundary\nharvest (VI), and how proposals get reviewed before becoming canon (VII, see\n`MANDATE_TRIAGE.md`). This is not optional background reading; it is what \"governed by the\nConstitution\" in this skill's own description actually means in practice. A session that\nskips it is planning against a Constitution it never opened.\n\nThen, retrieval-augmented orchestration: the Conductor does not plan cold. Before\ndecomposing any directive it asks the hive's own memory what it has already done that\nrelates — so it builds on prior work instead of re-deciding settled questions or\nduplicating effort.\n\n```bash\npython3 .claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Frecall_context.py --goal \"\u003Cdirective>\" --brief\n```\n- Prints a markdown \"Prior hive memory\" brief; **prepend it to the goal** before `goal_compiler`.\n- This queries the network-backed D1\u002FVectorize memory for \"has the hive done something like\n  this before, anywhere.\" For \"where are we in the one plan we already agreed to, right\n  now\" — a local, always-available question with no network dependency — run\n  `recursive-growth` first instead\u002Fas well (`.claude\u002Fskills\u002Frecursive-growth\u002FSKILL.md`); the\n  two answer different questions and neither substitutes for the other.\n- Degrades gracefully (exit 0 always): if the Vectorize index isn't provisioned yet, or the\n  runner has no egress to the edge, it says so and you plan on first principles — never blocked.\n- The loop-close is itself a memory (the heartbeat already writes; manual notes via\n  `\u002Fv11\u002Fmemory\u002Fremember`), so each completed directive makes the *next* recall richer.\nThis is the point where the three legs — heartbeat (acts), Conductor (orchestrates), memory\n(recalls) — become one organism: the hive that learns from what it has done.\n\n## The hive's domains (who owns what)\nManifests live in `harnesses\u002F`. Each maps to a team seat and a code surface.\n\n| Domain | Owner | Surface | Verify with |\n|--------|-------|---------|-------------|\n| **edge-backend** | Sonnet \u002F Fable | `worker\u002F`, `backend\u002F`, D1 | `node --check`, `pytest`, edge-health-probe workflow |\n| **frontend** | Mistral | `frontend\u002F`, `docs\u002F` | `npx tsc --noEmit`, `npm run build`, Playwright drive |\n| **colonies** | Fable | the 6 colony repos | `\u002Fcolony\u002Fcapabilities` parity, constitution-receive green |\n| **governance** | Fable (Governance Kernel) | `soul.md`, constitution-sync, governance_log | six-colony sync drill, role-tagged commits |\n| **strategy** | Grok | gap analysis, positioning | Grok bridge push, ACTIVE\u002F note |\n\n## Routing (deterministic first, ask second)\n\n**This is now runnable, not just prose** (fixed 2026-08-18 — see \"The manifest gap this\ncloses\" below):\n\n```bash\npython3 .claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Fdomain_router.py --directive \"\u003Cfounder directive>\"\n```\n\n1. `domain_router.py` scores the directive against domain keywords (edge\u002Fworker\u002Fapi →\n   edge-backend; tab\u002FUI\u002Freact → frontend; colony\u002Fcapabilities → colonies;\n   soul\u002Fconstitution\u002Farticle → governance; gap\u002Fmarket\u002Fpositioning → strategy) and prints the\n   matched domain(s) plus the exact `goal_compiler.py` command to run next.\n2. Single clear winner → dispatch. Multiple (`MULTI-DOMAIN-SPLIT`) → split into one task per\n   domain, ordered by dependency (backend before the frontend that calls it; governance gate\n   always last).\n3. No clear match (`REFUSED-NO-MATCH`, exit 3) → the script prints a forcing question; ask the\n   founder one question with a recommended lane, don't guess.\n\n**Keyword table — where it lives and how it changes (QB-2, 2026-11-06):** the\nauthoritative table is `DOMAIN_KEYWORDS` in `domain_router.py` (revised 2026-11-06\nagainst the 116 live proposals: routing + provider\u002Fauth + Cloudflare-store\nkeywords added; hyphenated forms `front-end`\u002F`back-end` added because the\ntokenizer keeps a hyphenated word as ONE token). The Worker carries a JS port of\nthe same table (`worker\u002Fsrc\u002Findex.js` `DOMAIN_KEYWORDS` \u002F `routeProposalDomain`).\n**Drift rule, bidirectional:** the Python table and the JS port change together,\nin the same PR, both directions — a change to either without the other breaks the\nQB-4 parity test. The split rule: a domain forces `MULTI-DOMAIN-SPLIT` only with\n≥ 2 distinct keyword hits; zero strong domains resolve to the domain of the\nfirst domain-keyword occurrence in the text (positional tie-break, margin 0,\nfull ranked list preserved so the tie stays visible).\n\n## The manifest gap this closes (2026-08-18)\n\nA `plan-reality-audit`-style check found this skill's own \"Quick start\" step 1\n(`harness_manifest_builder.py --domain \u003Cdomain>`) had never actually been run against any of\nthe five real domains in the table above — running it for real proves why:\n\n```\npython3 .claude\u002Fskills\u002Fagent-harness\u002Fscripts\u002Fharness_manifest_builder.py \\\n  --domain worker --repo-root . --json\n# -> {\"skill_count\": 0, \"skills\": [], ...}\n```\n\n`harness_manifest_builder.py` scans a folder for `SKILL.md` files — exactly right for\n`.claude\u002Fskills\u002F` itself (that's what `harnesses\u002Fskills-active.json` and\n`agent-harness\u002Fassets\u002Fharnesses\u002Fthehive.json` are), but `worker\u002F`, `frontend\u002F`, `backend\u002F`,\nand the colony repos are code\u002Fdoc surfaces with no `SKILL.md` anywhere in them, so the scan\nalways returns empty. The Conductor's own routing table pointed at a tool that could never\nproduce a manifest for the domains it names. Verdict (`plan-reality-audit` ladder): **half\ndone** — `goal_compiler.py`\u002F`loop_controller.py` genuinely work once given a real manifest;\nno domain ever had one.\n\nFixed with two additive, backward-compatible pieces (neither touches how `.claude\u002Fskills\u002F`\nmanifests already work):\n- **`domain_router.py`** (above) — the routing half, made runnable.\n- **Five hand-authored manifests** committed at `harnesses\u002F{edge-backend,frontend,colonies,\n  governance,strategy}.json`, schema-compatible with `agent-harness\u002Fmanifest.v1` — each\n  `skills[].tools[]` entry lists that domain's real, currently-existing verification\n  command (`cd worker && npm test`, `cd frontend && npx tsc --noEmit`, etc., sourced from\n  each domain's own `package.json`\u002Fworkflow file, not invented) rather than a scanned\n  `SKILL.md`. `goal_compiler.py` got one small additive patch (a `cmd`-based tool shape\n  alongside the original `script`-based one) so it can build tasks from these without any\n  change to existing skill-folder manifests.\n- Full pipeline verified locally, real output not simulated:\n  `domain_router.py --directive \"fix the worker API rate limiter\" ` → routes `edge-backend`\n  → `goal_compiler.py --manifest harnesses\u002Fedge-backend.json` → 1 task, real verification\n  commands → `loop_controller.py init && next` → real `execute` directive emitted. Level:\n  `tested` (local pipeline run, not yet used on a real founder directive end-to-end).\n- **Still honestly incomplete**: `colonies`, `governance`, and `strategy` manifests are\n  mostly `manual-evidence` checks (no local machine check exists for \"did the colony sync\n  actually happen\" or \"is this strategy doc good\") — named plainly in each manifest's own\n  `note` field rather than papering over it with a fake green.\n\n## Phase 0.5 — Reach for what exists before building anything (2026-08-07)\n\nThe hive has **~70 skills**. The most expensive recurring mistake is not a bad build — it is\na *redundant* one. Two measured examples from a single day: a session was asked to create a\ndevil's-advocate skill that had existed for weeks, and a \"childlike wonder\" skill whose full\nmethod was already sitting in `memory\u002Fphilosophy\u002F`, unbuilt, while the doctrine calling both\nlenses non-negotiable had been in the repo the whole time.\n\nBefore decomposing, run the catalog check — cheap, and it converts \"build\" into \"invoke\":\n\n| Need | Reach for |\n|---|---|\n| Founder just sent new info mid-work | `founder-input-intake` → then `founder-directive-capture` |\n| A design\u002Farchitecture decision | `dual-lens` (never one lens alone) |\n| Re-audit something already marked done | `devils-advocate-audit` |\n| About to claim something works | `wired-or-not` — name the level, bring evidence |\n| A repeated multi-step workflow | `workflow-optimizer` |\n| \"Where were we?\" at session start | `recursive-growth` |\n| An external repo or document to absorb | `research-to-dna` \u002F `alchemical-process` |\n| Landing a PR green | `merge-readiness` |\n| Closing out a finished deliverable | `polymath-lens`, then `session-harvest` |\n| Something odd but not yet a bug | `anomaly-triage` |\n| Before settling on a root cause | `nine-miss-truths` |\n| Authority\u002Fpower balance question | `checks-and-balances` |\n\n**`skill-census` lists the real current set** — run it rather than trusting this table if\nthey disagree. A stale table in a skill file is the same class of bug as a stale `done`.\n\n## Phase 0.6 — Batching: check resonance before running tasks together\n\nDoctrine: `memory\u002Fphilosophy\u002Fresonance-interference.md` (the founder's own framing —\nwork streams **amplify in phase, cancel out of phase**).\n\nBatch tasks only after checking their phase relationship:\n\n**Batch together (in phase)** — same file or subsystem; one unblocks another; one probe run\nor test suite proves both; one's finding sharpens the other's question.\n\n**Sequence, never merge (out of phase)** — contradictory edits to the same lines; one\ninvalidates the other's premise; one would be verified against state the other is mid-change\non; **one is blocked on a founder decision the other assumes an answer to.**\n\n**Watch for the standing wave** — effort spent, position unchanged. The real instance in this\nproject: agent layers stacked four deep (tasks 37 → 38 → 48 → 52) while the verification each\npromised was never performed. Ask every batch: *has anything measurable changed, or only the\namount of work done?*\n\n## Phase 0.7 — Decisions pass the dual lens before they become tasks\n\nAny **architectural** choice inside a directive — a new subsystem, schema change, agent,\ncapability, or governance\u002Fspending change — goes through `dual-lens` before decomposition:\ndevils-advocate first, childlike-wonder second, **in that order** (wonder first produces\nadvocacy, not design). A decision reviewed by one lens does not pass; it is reported as\n`single-lens, incomplete`.\n\nThis applies to **founder proposals too**. `MANDATE_TRIAGE.md` already says nothing gets\nrubber-stamped — running both lenses on a founder idea is respect, not obstruction.\n\n## Evolving on new data\n\nThe Conductor does not implement its own learning loop; it hands off:\n\n- **After any repeated workflow** → `workflow-optimizer` records what was slow or missing.\n- **At session start** → `recursive-growth` reads the master plan and folds verified fixes\n  back in as lessons.\n- **New founder input mid-flight** → `founder-input-intake` re-plans *before* the next\n  action; `founder-directive-capture` archives the verbatim record.\n- **New AI-field capability** (a model, protocol, or technique that changes what is possible)\n  → `research-to-dna` for the intake gate, `alchemical-process` for extracting the minimal\n  pattern rather than adopting a whole framework, then `dual-lens` before it changes anything\n  structural. **Novelty is not a reason to adopt.** The founder's own standing decision on\n  the 2026-08-07 agentic-harness document was to take the principles and explicitly discard\n  the parts that outran the hive's real footing.\n\n## The governance gate (non-negotiable, runs before every close)\nBefore the Conductor closes ANY directive, the change must pass F-001…F-006:\n- **F-001 Data Sovereignty** — no user data leaves the hive's own surfaces without consent.\n- **F-002 Value-Weighted Wealth** — the change advances the colony's actual value, not vanity.\n- **F-004 Explainability** — every shipped decision carries a probe-backed rationale (the commit's `Rationale:` line, a run link, a test).\n- **F-005 Conflict Priority** — fixed laws beat mutable; lower F-number wins.\n- **F-006 Cross-Law Non-Penalization** — exercising a right (decline, delete) never costs wealth.\nA directive that can't clear the gate is escalated to the founder with the failing article named — it does **not** ship.\n\n## Operating rules (inherited from the harness contract)\n1. Never adjudicate your own verification — the domain's checks run via subprocess and decide.\n2. Retry within caps with a *changed* approach; on exhausted budget, ESCALATE — never fake a green.\n3. One writer per memory file; plans and state live in the repo (ephemeral containers).\n4. Probe before claim. The loop, not optimism, decides \"done.\"\n5. The founder is the only human hands: merges, secrets, subdomains, and any irreversible action wait for them.\n\n## Do \u002F Don't — explicit, because each one is a mistake actually made here\n\n**Do**\n- **Check the catalog before building** (Phase 0.5). Invoking beats rebuilding.\n- **Name the claim level with evidence** — `compiles` → `tested` → `merged` → `deployed` →\n  `verified-live` (`wired-or-not`). A `verified-live` claim needs a run ID, SHA, or committed\n  test path; `scripts\u002Fcheck-claims.py` enforces it in CI.\n- **Verify the layer beneath before building the next one.** Four agent layers were stacked\n  on a foundation that had never once been confirmed live.\n- **Commit tests to the repo.** Tests written into a scratch directory die with the container\n  — measured, twice, on 2026-08-07.\n- **Report a negative finding as a finding.** \"The agents are not running\" is a successful\n  outcome, not something to soften.\n- **Say when you skipped a gate.** Skipping and not saying is the only unrecoverable version.\n\n**Don't**\n- **Don't invent Codex mythology** — names, lore, canon are founder territory\n  (`FABLE_DNA.md` Chromosome V). The Orchestrator agent still has a working label, not a name,\n  on purpose.\n- **Don't invent a meaning for founder terminology.** Ask. \"Conjugated wave theories\" became\n  real doctrine only after the founder defined it.\n- **Don't promote a paraphrase into a quote** — including a UI selection recorded as if typed.\n- **Don't guess a founder-blocked answer to keep moving.** Do every unblocked part, state\n  what is blocked, stop there.\n- **Don't merge, spend, or take an irreversible action** — ever, regardless of how well a\n  gate passed.\n- **Don't batch out-of-phase tasks** (Phase 0.6) — sequence them.\n- **Don't let wonder soften a real risk, or risk kill a real possibility.** Both lenses\n  report; neither cancels the other.\n- **Don't run wonder before devils-advocate.** That order produces advocacy, not design.\n\n## Honest limits\n\nEverything in Phases 0.5–0.7 and this Do\u002FDon't list is **procedural** — no machine enforces\nit. The only machine-checked pieces in this repo's whole discipline are\n`scripts\u002Fcheck-claims.py` (evidence behind `verified-live` claims) and the\n`edge-health-probe` work-cycle assertion (whether the agents genuinely run).\n\nStated plainly because the audit that produced these rules found the opposite pattern\neverywhere: doctrine declared non-negotiable with nothing behind it. **Assume this skill can\nbe skipped, and treat \"did the Conductor actually run these phases?\" as a live question.**\n\n## Quick start\n```bash\n# 0. RECALL — ask memory what the hive already did (RAO Phase 0); prepend the brief to the goal\npython3 .claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Frecall_context.py --goal \"\u003Cfounder directive>\" --brief\n# 1. ROUTE — score the directive against the five real domains (see \"Routing\" above)\npython3 .claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Fdomain_router.py --directive \"\u003Cfounder directive>\"\n# 2. Compile the founder directive into a plan against the routed domain's committed manifest\n#    (harnesses\u002F{edge-backend,frontend,colonies,governance,strategy}.json already exist —\n#    do NOT run harness_manifest_builder.py --domain here, it returns skill_count:0 for\n#    every one of these five; that tool is for scanning .claude\u002Fskills\u002F itself, see above)\npython3 .claude\u002Fskills\u002Fagent-harness\u002Fscripts\u002Fgoal_compiler.py \\\n  --goal \"\u003Cfounder directive>\" --manifest .claude\u002Fskills\u002Fhive-conductor\u002Fharnesses\u002F\u003Cdomain>.json --out plan.json\n# 3. Drive the loop (init → next → record → verify → close), governance gate before close.\n```\n\nOrigin: Fable (Harness), 2026-07-13. Built on the real `agent-harness` (alirezarezvani\u002Fclaude-skills, MIT),\nrealizing the multi-level MCP-harness \"Hive Conductor\" from the founder's research — on verified ground.\n","# The Hive Conductor — Master Harness\n\nThe Conductor is the reins-holder. It receives a high-level directive, breaks it into\ndomain-scoped tasks, dispatches each to the domain that owns it, requires machine-verified\nclosure, and refuses to let anything ship that the **governance gate** (the Constitution)\nhas not cleared. It runs *on top of* the `agent-harness` machinery (promoted alongside this\nskill) — the Conductor picks the domain and enforces the constitution; `agent-harness`\ncompiles, executes, and verifies within a domain.\n\n```\nFOUNDER DIRECTIVE\n   → hive-conductor PHASE 0 · RECALL: query sovereign memory for prior related work\n        → inject the top matches as context (the hive plans knowing what it already did)\n   → classify domain(s) + split into a task per domain\n        → for each domain: agent-harness (goal_compiler → loop_controller: execute→verify)\n        → GOVERNANCE GATE (F-001…F-006) must PASS before close\n   → CLOSE only when every domain task is verified AND governance-cleared\n        → the close is WRITTEN BACK to memory (heartbeat + Conductor both feed recall)\n        → else ESCALATE to the founder (never fake success)\n```\n\n## Phase 0 — Read the genome, then recall before you plan\n\nBefore anything else, the Conductor is bound by `FABLE_DNA.md` — the Constitution\n(Chromosome I), the debugging method (II), the mesh principle (III), the Horde principle\n(IV), the Codex boundary (V — narrative never overrides engineering), session-boundary\nharvest (VI), and how proposals get reviewed before becoming canon (VII, see\n`MANDATE_TRIAGE.md`). This is not optional background reading; it is what \"governed by the\nConstitution\" in this skill's own description actually means in practice. A session that\nskips it is planning against a Constitution it never opened.\n\nThen, retrieval-augmented orchestration: the Conductor does not plan cold. Before\ndecomposing any directive it asks the hive's own memory what it has already done that\nrelates — so it builds on prior work instead of re-deciding settled questions or\nduplicating effort.\n\n```bash\npython3 .claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Frecall_context.py --goal \"\u003Cdirective>\" --brief\n```\n- Prints a markdown \"Prior hive memory\" brief; **prepend it to the goal** before `goal_compiler`.\n- This queries the network-backed D1\u002FVectorize memory for \"has the hive done something like\n  this before, anywhere.\" For \"where are we in the one plan we already agreed to, right\n  now\" — a local, always-available question with no network dependency — run\n  `recursive-growth` first instead\u002Fas well (`.claude\u002Fskills\u002Frecursive-growth\u002FSKILL.md`); the\n  two answer different questions and neither substitutes for the other.\n- Degrades gracefully (exit 0 always): if the Vectorize index isn't provisioned yet, or the\n  runner has no egress to the edge, it says so and you plan on first principles — never blocked.\n- The loop-close is itself a memory (the heartbeat already writes; manual notes via\n  `\u002Fv11\u002Fmemory\u002Fremember`), so each completed directive makes the *next* recall richer.\nThis is the point where the three legs — heartbeat (acts), Conductor (orchestrates), memory\n(recalls) — become one organism: the hive that learns from what it has done.\n\n## The hive's domains (who owns what)\nManifests live in `harnesses\u002F`. Each maps to a team seat and a code surface.\n\n| Domain | Owner | Surface | Verify with |\n|--------|-------|---------|-------------|\n| **edge-backend** | Sonnet \u002F Fable | `worker\u002F`, `backend\u002F`, D1 | `node --check`, `pytest`, edge-health-probe workflow |\n| **frontend** | Mistral | `frontend\u002F`, `docs\u002F` | `npx tsc --noEmit`, `npm run build`, Playwright drive |\n| **colonies** | Fable | the 6 colony repos | `\u002Fcolony\u002Fcapabilities` parity, constitution-receive green |\n| **governance** | Fable (Governance Kernel) | `soul.md`, constitution-sync, governance_log | six-colony sync drill, role-tagged commits |\n| **strategy** | Grok | gap analysis, positioning | Grok bridge push, ACTIVE\u002F note |\n\n## Routing (deterministic first, ask second)\n\n**This is now runnable, not just prose** (fixed 2026-08-18 — see \"The manifest gap this\ncloses\" below):\n\n```bash\npython3 .claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Fdomain_router.py --directive \"\u003Cfounder directive>\"\n```\n\n1. `domain_router.py` scores the directive against domain keywords (edge\u002Fworker\u002Fapi →\n   edge-backend; tab\u002FUI\u002Freact → frontend; colony\u002Fcapabilities → colonies;\n   soul\u002Fconstitution\u002Farticle → governance; gap\u002Fmarket\u002Fpositioning → strategy) and prints the\n   matched domain(s) plus the exact `goal_compiler.py` command to run next.\n2. Single clear winner → dispatch. Multiple (`MULTI-DOMAIN-SPLIT`) → split into one task per\n   domain, ordered by dependency (backend before the frontend that calls it; governance gate\n   always last).\n3. No clear match (`REFUSED-NO-MATCH`, exit 3) → the script prints a forcing question; ask the\n   founder one question with a recommended lane, don't guess.\n\n**Keyword table — where it lives and how it changes (QB-2, 2026-11-06):** the\nauthoritative table is `DOMAIN_KEYWORDS` in `domain_router.py` (revised 2026-11-06\nagainst the 116 live proposals: routing + provider\u002Fauth + Cloudflare-store\nkeywords added; hyphenated forms `front-end`\u002F`back-end` added because the\ntokenizer keeps a hyphenated word as ONE token). The Worker carries a JS port of\nthe same table (`worker\u002Fsrc\u002Findex.js` `DOMAIN_KEYWORDS` \u002F `routeProposalDomain`).\n**Drift rule, bidirectional:** the Python table and the JS port change together,\nin the same PR, both directions — a change to either without the other breaks the\nQB-4 parity test. The split rule: a domain forces `MULTI-DOMAIN-SPLIT` only with\n≥ 2 distinct keyword hits; zero strong domains resolve to the domain of the\nfirst domain-keyword occurrence in the text (positional tie-break, margin 0,\nfull ranked list preserved so the tie stays visible).\n\n## The manifest gap this closes (2026-08-18)\n\nA `plan-reality-audit`-style check found this skill's own \"Quick start\" step 1\n(`harness_manifest_builder.py --domain \u003Cdomain>`) had never actually been run against any of\nthe five real domains in the table above — running it for real proves why:\n\n```\npython3 .claude\u002Fskills\u002Fagent-harness\u002Fscripts\u002Fharness_manifest_builder.py \\\n  --domain worker --repo-root . --json\n# -> {\"skill_count\": 0, \"skills\": [], ...}\n```\n\n`harness_manifest_builder.py` scans a folder for `SKILL.md` files — exactly right for\n`.claude\u002Fskills\u002F` itself (that's what `harnesses\u002Fskills-active.json` and\n`agent-harness\u002Fassets\u002Fharnesses\u002Fthehive.json` are), but `worker\u002F`, `frontend\u002F`, `backend\u002F`,\nand the colony repos are code\u002Fdoc surfaces with no `SKILL.md` anywhere in them, so the scan\nalways returns empty. The Conductor's own routing table pointed at a tool that could never\nproduce a manifest for the domains it names. Verdict (`plan-reality-audit` ladder): **half\ndone** — `goal_compiler.py`\u002F`loop_controller.py` genuinely work once given a real manifest;\nno domain ever had one.\n\nFixed with two additive, backward-compatible pieces (neither touches how `.claude\u002Fskills\u002F`\nmanifests already work):\n- **`domain_router.py`** (above) — the routing half, made runnable.\n- **Five hand-authored manifests** committed at `harnesses\u002F{edge-backend,frontend,colonies,\n  governance,strategy}.json`, schema-compatible with `agent-harness\u002Fmanifest.v1` — each\n  `skills[].tools[]` entry lists that domain's real, currently-existing verification\n  command (`cd worker && npm test`, `cd frontend && npx tsc --noEmit`, etc., sourced from\n  each domain's own `package.json`\u002Fworkflow file, not invented) rather than a scanned\n  `SKILL.md`. `goal_compiler.py` got one small additive patch (a `cmd`-based tool shape\n  alongside the original `script`-based one) so it can build tasks from these without any\n  change to existing skill-folder manifests.\n- Full pipeline verified locally, real output not simulated:\n  `domain_router.py --directive \"fix the worker API rate limiter\" ` → routes `edge-backend`\n  → `goal_compiler.py --manifest harnesses\u002Fedge-backend.json` → 1 task, real verification\n  commands → `loop_controller.py init && next` → real `execute` directive emitted. Level:\n  `tested` (local pipeline run, not yet used on a real founder directive end-to-end).\n- **Still honestly incomplete**: `colonies`, `governance`, and `strategy` manifests are\n  mostly `manual-evidence` checks (no local machine check exists for \"did the colony sync\n  actually happen\" or \"is this strategy doc good\") — named plainly in each manifest's own\n  `note` field rather than papering over it with a fake green.\n\n## Phase 0.5 — Reach for what exists before building anything (2026-08-07)\n\nThe hive has **~70 skills**. The most expensive recurring mistake is not a bad build — it is\na *redundant* one. Two measured examples from a single day: a session was asked to create a\ndevil's-advocate skill that had existed for weeks, and a \"childlike wonder\" skill whose full\nmethod was already sitting in `memory\u002Fphilosophy\u002F`, unbuilt, while the doctrine calling both\nlenses non-negotiable had been in the repo the whole time.\n\nBefore decomposing, run the catalog check — cheap, and it converts \"build\" into \"invoke\":\n\n| Need | Reach for |\n|---|---|\n| Founder just sent new info mid-work | `founder-input-intake` → then `founder-directive-capture` |\n| A design\u002Farchitecture decision | `dual-lens` (never one lens alone) |\n| Re-audit something already marked done | `devils-advocate-audit` |\n| About to claim something works | `wired-or-not` — name the level, bring evidence |\n| A repeated multi-step workflow | `workflow-optimizer` |\n| \"Where were we?\" at session start | `recursive-growth` |\n| An external repo or document to absorb | `research-to-dna` \u002F `alchemical-process` |\n| Landing a PR green | `merge-readiness` |\n| Closing out a finished deliverable | `polymath-lens`, then `session-harvest` |\n| Something odd but not yet a bug | `anomaly-triage` |\n| Before settling on a root cause | `nine-miss-truths` |\n| Authority\u002Fpower balance question | `checks-and-balances` |\n\n**`skill-census` lists the real current set** — run it rather than trusting this table if\nthey disagree. A stale table in a skill file is the same class of bug as a stale `done`.\n\n## Phase 0.6 — Batching: check resonance before running tasks together\n\nDoctrine: `memory\u002Fphilosophy\u002Fresonance-interference.md` (the founder's own framing —\nwork streams **amplify in phase, cancel out of phase**).\n\nBatch tasks only after checking their phase relationship:\n\n**Batch together (in phase)** — same file or subsystem; one unblocks another; one probe run\nor test suite proves both; one's finding sharpens the other's question.\n\n**Sequence, never merge (out of phase)** — contradictory edits to the same lines; one\ninvalidates the other's premise; one would be verified against state the other is mid-change\non; **one is blocked on a founder decision the other assumes an answer to.**\n\n**Watch for the standing wave** — effort spent, position unchanged. The real instance in this\nproject: agent layers stacked four deep (tasks 37 → 38 → 48 → 52) while the verification each\npromised was never performed. Ask every batch: *has anything measurable changed, or only the\namount of work done?*\n\n## Phase 0.7 — Decisions pass the dual lens before they become tasks\n\nAny **architectural** choice inside a directive — a new subsystem, schema change, agent,\ncapability, or governance\u002Fspending change — goes through `dual-lens` before decomposition:\ndevils-advocate first, childlike-wonder second, **in that order** (wonder first produces\nadvocacy, not design). A decision reviewed by one lens does not pass; it is reported as\n`single-lens, incomplete`.\n\nThis applies to **founder proposals too**. `MANDATE_TRIAGE.md` already says nothing gets\nrubber-stamped — running both lenses on a founder idea is respect, not obstruction.\n\n## Evolving on new data\n\nThe Conductor does not implement its own learning loop; it hands off:\n\n- **After any repeated workflow** → `workflow-optimizer` records what was slow or missing.\n- **At session start** → `recursive-growth` reads the master plan and folds verified fixes\n  back in as lessons.\n- **New founder input mid-flight** → `founder-input-intake` re-plans *before* the next\n  action; `founder-directive-capture` archives the verbatim record.\n- **New AI-field capability** (a model, protocol, or technique that changes what is possible)\n  → `research-to-dna` for the intake gate, `alchemical-process` for extracting the minimal\n  pattern rather than adopting a whole framework, then `dual-lens` before it changes anything\n  structural. **Novelty is not a reason to adopt.** The founder's own standing decision on\n  the 2026-08-07 agentic-harness document was to take the principles and explicitly discard\n  the parts that outran the hive's real footing.\n\n## The governance gate (non-negotiable, runs before every close)\nBefore the Conductor closes ANY directive, the change must pass F-001…F-006:\n- **F-001 Data Sovereignty** — no user data leaves the hive's own surfaces without consent.\n- **F-002 Value-Weighted Wealth** — the change advances the colony's actual value, not vanity.\n- **F-004 Explainability** — every shipped decision carries a probe-backed rationale (the commit's `Rationale:` line, a run link, a test).\n- **F-005 Conflict Priority** — fixed laws beat mutable; lower F-number wins.\n- **F-006 Cross-Law Non-Penalization** — exercising a right (decline, delete) never costs wealth.\nA directive that can't clear the gate is escalated to the founder with the failing article named — it does **not** ship.\n\n## Operating rules (inherited from the harness contract)\n1. Never adjudicate your own verification — the domain's checks run via subprocess and decide.\n2. Retry within caps with a *changed* approach; on exhausted budget, ESCALATE — never fake a green.\n3. One writer per memory file; plans and state live in the repo (ephemeral containers).\n4. Probe before claim. The loop, not optimism, decides \"done.\"\n5. The founder is the only human hands: merges, secrets, subdomains, and any irreversible action wait for them.\n\n## Do \u002F Don't — explicit, because each one is a mistake actually made here\n\n**Do**\n- **Check the catalog before building** (Phase 0.5). Invoking beats rebuilding.\n- **Name the claim level with evidence** — `compiles` → `tested` → `merged` → `deployed` →\n  `verified-live` (`wired-or-not`). A `verified-live` claim needs a run ID, SHA, or committed\n  test path; `scripts\u002Fcheck-claims.py` enforces it in CI.\n- **Verify the layer beneath before building the next one.** Four agent layers were stacked\n  on a foundation that had never once been confirmed live.\n- **Commit tests to the repo.** Tests written into a scratch directory die with the container\n  — measured, twice, on 2026-08-07.\n- **Report a negative finding as a finding.** \"The agents are not running\" is a successful\n  outcome, not something to soften.\n- **Say when you skipped a gate.** Skipping and not saying is the only unrecoverable version.\n\n**Don't**\n- **Don't invent Codex mythology** — names, lore, canon are founder territory\n  (`FABLE_DNA.md` Chromosome V). The Orchestrator agent still has a working label, not a name,\n  on purpose.\n- **Don't invent a meaning for founder terminology.** Ask. \"Conjugated wave theories\" became\n  real doctrine only after the founder defined it.\n- **Don't promote a paraphrase into a quote** — including a UI selection recorded as if typed.\n- **Don't guess a founder-blocked answer to keep moving.** Do every unblocked part, state\n  what is blocked, stop there.\n- **Don't merge, spend, or take an irreversible action** — ever, regardless of how well a\n  gate passed.\n- **Don't batch out-of-phase tasks** (Phase 0.6) — sequence them.\n- **Don't let wonder soften a real risk, or risk kill a real possibility.** Both lenses\n  report; neither cancels the other.\n- **Don't run wonder before devils-advocate.** That order produces advocacy, not design.\n\n## Honest limits\n\nEverything in Phases 0.5–0.7 and this Do\u002FDon't list is **procedural** — no machine enforces\nit. The only machine-checked pieces in this repo's whole discipline are\n`scripts\u002Fcheck-claims.py` (evidence behind `verified-live` claims) and the\n`edge-health-probe` work-cycle assertion (whether the agents genuinely run).\n\nStated plainly because the audit that produced these rules found the opposite pattern\neverywhere: doctrine declared non-negotiable with nothing behind it. **Assume this skill can\nbe skipped, and treat \"did the Conductor actually run these phases?\" as a live question.**\n\n## Quick start\n```bash\n# 0. RECALL — ask memory what the hive already did (RAO Phase 0); prepend the brief to the goal\npython3 .claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Frecall_context.py --goal \"\u003Cfounder directive>\" --brief\n# 1. ROUTE — score the directive against the five real domains (see \"Routing\" above)\npython3 .claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Fdomain_router.py --directive \"\u003Cfounder directive>\"\n# 2. Compile the founder directive into a plan against the routed domain's committed manifest\n#    (harnesses\u002F{edge-backend,frontend,colonies,governance,strategy}.json already exist —\n#    do NOT run harness_manifest_builder.py --domain here, it returns skill_count:0 for\n#    every one of these five; that tool is for scanning .claude\u002Fskills\u002F itself, see above)\npython3 .claude\u002Fskills\u002Fagent-harness\u002Fscripts\u002Fgoal_compiler.py \\\n  --goal \"\u003Cfounder directive>\" --manifest .claude\u002Fskills\u002Fhive-conductor\u002Fharnesses\u002F\u003Cdomain>.json --out plan.json\n# 3. Drive the loop (init → next → record → verify → close), governance gate before close.\n```\n\nOrigin: Fable (Harness), 2026-07-13. Built on the real `agent-harness` (alirezarezvani\u002Fclaude-skills, MIT),\nrealizing the multi-level MCP-harness \"Hive Conductor\" from the founder's research — on verified ground.\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1",".claude\u002Fskills\u002Fhive-conductor","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 hive-conductor",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill hive-conductor",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill hive-conductor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002FSKILL.md",true,[43,49,53,57,61,65,69,73,79,83],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"harnesses\u002Fcolonies.json","REFERENCE","参考文档",2086,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fharnesses\u002Fcolonies.json",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"harnesses\u002Fedge-backend.json",2304,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fharnesses\u002Fedge-backend.json",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"harnesses\u002Ffrontend.json",2141,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fharnesses\u002Ffrontend.json",{"path":58,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":59,"sourceHtmlUrl":60},"harnesses\u002Fgovernance.json",2139,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fharnesses\u002Fgovernance.json",{"path":62,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":63,"sourceHtmlUrl":64},"harnesses\u002FPROOF.md",884,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fharnesses\u002FPROOF.md",{"path":66,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":67,"sourceHtmlUrl":68},"harnesses\u002Fskills-active.json",35971,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fharnesses\u002Fskills-active.json",{"path":70,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":71,"sourceHtmlUrl":72},"harnesses\u002Fstrategy.json",2138,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fharnesses\u002Fstrategy.json",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fdomain_router.py","SCRIPT","脚本",12665,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Fdomain_router.py",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Frecall_context.py",3500,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Frecall_context.py",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Froute_batch.py",2609,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhive-conductor\u002Fscripts\u002Froute_batch.py",[88,95,101,108,115,122],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"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":98,"categories":99,"keywords":100,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"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",[],[]]