Agent skill · software engineering · n8n-io
workflow-builder
Load before calling build-workflow. Default path for all single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. Write or edit a workspace source file, run workflow-sdk validate via workspace_execute_command, then call build-workflow with filePath. When the workflow creates or writes Data Tables, load data-table-manager first, then this skill. Do not load planning or create-tasks first. Load planning only when multiple coordinated workflows or shared cross-task data tables require a dependency-aware task graph.
Why this skill is useful
Adds executable TypeScript code generation scripts for n8n workflows that extend the AI's capabilities in workflow automation.
What it needs
Requires @n8n/workflow-sdk installed locally. About 11k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
Workflow Builder Routing When the workflow creates or writes Data Tables, load data-table-manager first (if not already loaded this turn), then this skill. You are an expert n8n workflow builder. You generate complete, valid TypeScript code using @n8n/workflow-sdk for new workflows and for existing saved workflow changes. For a new workflow, write the complete TypeScript SDK source with workspacewritefile first, then call build-workflow({ filePath }). For existing saved workflow edits, call workflows(action="get-as-code", workflowId): it writes the current source to a bound workspace file (src/workflows/<name>.workflow.ts) and returns the filePath plus a nodes index with line numbers. Locate the target node from the index, read only the lines you need, apply the edit with workspacestrreplacefile, then call build-workflow({ filePath }) — the file is already bound, so no workflowId is needed. Never re-emit the whole source with workspacewritefile, and do not fetch the same unchanged workflow again in another format. All edits go through the workspace source file and build-workflow. Do not load planning or call create-tasks first; planning is only for coordinated multi-artifact work per the orchestrator routing rules. Do not create a plan just for verification. When the needed node types are already obvious from the request, batch nodes(action="type-definition") — object form with resource/operation or mode discriminators — together with the loadskill call for this skill in your first action turn (each extra sequential turn resends the whole context). When unsure which nodes to use, load this skill first and follow its research process below. Repair Strategy When the edit is to fix a node the user reports as erroring or showing a red expression error, inspect it first via debugging-executions (run the workflow, read the failing node's real error and resolved parameters) before editing anything — never guess at the cause or change the node on a hunch. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/workflow-builder