[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75QEG39B8JW262PB3535P9D":3,"skill-same:01M75QEG39B8JW262PB3535P9D":55},{"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},"01M75QEG39B8JW262PB3535P9D","agent-workflow-designer",null,"Design production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost\u002Fcontext controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fagent-workflow-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"agent-workflow-designer\"\ndescription: \"Design production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost\u002Fcontext controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.\"\n---\n\n# Agent Workflow Designer\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Multi-Agent Systems \u002F AI Orchestration\n\n---\n\n## Overview\n\nDesign production-grade multi-agent workflows with clear pattern choice, handoff contracts, failure handling, and cost\u002Fcontext controls.\n\n## Core Capabilities\n\n- Workflow pattern selection for multi-step agent systems\n- Skeleton config generation for fast workflow bootstrapping\n- Context and cost discipline across long-running flows\n- Error recovery and retry strategy scaffolding\n- Documentation pointers for operational pattern tradeoffs\n\n---\n\n## When to Use\n\n- A single prompt is insufficient for task complexity\n- You need specialist agents with explicit boundaries\n- You want deterministic workflow structure before implementation\n- You need validation loops for quality or safety gates\n\n---\n\n## Quick Start\n\n```bash\n# Generate a sequential workflow skeleton\npython3 scripts\u002Fworkflow_scaffolder.py sequential --name content-pipeline\n\n# Generate an orchestrator workflow and save it\npython3 scripts\u002Fworkflow_scaffolder.py orchestrator --name incident-triage --output workflows\u002Fincident-triage.json\n```\n\n---\n\n## Pattern Map\n\n- `sequential`: strict step-by-step dependency chain\n- `parallel`: fan-out\u002Ffan-in for independent subtasks\n- `router`: dispatch by intent\u002Ftype with fallback\n- `orchestrator`: planner coordinates specialists with dependencies\n- `evaluator`: generator + quality gate loop\n\nDetailed templates: `references\u002Fworkflow-patterns.md`\n\n---\n\n## Recommended Workflow\n\n1. Select pattern based on dependency shape and risk profile.\n2. Scaffold config via `scripts\u002Fworkflow_scaffolder.py`.\n3. Define handoff contract fields for every edge.\n4. Add retry\u002Ftimeouts and output validation gates.\n5. Dry-run with small context budgets before scaling.\n\n---\n\n## Common Pitfalls\n\n- Over-orchestrating tasks solvable by one well-structured prompt\n- Missing timeout\u002Fretry policies for external-model calls\n- Passing full upstream context instead of targeted artifacts\n- Ignoring per-step cost accumulation\n\n## Best Practices\n\n1. Start with the smallest pattern that can satisfy requirements.\n2. Keep handoff payloads explicit and bounded.\n3. Validate intermediate outputs before fan-in synthesis.\n4. Enforce budget and timeout limits in every step.\n","# Agent Workflow Designer\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Multi-Agent Systems \u002F AI Orchestration\n\n---\n\n## Overview\n\nDesign production-grade multi-agent workflows with clear pattern choice, handoff contracts, failure handling, and cost\u002Fcontext controls.\n\n## Core Capabilities\n\n- Workflow pattern selection for multi-step agent systems\n- Skeleton config generation for fast workflow bootstrapping\n- Context and cost discipline across long-running flows\n- Error recovery and retry strategy scaffolding\n- Documentation pointers for operational pattern tradeoffs\n\n---\n\n## When to Use\n\n- A single prompt is insufficient for task complexity\n- You need specialist agents with explicit boundaries\n- You want deterministic workflow structure before implementation\n- You need validation loops for quality or safety gates\n\n---\n\n## Quick Start\n\n```bash\n# Generate a sequential workflow skeleton\npython3 scripts\u002Fworkflow_scaffolder.py sequential --name content-pipeline\n\n# Generate an orchestrator workflow and save it\npython3 scripts\u002Fworkflow_scaffolder.py orchestrator --name incident-triage --output workflows\u002Fincident-triage.json\n```\n\n---\n\n## Pattern Map\n\n- `sequential`: strict step-by-step dependency chain\n- `parallel`: fan-out\u002Ffan-in for independent subtasks\n- `router`: dispatch by intent\u002Ftype with fallback\n- `orchestrator`: planner coordinates specialists with dependencies\n- `evaluator`: generator + quality gate loop\n\nDetailed templates: `references\u002Fworkflow-patterns.md`\n\n---\n\n## Recommended Workflow\n\n1. Select pattern based on dependency shape and risk profile.\n2. Scaffold config via `scripts\u002Fworkflow_scaffolder.py`.\n3. Define handoff contract fields for every edge.\n4. Add retry\u002Ftimeouts and output validation gates.\n5. Dry-run with small context budgets before scaling.\n\n---\n\n## Common Pitfalls\n\n- Over-orchestrating tasks solvable by one well-structured prompt\n- Missing timeout\u002Fretry policies for external-model calls\n- Passing full upstream context instead of targeted artifacts\n- Ignoring per-step cost accumulation\n\n## Best Practices\n\n1. Start with the smallest pattern that can satisfy requirements.\n2. Keep handoff payloads explicit and bounded.\n3. Validate intermediate outputs before fan-in synthesis.\n4. Enforce budget and timeout limits in every step.\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fengineering\u002Fskills\u002Fagent-workflow-designer","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 agent-workflow-designer",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill agent-workflow-designer",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill agent-workflow-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fagent-workflow-designer\u002FSKILL.md",true,[43,49],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fworkflow-patterns.md","REFERENCE","参考文档",1518,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fagent-workflow-designer\u002Freferences\u002Fworkflow-patterns.md",{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"scripts\u002Fworkflow_scaffolder.py","SCRIPT","脚本",3365,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fagent-workflow-designer\u002Fscripts\u002Fworkflow_scaffolder.py",[56,63,69,76,83,90],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"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":66,"categories":67,"keywords":68,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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",[],[]]