n8n Code Node JavaScript
czlonkowski/n8n-skills
Guides writing JavaScript in n8n Code nodes: picking an execution mode, reading input data, returning items, using built-in helpers and avoiding common errors.
Helps your agent write and edit Windmill workflow-as-code scripts built from workflow, task, step, sleep and approval calls, and then preview them locally.
Install Windmill Workflow-as-Code Scripts
$ npx skills add windmill-labs/windmill --skill write-workflow-as-code -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install windmill-labs/windmill write-workflow-as-code --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/windmill-labs/windmill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/system_prompts/auto-generated/skills/write-workflow-as-code .claude/skills/write-workflow-as-code && 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 "write-workflow-as-code" agent skill from https://github.com/windmill-labs/windmill/tree/main/system_prompts/auto-generated/skills/write-workflow-as-code into .claude/skills/write-workflow-as-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-workflow-as-code", 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/windmill-labs/windmill/tree/main/system_prompts/auto-generated/skills/write-workflow-as-codeType 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 windmill-labs/windmill --skill write-workflow-as-code -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install windmill-labs/windmill write-workflow-as-code --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/system_prompts/auto-generated/skills/write-workflow-as-code .agents/skills/write-workflow-as-code && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-workflow-as-code" agent skill from https://github.com/windmill-labs/windmill/tree/main/system_prompts/auto-generated/skills/write-workflow-as-code into .agents/skills/write-workflow-as-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-workflow-as-code", 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 windmill-labs/windmill --skill write-workflow-as-code -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install windmill-labs/windmill write-workflow-as-code --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/system_prompts/auto-generated/skills/write-workflow-as-code .cursor/skills/write-workflow-as-code && 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 "write-workflow-as-code" agent skill from https://github.com/windmill-labs/windmill/tree/main/system_prompts/auto-generated/skills/write-workflow-as-code into .cursor/skills/write-workflow-as-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-workflow-as-code", 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/windmill-labs/windmill.git --path system_prompts/auto-generated/skills/write-workflow-as-code--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 windmill-labs/windmill --skill write-workflow-as-code -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install windmill-labs/windmill write-workflow-as-code --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/system_prompts/auto-generated/skills/write-workflow-as-code .gemini/skills/write-workflow-as-code && 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 "write-workflow-as-code" agent skill from https://github.com/windmill-labs/windmill/tree/main/system_prompts/auto-generated/skills/write-workflow-as-code into .gemini/skills/write-workflow-as-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-workflow-as-code", 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 windmill-labs/windmill write-workflow-as-codeInstalls 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 windmill-labs/windmill --skill write-workflow-as-code -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .github/skills && cp -r skills-src/system_prompts/auto-generated/skills/write-workflow-as-code .github/skills/write-workflow-as-code && 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 "write-workflow-as-code" agent skill from https://github.com/windmill-labs/windmill/tree/main/system_prompts/auto-generated/skills/write-workflow-as-code into .github/skills/write-workflow-as-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-workflow-as-code", 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 windmill-labs/windmill --skill write-workflow-as-code -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install windmill-labs/windmill write-workflow-as-code --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/system_prompts/auto-generated/skills/write-workflow-as-code .opencode/skills/write-workflow-as-code && 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 "write-workflow-as-code" agent skill from https://github.com/windmill-labs/windmill/tree/main/system_prompts/auto-generated/skills/write-workflow-as-code into .opencode/skills/write-workflow-as-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-workflow-as-code", 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
write-workflow-as-code- GitHub stars
- 18k
- Token cost
- ~7.9k tokens
- SKILL.md length
- 1,753 words
- Files
- 1
- Skills in repo
- 42
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Helps your agent write and edit Windmill workflow-as-code scripts built from workflow, task, step, sleep and approval calls, and then preview them locally.
- Writing a Windmill workflow that waits for an approval before continuing
- SKILL.md covers CLI Commands, Scope, File Shape and Checkpoint And Replay Model, plus 7 more sections
- Calls git
- Modifying an existing workflow-as-code script that uses tasks and steps
What it does
The skill targets scripts that define a Windmill workflow in code. It names the building blocks workflow, task, step, sleep and approvals, together with the taskScript and taskFlow helpers and their snake_case forms task_script and task_flow, and it applies whenever one of those is being written or modified.
Around the code itself, the agent follows a fixed way of using the wmill CLI. A local edit is tried with script preview, the deployed copy is only invoked with script run when you ask for it, and nothing is pushed unless you say deploy, publish or ship. After imports or main's arguments change, generate-metadata is rerun so the input schema, lock and wmill-lock.yaml do not drift and cause noisy diffs in git sync and CI.
When your agent uses it
- Writing a Windmill workflow that waits for an approval before continuing
- Modifying an existing workflow-as-code script that uses tasks and steps
- Adding a sleep between steps of a scripted workflow
Example prompts
- “Create a Windmill workflow script that runs two tasks in order and then waits for approval.”
- “Edit the onboarding workflow so it sleeps between its second and third step.”
- “Preview the local copy of my workflow script without deploying it.”
Requirements
- The wmill CLI
- A Windmill workspace
What it can do on your machine
Read from SKILL.md and the folder at commit eab3dd5. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Windmill Workflow-as-Code Scripts loads about 7.9k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 1,753 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); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,753 words (~7,923 tokens).
- name
- write-workflow-as-code
Files
Just SKILL.md in system_prompts/auto-generated/skills/write-workflow-as-code of windmill-labs/windmill.
Open the folder on GitHubat commit eab3dd5
Compare with similar skills
Windmill Workflow-as-Code Scripts 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 |
|---|---|---|---|---|---|---|
| Windmill Workflow-as-Code Scripts this skillwindmill-labs/windmill | 18k | — | ~7.9k | Automated safety check: Pass | Custom licence | |
| n8n Code Node JavaScriptczlonkowski/n8n-skills | 6.4k | — | ~4.9k | Automated safety check: Pass | MIT | |
| GitHub Star Managercat-xierluo/legal-skills | 713 | — | ~2k | Automated safety check: Notes | MIT | |
| Stp AutomationJoelLewis/finance_skills | 205 | — | ~7.8k | Automated safety check: Pass | MIT | |
| Manor Workspace Architecturemanor-os/manor-ai | 161 | — | ~756 | Automated safety check: Pass | Custom licence | |
| Workflow AutomatorOneWave-AI/claude-skills | 322 | — | ~984 | Automated safety check: Pass | MIT |
Similar skills
GitHub Star Manager
cat-xierluo/legal-skills
Finds GitHub projects mentioned in articles or screenshots and stars them, tracks updates to your starred repos, and builds an HTML dashboard to browse them.
Stp Automation
JoelLewis/finance_skills
Measure and raise straight-through processing (STP) rates in securities operations through zero-touch, exception-based processing.
Manor Workspace Architecture
manor-os/manor-ai
A skill your agent uses when changing, debugging, reviewing, documenting, or testing Manor Workspace behavior, especially when a change crosses chat, Strategist, Proposal, Task, Plan, Workflow…
Workflow Automator
OneWave-AI/claude-skills
Takes a manual business workflow description and designs the automated version.
Skyvern Browser Automation
Skyvern-AI/skyvern
Picks the right Skyvern CLI command for a web task, from quick yes/no checks to reusable multi-page workflows, instead of falling back to plain page fetching.
More from windmill-labs/windmill
All 42 skills in this repoWindmill Trigger Type Checklist
windmill-labs/windmill
Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.
Windmill AI Evals
windmill-labs/windmill
Writes and runs black-box benchmark cases for Windmill's flow, app, script, CLI and global AI generation modes, including before-and-after comparisons.
Domain Modeling and Glossary
windmill-labs/windmill
Actively challenges vague or conflicting terminology as you design, and keeps a living domain glossary file up to date in real time.
Local PR Review
windmill-labs/windmill
Runs the same code review locally that GitHub's auto-review actions run on a PR, delegating to a fresh-context subagent so the review isn't biased by the main session's own reasoning.
Draft PR with CI Rounds
windmill-labs/windmill
Opens a draft GitHub pull request with a conventional title and explicit body, then drives CI review rounds before marking it ready.
Windmill Dev Page Preview
windmill-labs/windmill
Opens the Windmill dev page to preview a flow, script or app, choosing between proxy and direct mode and deciding whether the agent or the runtime starts the wmill dev server.
Related
Categories
Questions about Windmill Workflow-as-Code Scripts
What does Windmill Workflow-as-Code Scripts do?
Helps your agent write and edit Windmill workflow-as-code scripts built from workflow, task, step, sleep and approval calls, and then preview them locally. The skill targets scripts that define a Windmill workflow in code. It names the building blocks workflow, task, step, sleep and approvals, together with the taskScript and taskFlow helpers and their snake_case forms task_script and task_flow, and it applies whenever one of those is being written or modified.
When should I use Windmill Workflow-as-Code Scripts?
Windmill Workflow-as-Code Scripts fits situations like: writing a Windmill workflow that waits for an approval before continuing; modifying an existing workflow-as-code script that uses tasks and steps; adding a sleep between steps of a scripted workflow.
How do I install Windmill Workflow-as-Code Scripts in Claude Code?
Run `npx skills add windmill-labs/windmill --skill write-workflow-as-code -a claude-code`. Or copy the skill folder (system_prompts/auto-generated/skills/write-workflow-as-code in windmill-labs/windmill) into .claude/skills/write-workflow-as-code in your project. Claude Code loads it when a task matches its description.
How do I install Windmill Workflow-as-Code Scripts in Codex?
Run `npx skills add windmill-labs/windmill --skill write-workflow-as-code -a codex`. Or copy the skill folder (system_prompts/auto-generated/skills/write-workflow-as-code in windmill-labs/windmill) into .agents/skills/write-workflow-as-code in your project. Codex loads it when a task matches its description.
Can I use Windmill Workflow-as-Code Scripts 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 windmill-labs/windmill --skill write-workflow-as-code -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-workflow-as-code, .gemini/skills/write-workflow-as-code, .github/skills/write-workflow-as-code and .opencode/skills/write-workflow-as-code in your project.
What does Windmill Workflow-as-Code Scripts need to run?
Going by SKILL.md and its folder, Windmill Workflow-as-Code Scripts needs the command-line tools its instructions call (git). Our summary lists: The wmill CLI; A Windmill workspace.
Does Windmill Workflow-as-Code Scripts access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Windmill Workflow-as-Code Scripts 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. Review the folder before installing.
What licence does Windmill Workflow-as-Code Scripts use?
Windmill Workflow-as-Code Scripts has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Windmill Workflow-as-Code Scripts use?
About 7.9k tokens (SKILL.md is roughly 32k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Windmill Workflow-as-Code Scripts?
Skills that share tags, products or a category with Windmill Workflow-as-Code Scripts: n8n Code Node JavaScript (czlonkowski/n8n-skills, 6.4k stars), GitHub Star Manager (cat-xierluo/legal-skills, 713 stars), Stp Automation (JoelLewis/finance_skills, 205 stars) and Manor Workspace Architecture (manor-os/manor-ai, 161 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Windmill Workflow-as-Code Scripts?
windmill-labs (a GitHub organization) maintains it in windmill-labs/windmill, which has 18,117 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on October 7, 2026.
Source: windmill-labs/windmill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.