[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MHD1GJ4C6YF0W6EVT2TPDW":3,"skill-same:01M6MHD1GJ4C6YF0W6EVT2TPDW":72},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":13,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6MHD1GJ4C6YF0W6EVT2TPDW","workflow-builder",null,"Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-workflow-builder-skill-3e7278d7\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"workflow","builder","workflow builder","judge","design","scripts","fresh","across","files","context","write","multi-agent","automate","loop","pipeline","orchestrate","code","run","create","workflows","2026-11-10 10:12:30",false,"---\nname: workflow-builder\ndescription: Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.\nlicense: MIT\nmetadata:\n  inspired_by: \"https:\u002F\u002Fgithub.com\u002Fray-amjad\u002Fclaude-code-workflow-creator (Ray Amjad)\"\n  targets: \"Claude Code Workflow tool (CLAUDE_CODE_WORKFLOWS=1, \u002Fworkflows)\"\n  version: 1.0.0\n---\n\n# Workflow Builder\n\nAuthor runnable workflow scripts for Claude Code's Workflow tool: deterministic multi-agent orchestration files (`.js`) that fan work out to fresh-context sub-agents under plain JavaScript control flow. Only leaf `agent()` calls spend tokens, so the main session stays clean and the whole run is resumable.\n\n## ALWAYS start every session with intake (non-negotiable)\n\nBefore proposing or writing any workflow, run the intake. Do not skip to code.\n\n1. **Ask what kind of workflow they want.** Use this opening question set:\n   - What repeatable, multi-step task do you want to automate?\n   - What is the one unit of work a single sub-agent does once?\n   - How many units — a known list, or discovered by looping?\n   - Do later steps need *all* prior results at once, or can each item flow on its own?\n   - Does any step need structured data back (a verdict, a list, scores)?\n   - Roughly how many tokens \u002F how deep should it go?\n\n2. **If the user is vague, do NOT stall.** Run the recommendation engine to turn whatever you have into 1-2 concrete proposals, then present them *with the reasoning*:\n   ```bash\n   python scripts\u002Fworkflow_intake.py --task \"their description\" \\\n     --units unknown --stages unknown --needs-all unknown --structured unknown\n   ```\n   The engine returns a recommended topology (fan-out \u002F pipeline \u002F loop \u002F barrier \u002F judge-panel), model picks, a budget guard, and a one-line rationale per choice. Present those as \"Here's what I'd build and why\" — never ask the user to re-answer questions they already half-answered.\n\n3. **Confirm the shape with the user** (topology + phases + parallel-vs-pipeline) before writing the file. This is the only approval gate.\n\nSee [references\u002Fdecision_and_intake_guide.md](references\u002Fdecision_and_intake_guide.md) for the full question framework, the vague-input playbook, and worked recommendation examples.\n\n## Decide if a workflow is even the right tool\n\n| Scenario | Use |\n|----------|-----|\n| Single sub-agent, one task | plain Agent tool |\n| Reusable procedure, Claude picks steps dynamically | a Skill |\n| Many sub-agents in a fixed topology, deterministic + resumable | **Workflow** ✓ |\n\nWorkflows earn their cost when work is parallel or multi-stage, must be reproducible, long enough to fail halfway (so resume matters), or benefits from isolating each step in its own context window. For one-off tasks, just use Claude directly.\n\n## Build → validate → run loop\n\n1. **Scaffold** a starter from the confirmed topology:\n   ```bash\n   python scripts\u002Fscaffold_workflow.py --topology pipeline --name pr-triage \\\n     --description \"Triage open PRs\" > .claude\u002Fworkflows\u002Fpr-triage.js\n   ```\n2. **Edit** the file: `meta` block first (pure literal, first statement), then the async body using the injected globals — `agent()`, `pipeline()`, `parallel()`, `phase()`, `log()`, `budget`, `args`, `workflow()`. Full surface in [references\u002Fapi_reference.md](references\u002Fapi_reference.md); copy-paste shapes in [references\u002Forchestration_patterns.md](references\u002Forchestration_patterns.md).\n3. **Validate** before running — catches the parser-fatal mistakes:\n   ```bash\n   python scripts\u002Fvalidate_workflow.py .claude\u002Fworkflows\u002Fpr-triage.js\n   ```\n4. **Run** it: enable the feature with `export CLAUDE_CODE_WORKFLOWS=1`, save the file under `.claude\u002Fworkflows\u002F`, then use `\u002Fworkflows` to launch and watch it live. Press **P** to pause\u002Fresume, **X** to skip a sub-agent. Failed agents retry automatically.\n\n## Hard rules (validator enforces these)\n\n- `meta` is a **pure literal** and the **first statement** — no variables, spreads, template strings, or function calls inside it.\n- **No non-determinism:** `Date.now()`, `Math.random()`, argless `new Date()` break resume — pass timestamps via `args`.\n- **No filesystem \u002F Node APIs** (`require`, `fs`, `process`, network) in the orchestrator — that work belongs *inside* `agent()` prompts.\n- `parallel()` takes **thunks** (`() => agent(...)`), not bare promises. Default to `pipeline()` unless a stage needs the whole prior result set.\n- **Guard every open-ended loop** with a counter or `budget.remaining()` check — unguarded loops hit the 1000-agent cap.\n- Filter skipped\u002Ffailed agents: `results.filter(Boolean)`.\n\n## Tooling\n\n- `scripts\u002Fworkflow_intake.py` — intake recommendation engine (topology + model + budget + rationale from vague input).\n- `scripts\u002Fvalidate_workflow.py` — stdlib linter for the rules above; PASS \u002F WARN \u002F FAIL with line numbers.\n- `scripts\u002Fscaffold_workflow.py` — generate a starter `.js` for any topology.\n- `assets\u002Ftemplates\u002F` — fan-out, pipeline, loop-until-budget starters. `assets\u002Fexamples\u002F` — a complete runnable workflow.\n\nAll scripts run with `--sample` (no args) and `--help`.\n","# Workflow Builder\n\nAuthor runnable workflow scripts for Claude Code's Workflow tool: deterministic multi-agent orchestration files (`.js`) that fan work out to fresh-context sub-agents under plain JavaScript control flow. Only leaf `agent()` calls spend tokens, so the main session stays clean and the whole run is resumable.\n\n## ALWAYS start every session with intake (non-negotiable)\n\nBefore proposing or writing any workflow, run the intake. Do not skip to code.\n\n1. **Ask what kind of workflow they want.** Use this opening question set:\n   - What repeatable, multi-step task do you want to automate?\n   - What is the one unit of work a single sub-agent does once?\n   - How many units — a known list, or discovered by looping?\n   - Do later steps need *all* prior results at once, or can each item flow on its own?\n   - Does any step need structured data back (a verdict, a list, scores)?\n   - Roughly how many tokens \u002F how deep should it go?\n\n2. **If the user is vague, do NOT stall.** Run the recommendation engine to turn whatever you have into 1-2 concrete proposals, then present them *with the reasoning*:\n   ```bash\n   python scripts\u002Fworkflow_intake.py --task \"their description\" \\\n     --units unknown --stages unknown --needs-all unknown --structured unknown\n   ```\n   The engine returns a recommended topology (fan-out \u002F pipeline \u002F loop \u002F barrier \u002F judge-panel), model picks, a budget guard, and a one-line rationale per choice. Present those as \"Here's what I'd build and why\" — never ask the user to re-answer questions they already half-answered.\n\n3. **Confirm the shape with the user** (topology + phases + parallel-vs-pipeline) before writing the file. This is the only approval gate.\n\nSee [references\u002Fdecision_and_intake_guide.md](references\u002Fdecision_and_intake_guide.md) for the full question framework, the vague-input playbook, and worked recommendation examples.\n\n## Decide if a workflow is even the right tool\n\n| Scenario | Use |\n|----------|-----|\n| Single sub-agent, one task | plain Agent tool |\n| Reusable procedure, Claude picks steps dynamically | a Skill |\n| Many sub-agents in a fixed topology, deterministic + resumable | **Workflow** ✓ |\n\nWorkflows earn their cost when work is parallel or multi-stage, must be reproducible, long enough to fail halfway (so resume matters), or benefits from isolating each step in its own context window. For one-off tasks, just use Claude directly.\n\n## Build → validate → run loop\n\n1. **Scaffold** a starter from the confirmed topology:\n   ```bash\n   python scripts\u002Fscaffold_workflow.py --topology pipeline --name pr-triage \\\n     --description \"Triage open PRs\" > .claude\u002Fworkflows\u002Fpr-triage.js\n   ```\n2. **Edit** the file: `meta` block first (pure literal, first statement), then the async body using the injected globals — `agent()`, `pipeline()`, `parallel()`, `phase()`, `log()`, `budget`, `args`, `workflow()`. Full surface in [references\u002Fapi_reference.md](references\u002Fapi_reference.md); copy-paste shapes in [references\u002Forchestration_patterns.md](references\u002Forchestration_patterns.md).\n3. **Validate** before running — catches the parser-fatal mistakes:\n   ```bash\n   python scripts\u002Fvalidate_workflow.py .claude\u002Fworkflows\u002Fpr-triage.js\n   ```\n4. **Run** it: enable the feature with `export CLAUDE_CODE_WORKFLOWS=1`, save the file under `.claude\u002Fworkflows\u002F`, then use `\u002Fworkflows` to launch and watch it live. Press **P** to pause\u002Fresume, **X** to skip a sub-agent. Failed agents retry automatically.\n\n## Hard rules (validator enforces these)\n\n- `meta` is a **pure literal** and the **first statement** — no variables, spreads, template strings, or function calls inside it.\n- **No non-determinism:** `Date.now()`, `Math.random()`, argless `new Date()` break resume — pass timestamps via `args`.\n- **No filesystem \u002F Node APIs** (`require`, `fs`, `process`, network) in the orchestrator — that work belongs *inside* `agent()` prompts.\n- `parallel()` takes **thunks** (`() => agent(...)`), not bare promises. Default to `pipeline()` unless a stage needs the whole prior result set.\n- **Guard every open-ended loop** with a counter or `budget.remaining()` check — unguarded loops hit the 1000-agent cap.\n- Filter skipped\u002Ffailed agents: `results.filter(Boolean)`.\n\n## Tooling\n\n- `scripts\u002Fworkflow_intake.py` — intake recommendation engine (topology + model + budget + rationale from vague input).\n- `scripts\u002Fvalidate_workflow.py` — stdlib linter for the rules above; PASS \u002F WARN \u002F FAIL with line numbers.\n- `scripts\u002Fscaffold_workflow.py` — generate a starter `.js` for any topology.\n- `assets\u002Ftemplates\u002F` — fan-out, pipeline, loop-until-budget starters. `assets\u002Fexamples\u002F` — a complete runnable workflow.\n\nAll scripts run with `--sample` (no args) and `--help`.\n",{"name":5,"license":14,"metadata":48,"description":7},{"targets":49,"version":50,"inspired_by":51},"Claude Code Workflow tool (CLAUDE_CODE_WORKFLOWS=1, \u002Fworkflows)","1.0.0","https:\u002F\u002Fgithub.com\u002Fray-amjad\u002Fclaude-code-workflow-creator (Ray Amjad)","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-workflow-builder-skill-3e7278d7","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill workflow-builder",{"tool":64,"command":65},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill workflow-builder",{"tool":67,"command":68},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill workflow-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-workflow-builder-skill-3e7278d7\u002FSKILL.md",true,[],[73,98,125,152,180,215],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":43},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[75,80,81,82,83,39,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"github","ai agents","web","notes","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":43},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[106,107,108,109,110,111,40,112,113,114,115,116,117,118,119,120,121,122,123,124],"vardoger analyze","analyze","directory","cli","github copilot","copilot","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":135,"publishedAt":43},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[131,134],{"categoryNo":132,"categoryName":133,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[136,137,138,139,140,141,142,143,37,144,145,146,147,91,148,31,149,150,96,151],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","ocr","Video","Audio","mp4","images","transformation","free","hls",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":43},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[162,163,164,165,166,167,168,169,170,91,171,172,173,174,175,176,177,178,179,96],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":197,"publishedAt":43},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[186,189,194],{"categoryNo":187,"categoryName":188,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":190,"categoryName":191,"taxonomyType":192,"taxonomyTypeDesc":193},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":195,"categoryName":196,"taxonomyType":192,"taxonomyTypeDesc":193},"01JBSEEDCAT000000000000038","人力资源",[198,199,200,201,202,203,204,205,107,206,91,207,208,209,210,211,212,213,96,214],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":43},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[222,223,224,225,226,201,227,91,211,228,229,230,231,232,233,234,235,236,96,237],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]