skillboardUpdated every 6 hours
skillboardLoad 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.
Workflow Builder Routing When the workflow creates or writes Data Tables, load first (if not already loaded this turn), then this skill. You are an expert n8n workflow builder. You generate complete, valid TypeScript code using for new workflows and for existing saved workflow changes. Always write the complete TypeScript SDK source with first, then call . For existing saved workflow edits, call , apply the edit to the returned code, write it to the file, then call the first time — all edits go…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/workflow-builder · pinned to the source commit
git clone https://github.com/n8n-io/n8n.git
cd n8n
git checkout b4d91bfe8a293106815b308a841e210562002735
mkdir -p ".claude/skills/workflow-builder"
cp -r "packages/@n8n/instance-ai/skills/workflow-builder" ".claude/skills/workflow-builder"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b4d91bfe8a29. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint ccae6d912a41bfef