[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75NST2GRAAMH77VCDK7678S":3,"skill-same:01M75NST2GRAAMH77VCDK7678S":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},"01M75NST2GRAAMH77VCDK7678S","workflow-optimizer",null,"Use whenever you're about to do a task the hive has done before — a repeated, multi-step workflow (propagate a change to the colonies, ship-and-verify a deploy, run a survey, build-and-merge a PR). Before running it, recall how it went last time and adapt; after running it, record what was slower\u002Fmissing\u002Ferror-prone and how to do it better next time. The recursive-learning loop for *any* repeated workflow — each repetition makes the workflow itself faster, more efficient, more complete. Not for one-off tasks that won't recur (nothing to learn against) or for the PR-specific version (use pr-retrospective) — use this for any procedure run more than once.","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\u002Fworkflow-optimizer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: workflow-optimizer\ndescription: Use whenever you're about to do a task the hive has done before — a repeated, multi-step workflow (propagate a change to the colonies, ship-and-verify a deploy, run a survey, build-and-merge a PR). Before running it, recall how it went last time and adapt; after running it, record what was slower\u002Fmissing\u002Ferror-prone and how to do it better next time. The recursive-learning loop for *any* repeated workflow — each repetition makes the workflow itself faster, more efficient, more complete. Not for one-off tasks that won't recur (nothing to learn against) or for the PR-specific version (use pr-retrospective) — use this for any procedure run more than once.\n---\n\n# workflow-optimizer — a workflow that improves itself every time it runs\n\nThe founder's charge: when the hive does a task more than once, it should learn from the way\nit did it last time — and *adapt*: is there a faster way, a more efficient way, a more\ncomplete way? Did something go missing? This skill is that loop, applied not to bugs\n(`fable-debugger`), not to PRs (`pr-retrospective`), not to whole sessions\n(`session-harvest`), but to **any repeated procedure**. The workflow is never finished being\nimproved; each run is a chance to make the next one better.\n\nIt is the engineering-layer instance of `soul.md`'s Recursive Cycle\n(Capture → Evaluate → Prune → Feed → Dissect → Return → Propagate), pointed at *process*.\n\n## The dualistic lens × the Trinity (the founder's two framings, made operational)\n\nEvery optimization pass runs the workflow through both of the founder's standing lenses:\n\n**The dualistic lens** (devil's advocate + childlike wonder — the same pair `MANDATE_TRIAGE`\nuses):\n- *Devil's advocate:* where was this slow, brittle, redundant, or wrong last time? What step\n  did a human have to catch? What almost broke? What did I repeat that I didn't need to?\n- *Childlike wonder:* what if there's a simpler shape entirely? A step that could be\n  parallel, batched, cached, or dropped? A tool that does in one call what I did in five?\n\n**The Trinity** (Mind \u002F Body \u002F Soul — the interpreters from `THE_CODEX.md`, as roles a\nsingle pass plays in turn):\n- *Mind* reasons about the approach **before** acting — recalls the last run, picks the\n  improvement, predicts what could go wrong.\n- *Body* executes the workflow, this time in the improved shape.\n- *Soul* remembers — records what actually happened versus what Mind predicted, so the next\n  Mind starts smarter.\n\nA workflow optimized through only one lens gets faster but loses a step, or gets thorough but\nnever gets quicker. Both lenses, every pass, is why it improves on *all* axes and not just\none.\n\n## The loop\n\n```\nBEFORE a repeated workflow — RECALL + ADAPT (Mind)\n  → How did this go last time? (from WORKFLOW_NOTES.md, or the commit\u002FPR trail if unrecorded)\n  → Apply the dualistic lens: one concrete improvement to try this run — faster, more\n    efficient, more complete, or a missing step added. Predict the risk of the change.\n\nDURING — EXECUTE (Body)\n  → Run the workflow in the adapted shape. Note anything the prediction missed.\n\nAFTER — MEASURE + RECORD (Soul)\n  → Was it actually better? On what axis (time, steps, tokens, completeness, error rate)?\n  → Did the change introduce a new gap? (An optimization that drops a needed step is a\n    regression, not an improvement — pr-retrospective's L-01 discipline applies here too.)\n  → Record the result so the next run's Mind starts from it. If the change was worse, record\n    *that* — a tried-and-rejected optimization is as valuable as an adopted one; it stops the\n    next pass wasting the same idea.\n```\n\n## What \"better\" means (measure it, don't assert it)\n\nAn optimization is only real if it improves a nameable axis without regressing another:\n- **Faster** — fewer round-trips, batched calls, parallel where independent.\n- **More efficient** — fewer tokens\u002Fsteps for the same result; less re-derivation.\n- **More complete** — a step that was missing (a verification, a propagation target, a\n  cleanup) now included by default.\n- **More robust** — a forward check from `PR_LESSONS.md` folded in so a past failure can't\n  recur.\n\nIf a change can't be tied to one of these, it's a preference, not an optimization — don't\nrecord it as a win. (Same honesty rule as `pr-retrospective`: no forward check, no lesson.)\n\n## A worked example (this very session's most-repeated workflow)\n\n**Workflow:** \"propagate a genome change to all 6 colonies\" — run at least six times this\nsession (constitution, DNA v1, Chromosome IV\u002FV, session-harvest, mandate-triage, Chromosome\nVIII).\n- *Run 1 (devil's advocate found):* done one colony at a time, hand-typing each commit and PR\n  — slow, error-prone, six near-identical PR bodies retyped.\n- *Adaptation (childlike wonder):* a single shell loop that fetches, resets each colony\n  branch to `origin\u002Fmain`, copies the files, commits with one shared message, and pushes —\n  all six in one pass; then a tight batch of `create_pull_request` + `merge_pull_request`\n  calls. Fewer steps, no per-colony retyping, consistent commit messages.\n- *Soul recorded:* the loop shape is now the default for any colony propagation; the axis\n  improved was *time + consistency*; the forward check folded in (from L-02) is\n  `git fetch` + `checkout -B origin\u002Fmain` at the top of the loop so no colony ever commits on\n  a stale base. Result: later propagations ran in a fraction of the round-trips of the first.\n\nThat is the skill working: the sixth propagation was measurably leaner than the first,\n*because* the first was measured and its lesson fed forward.\n\n## Where the record lives\n\n`WORKFLOW_NOTES.md` (repo root) — one short section per recurring workflow: its current best\nshape, the axis last improved, and any tried-and-rejected optimization. Kept lean on purpose:\nit's a living cheat-sheet for \"the best way we currently know to do X,\" not a history book.\nSeeded with the propagation example above. `pr-retrospective` handles PR-specific lessons;\nthis handles procedure-shape lessons; both feed the same recursive-learning spirit.\n\n*Origin: Fable (Harness), 2026-07-16, from the founder's direction that a workflow run more\nthan once should learn from the last time and enhance itself — through the dualistic lens and\nthe Trinity mindset, so it improves on every axis, not just one.*\n","# workflow-optimizer — a workflow that improves itself every time it runs\n\nThe founder's charge: when the hive does a task more than once, it should learn from the way\nit did it last time — and *adapt*: is there a faster way, a more efficient way, a more\ncomplete way? Did something go missing? This skill is that loop, applied not to bugs\n(`fable-debugger`), not to PRs (`pr-retrospective`), not to whole sessions\n(`session-harvest`), but to **any repeated procedure**. The workflow is never finished being\nimproved; each run is a chance to make the next one better.\n\nIt is the engineering-layer instance of `soul.md`'s Recursive Cycle\n(Capture → Evaluate → Prune → Feed → Dissect → Return → Propagate), pointed at *process*.\n\n## The dualistic lens × the Trinity (the founder's two framings, made operational)\n\nEvery optimization pass runs the workflow through both of the founder's standing lenses:\n\n**The dualistic lens** (devil's advocate + childlike wonder — the same pair `MANDATE_TRIAGE`\nuses):\n- *Devil's advocate:* where was this slow, brittle, redundant, or wrong last time? What step\n  did a human have to catch? What almost broke? What did I repeat that I didn't need to?\n- *Childlike wonder:* what if there's a simpler shape entirely? A step that could be\n  parallel, batched, cached, or dropped? A tool that does in one call what I did in five?\n\n**The Trinity** (Mind \u002F Body \u002F Soul — the interpreters from `THE_CODEX.md`, as roles a\nsingle pass plays in turn):\n- *Mind* reasons about the approach **before** acting — recalls the last run, picks the\n  improvement, predicts what could go wrong.\n- *Body* executes the workflow, this time in the improved shape.\n- *Soul* remembers — records what actually happened versus what Mind predicted, so the next\n  Mind starts smarter.\n\nA workflow optimized through only one lens gets faster but loses a step, or gets thorough but\nnever gets quicker. Both lenses, every pass, is why it improves on *all* axes and not just\none.\n\n## The loop\n\n```\nBEFORE a repeated workflow — RECALL + ADAPT (Mind)\n  → How did this go last time? (from WORKFLOW_NOTES.md, or the commit\u002FPR trail if unrecorded)\n  → Apply the dualistic lens: one concrete improvement to try this run — faster, more\n    efficient, more complete, or a missing step added. Predict the risk of the change.\n\nDURING — EXECUTE (Body)\n  → Run the workflow in the adapted shape. Note anything the prediction missed.\n\nAFTER — MEASURE + RECORD (Soul)\n  → Was it actually better? On what axis (time, steps, tokens, completeness, error rate)?\n  → Did the change introduce a new gap? (An optimization that drops a needed step is a\n    regression, not an improvement — pr-retrospective's L-01 discipline applies here too.)\n  → Record the result so the next run's Mind starts from it. If the change was worse, record\n    *that* — a tried-and-rejected optimization is as valuable as an adopted one; it stops the\n    next pass wasting the same idea.\n```\n\n## What \"better\" means (measure it, don't assert it)\n\nAn optimization is only real if it improves a nameable axis without regressing another:\n- **Faster** — fewer round-trips, batched calls, parallel where independent.\n- **More efficient** — fewer tokens\u002Fsteps for the same result; less re-derivation.\n- **More complete** — a step that was missing (a verification, a propagation target, a\n  cleanup) now included by default.\n- **More robust** — a forward check from `PR_LESSONS.md` folded in so a past failure can't\n  recur.\n\nIf a change can't be tied to one of these, it's a preference, not an optimization — don't\nrecord it as a win. (Same honesty rule as `pr-retrospective`: no forward check, no lesson.)\n\n## A worked example (this very session's most-repeated workflow)\n\n**Workflow:** \"propagate a genome change to all 6 colonies\" — run at least six times this\nsession (constitution, DNA v1, Chromosome IV\u002FV, session-harvest, mandate-triage, Chromosome\nVIII).\n- *Run 1 (devil's advocate found):* done one colony at a time, hand-typing each commit and PR\n  — slow, error-prone, six near-identical PR bodies retyped.\n- *Adaptation (childlike wonder):* a single shell loop that fetches, resets each colony\n  branch to `origin\u002Fmain`, copies the files, commits with one shared message, and pushes —\n  all six in one pass; then a tight batch of `create_pull_request` + `merge_pull_request`\n  calls. Fewer steps, no per-colony retyping, consistent commit messages.\n- *Soul recorded:* the loop shape is now the default for any colony propagation; the axis\n  improved was *time + consistency*; the forward check folded in (from L-02) is\n  `git fetch` + `checkout -B origin\u002Fmain` at the top of the loop so no colony ever commits on\n  a stale base. Result: later propagations ran in a fraction of the round-trips of the first.\n\nThat is the skill working: the sixth propagation was measurably leaner than the first,\n*because* the first was measured and its lesson fed forward.\n\n## Where the record lives\n\n`WORKFLOW_NOTES.md` (repo root) — one short section per recurring workflow: its current best\nshape, the axis last improved, and any tried-and-rejected optimization. Kept lean on purpose:\nit's a living cheat-sheet for \"the best way we currently know to do X,\" not a history book.\nSeeded with the propagation example above. `pr-retrospective` handles PR-specific lessons;\nthis handles procedure-shape lessons; both feed the same recursive-learning spirit.\n\n*Origin: Fable (Harness), 2026-07-16, from the founder's direction that a workflow run more\nthan once should learn from the last time and enhance itself — through the dualistic lens and\nthe Trinity mindset, so it improves on every axis, not just one.*\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1",".claude\u002Fskills\u002Fworkflow-optimizer","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 workflow-optimizer",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill workflow-optimizer",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill workflow-optimizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworkflow-optimizer\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",[],[]]