Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool.
Install Workflow Builder
$ npx skills add alirezarezvani/claude-skills --skill workflow-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills workflow-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/workflow-builder/skills/workflow-builder .claude/skills/workflow-builder && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "workflow-builder" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/workflow-builder/skills/workflow-builder into .claude/skills/workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-builder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/engineering/workflow-builder/skills/workflow-builderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-skills --skill workflow-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills workflow-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/workflow-builder/skills/workflow-builder .agents/skills/workflow-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workflow-builder" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/workflow-builder/skills/workflow-builder into .agents/skills/workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-builder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill workflow-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills workflow-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/workflow-builder/skills/workflow-builder .cursor/skills/workflow-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "workflow-builder" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/workflow-builder/skills/workflow-builder into .cursor/skills/workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-builder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path engineering/workflow-builder/skills/workflow-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-skills --skill workflow-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills workflow-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/workflow-builder/skills/workflow-builder .gemini/skills/workflow-builder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "workflow-builder" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/workflow-builder/skills/workflow-builder into .gemini/skills/workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-builder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-skills workflow-builderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-skills --skill workflow-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/workflow-builder/skills/workflow-builder .github/skills/workflow-builder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "workflow-builder" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/workflow-builder/skills/workflow-builder into .github/skills/workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-builder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill workflow-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills workflow-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/workflow-builder/skills/workflow-builder .opencode/skills/workflow-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "workflow-builder" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/workflow-builder/skills/workflow-builder into .opencode/skills/workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-builder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
workflow-builder- GitHub stars
- 28k
- Used in
- 1 other repo
- Token cost
- ~1.3k tokens
- SKILL.md length
- 562 words
- Files
- 15 (incl. scripts, references, assets)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool.
- Works in 3 steps: Ask what kind of workflow they want. Use… → If the user is vague, do NOT stall. Run… → Confirm the shape with the user…
- A user wants to build
- SKILL.md covers ALWAYS start every session…, Decide if a workflow is even…, Build → validate → run loop and Hard rules (validator enforces…, plus 1 more section
- Runs JavaScript and Python scripts from its folder; calls python
What it does
Workflow Builder is an agent skill from alirezarezvani/claude-skills. Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) 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.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files, including scripts, reference files and assets (for example `README.md`, `assets/examples/pr-triage.js` and `assets/templates/fan-out.js`).
It sits in Agent Workflows, covering Subagents. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- A user wants to build
- Run a custom Claude Code workflow
- Orchestrate sub-agents (fan-out
- Automate a repeatable multi-step task across fresh-context agents
Example prompts
- “/workflow-builder”
Requirements
- Python 3
- Node.js
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Ask what kind of workflow they want. Use this opening question set
- 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…
- Confirm the shape with the user (topology + phases + parallel-vs-pipeline) before writing the file. This is the only approval gate.
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (JavaScript and Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Workflow Builder loads about 1.3k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 562 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 562 words, ~1,335 tokens.
Download SKILL.mdSave it as
.claude/skills/workflow-builder/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.- name
- workflow-builder
- description
- Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) 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.
- license
- MIT
- metadata.inspired_by
- https://github.com/ray-amjad/claude-code-workflow-creator (Ray Amjad)
- metadata.targets
- Claude Code Workflow tool (CLAUDE_CODE_WORKFLOWS=1, /workflows)
- metadata.version
- 1.0.0
Workflow Builder
Author 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.
ALWAYS start every session with intake (non-negotiable)
Before proposing or writing any workflow, run the intake. Do not skip to code.
Ask what kind of workflow they want. Use this opening question set:
- What repeatable, multi-step task do you want to automate?
- What is the one unit of work a single sub-agent does once?
- How many units — a known list, or discovered by looping?
- Do later steps need all prior results at once, or can each item flow on its own?
- Does any step need structured data back (a verdict, a list, scores)?
- Roughly how many tokens / how deep should it go?
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:
bash python scripts/workflow_intake.py --task "their description" \ --units unknown --stages unknown --needs-all unknown --structured unknownThe engine returns a recommended topology (fan-out / pipeline / loop / barrier / 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.
Confirm the shape with the user (topology + phases + parallel-vs-pipeline) before writing the file. This is the only approval gate.
See references/decision_and_intake_guide.md for the full question framework, the vague-input playbook, and worked recommendation examples.
Decide if a workflow is even the right tool
| Scenario | Use |
|---|---|
| Single sub-agent, one task | plain Agent tool |
| Reusable procedure, Claude picks steps dynamically | a Skill |
| Many sub-agents in a fixed topology, deterministic + resumable | Workflow ✓ |
Workflows 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.
Show full SKILL.md (252 more words)Show less
Build → validate → run loop
- Scaffold a starter from the confirmed topology:
bash python scripts/scaffold_workflow.py --topology pipeline --name pr-triage \ --description "Triage open PRs" > .claude/workflows/pr-triage.js - Edit the file:
metablock 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/api_reference.md; copy-paste shapes in references/orchestration_patterns.md. - Validate before running — catches the parser-fatal mistakes:
bash python scripts/validate_workflow.py .claude/workflows/pr-triage.js - Run it: enable the feature with
export CLAUDE_CODE_WORKFLOWS=1, save the file under.claude/workflows/, then use/workflowsto launch and watch it live. Press P to pause/resume, X to skip a sub-agent. Failed agents retry automatically.
Hard rules (validator enforces these)
metais a pure literal and the first statement — no variables, spreads, template strings, or function calls inside it.- No non-determinism:
Date.now(),Math.random(), arglessnew Date()break resume — pass timestamps viaargs. - No filesystem / Node APIs (
require,fs,process, network) in the orchestrator — that work belongs insideagent()prompts. parallel()takes thunks (() => agent(...)), not bare promises. Default topipeline()unless a stage needs the whole prior result set.- Guard every open-ended loop with a counter or
budget.remaining()check — unguarded loops hit the 1000-agent cap. - Filter skipped/failed agents:
results.filter(Boolean).
Tooling
scripts/workflow_intake.py— intake recommendation engine (topology + model + budget + rationale from vague input).scripts/validate_workflow.py— stdlib linter for the rules above; PASS / WARN / FAIL with line numbers.scripts/scaffold_workflow.py— generate a starter.jsfor any topology.assets/templates/— fan-out, pipeline, loop-until-budget starters.assets/examples/— a complete runnable workflow.
All scripts run with --sample (no args) and --help.
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 14 other files (scripts, references, assets) in engineering/workflow-builder/skills/workflow-builder of alirezarezvani/claude-skills.
- SKILL.md
- README.md
- assets/examples/pr-triage.js
- assets/templates/fan-out.js
- assets/templates/loop-until-budget.js
- assets/templates/pipeline.js
- expected_outputs/intake_pr_review.json
- expected_outputs/scaffold_pipeline.js
- expected_outputs/validate_sample.txt
- references/api_reference.md
- references/decision_and_intake_guide.md
- references/orchestration_patterns.md
- scripts/scaffold_workflow.py
- scripts/validate_workflow.py
- scripts/workflow_intake.py
Open the folder on GitHubat commit 19392f7
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in alirezarezvani/claude-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Workflow Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Workflow Builder this skillalirezarezvani/claude-skills | 28k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 37k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None | |
| Dispatching Parallel Agentsultralisp/ultralisp | 258 | 40 repos | ~1.5k | Automated safety check: Pass | None | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| Task Observerrebelytics/one-skill-to-rule-them-all | 3.2k | 1 repos | ~12k | Automated safety check: Pass | CC-BY-4.0 |
Similar skills
- Official
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Dispatching Parallel Agents
ultralisp/ultralisp
A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
Task Observer
rebelytics/one-skill-to-rule-them-all
Monitors task execution for skill improvement opportunities.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Workflow Builder
What does Workflow Builder do?
Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool. Workflow Builder is an agent skill from alirezarezvani/claude-skills.claude/workflows/) for Claude Code's Workflow tool.
When should I use Workflow Builder?
Workflow Builder fits situations like: A user wants to build; run a custom Claude Code workflow; orchestrate sub-agents (fan-out; automate a repeatable multi-step task across fresh-context agents.
How do I install Workflow Builder in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill workflow-builder -a claude-code`. Or copy the skill folder (engineering/workflow-builder/skills/workflow-builder in alirezarezvani/claude-skills) into .claude/skills/workflow-builder in your project. Claude Code loads it when a task matches its description.
How do I install Workflow Builder in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill workflow-builder -a codex`. Or copy the skill folder (engineering/workflow-builder/skills/workflow-builder in alirezarezvani/claude-skills) into .agents/skills/workflow-builder in your project. Codex loads it when a task matches its description.
Can I use Workflow Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill workflow-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-builder, .gemini/skills/workflow-builder, .github/skills/workflow-builder and .opencode/skills/workflow-builder in your project.
What does Workflow Builder need to run?
Going by SKILL.md and its folder, Workflow Builder needs JavaScript and Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3; Node.js.
Does Workflow Builder access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Workflow Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Workflow Builder use?
Workflow Builder is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Workflow Builder use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.
What are the alternatives to Workflow Builder?
Skills that share tags, products or a category with Workflow Builder: Claude Code Agent Development (anthropics/claude-plugins-official, 37k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Workflow Builder?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,788 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.