Guide · Agent skill
How to use the Workflow Creator agent skill (workflow-creator)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The workflow-creator skill is an agent skill for Qwen Code that teaches the agent to write and maintain saved Dynamic Workflows: small JavaScript files that split a task into phases, run sub-agents, and return a final result. This guide explains what the skill does, how to install it, how to trigger it, and what it needs. After reading it you will be able to save a repeatable multi-agent task as a named slash command in your project.
Workflow CreatorQwenLM/qwen-code · Apache-2.0 Download the skill Quick start
- 1Get Qwen Code with Dynamic Workflow. Make sure you use Qwen Code with the Dynamic Workflow feature and the workflow tool available.
- 2Install the skill. Download the ZIP from this page and unzip it into ~/.claude/skills/ or the project's .claude/skills/ folder, or upload it under Settings, Capabilities, Skills in the Claude apps.
- 3Describe the workflow. Ask the agent in plain language to create, save, or edit a Dynamic Workflow, stating the phases and their order.
- 4Review the saved file. The agent writes the script to .qwen/workflows and reads it back to check the name, metadata, phase order, and return value.
- 5Run the slash command. Use the slash command the agent reports, or ask the model to call Workflow with the name in the OpenTUI renderer.
- 6Check the result. Use /workflows with the run ID to view a finished run, or refresh the Saved tab in Web Shell.
What the workflow-creator skill makes the agent do
When the skill is active and you ask the agent to create, save, edit, or reuse a Dynamic Workflow, the agent writes a JavaScript file to your project's .qwen/workflows folder. Each file is exposed as a slash command named after the file. The agent picks a lower-case name, reads the file back to check its name, metadata, phase order, dependency flow, and final return value, and then reports the saved path and the slash command to run.
The skill does not run the workflow unless you ask it to. It also does not manage Task Flow YAML files under qwen-workflow-design, which are a different feature.
Install the workflow-creator skill
Download the ZIP from this page and unzip it into one of two places. For a personal skill available in all your projects, unzip it into ~/.claude/skills/. For a skill that only applies to one project, unzip it into that project's .claude/skills/ folder.
You can also upload the skill in the Claude apps. Open Settings, go to Capabilities, then Skills, and upload the skill there.
The package contains SKILL.md and SKILL.test.ts.
Trigger the skill with natural requests
You do not need a special command to use the skill. Describe what you want in plain language and mention that you want it saved or edited as a workflow. The skill's description says it applies when you ask to create, save, edit, or reuse a Dynamic Workflow, including requests started from the Web Shell Workflows page.
The agent will ask you a question only when the goal, the ordering of phases, or the write scope is materially unclear. Otherwise it creates the smallest script that captures the phases and dependencies you described.
- Save a workflow that reviews a pull request, then summarizes the risks.
- Edit my existing release-check workflow so the tests run before the summary.
- Create a reusable workflow for triaging new bug reports.
What a workflow script looks like
Every saved script starts with a literal metadata declaration that gives the workflow a display name and description. The script then uses sandbox globals such as phase, log, agent, parallel, pipeline, workflow, args, and budget. Each agent gets a complete, scoped prompt and a short label, and the prompt states whether that agent may edit files.
Independent work runs inside parallel, while dependent work runs in sequence with prior results passed explicitly. Every successful path ends with an explicit return of the final result.
- Scripts cannot import modules or access the filesystem, shell, environment, or network directly; required reads and actions belong in agent prompts.
- Variable input goes in args rather than hard-coded values.
- Do not use node --check to validate workflow scripts, because valid scripts may contain top-level await and return.
export const meta = {
name: 'Release readiness',
description: 'Inspect, validate, and summarize a release candidate',
};Run the saved workflow
In the interactive TUI's ink renderer, run the slash command for your workflow. It runs in the foreground: progress appears in the tool card, and completion displays the result and notifies the model. If you need to see a finished run later, use /workflows with the run ID.
In the OpenTUI renderer, the slash command does not yet run client-scheduled tools. There, ask the model to call Workflow with the workflow name instead. In Web Shell, return to Workflows and refresh the Saved tab if it is already open.
/workflows <runId>Safety notes: scripts, network and scope
The skill is documented as not running scripts and not using the network. Workflow scripts themselves cannot read files, run shell commands, or reach the network directly. Any such action is routed through an agent prompt, so review what those prompts ask agents to do before you run a workflow.
By default the skill saves to project scope. It writes to ~/.qwen/workflows only when you explicitly ask for a workflow shared across projects. It will not overwrite an existing workflow with a different design unless you request that, and it will not delete or rename a workflow unless you explicitly ask.
Tips for getting good workflows
Describe the phases in the order they should happen and say which steps depend on earlier results. State whether an agent is allowed to edit files. If you want to change an existing workflow, name it so the agent reads the current file first and preserves unrelated behavior and metadata.
For full sandbox details, load the companion workflow-authoring skill, which the skill recommends before writing anything beyond a trivial script.
- Keep each workflow to one repeatable task so the script stays small.
- Put changing inputs in args so you can reuse the same workflow.
- Commit project workflows in .qwen/workflows to version control to share them with a team.
What people use it for
- Turn a repeatable multi-agent code review into a named slash command that every team member can run.
- Save a release readiness check that inspects, validates, and summarizes a candidate build.
- Build a bug report triage workflow that runs parallel agents and returns one summary.
- Store shared project-level workflow definitions in version control under .qwen/workflows.
- Create a workflow from the Web Shell Workflows page and have the skill save it to the right place.
Frequently asked questions
How do I install the workflow-creator skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for all projects, or into a project's .claude/skills/ folder for one project. You can also upload it in the Claude apps under Settings, Capabilities, Skills.
What do I need to use workflow-creator?
You need Qwen Code with the Dynamic Workflow feature and the workflow tool. The skill also works with the companion workflow-authoring skill, which is the full sandbox reference.
Is workflow-creator free?
The skill is listed under the Apache-2.0 licence from the QwenLM/qwen-code repository. This page does not state any pricing, so check the licence and the project for its terms.
Does the skill run my workflow scripts or use the network?
No. The skill is listed as not running scripts and not using the network. It only writes and checks the workflow file unless you ask it to run the workflow.
Where does the skill save my workflow?
It saves to the project's .qwen/workflows folder by default. It uses ~/.qwen/workflows only when you explicitly ask for a workflow shared across projects.
What is the difference between this and Task Flow YAML?
This skill manages .qwen/workflows JavaScript files. It explicitly excludes qwen-workflow-design YAML files, which are a different feature handled by Task Flow definitions.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use workflow-creator if you already work in Qwen Code and want repeatable multi-agent tasks saved as named slash commands in your project. Pick something else if you do not use Qwen Code or Dynamic Workflow, or if you need scripts that access files, shell, or the network directly, since workflow scripts cannot do that.
Download the skill