czlonkowski/n8n-skills
7 skills30.2k installs37.3k starsGitHub
Install
npx skills add https://github.com/czlonkowski/n8n-skillsSkills in this repo
1N8n Workflow Patternsn8n-workflow-patterns is a reference skill for solo builders and small teams who automate with n8n instead of writing one-off scripts. It distills six recurring architectures—webhook ingress, REST API glue, database read/write/sync, AI agents with tools and memory, batch jobs, and scheduled tasks—so you pick a structure before dropping nodes. Use it when planning a new workflow, refactoring brittle graphs, or when someone asks to connect SaaS tools, expose an HTTP endpoint, or run periodic jobs. The skill ties each pattern to a recommended flow (triggers, transforms, error handling, and outputs), which speeds agent-assisted workflow generation and reduces dead-end designs. It fits the Build phase most directly but remains relevant when you harden automations in Ship and Operate.7kinstalls2N8n Mcp Tools Expertn8n MCP Tools Expert is the routing layer for solo builders who automate with n8n through the n8n-mcp MCP server and do not want to guess among dozens of tools. It is marked highest priority in the pack because wrong tool choice or wrong nodeType strings waste cycles and produce false validation results. Coverage spans node discovery with detail levels, configuration validation at minimal through strict profiles, workflow create/update/validate flows, template library search, and documentation helpers. You learn when to use search_nodes versus get_node, how AI-friendly validation differs from strict runtime checks, and how multi-output nodes expect branch and case parameters. The skill explicitly depends on the full n8n-mcp tool surface (40+) and points to sibling skills for expressions, patterns, validation interpretation, and node configuration. Five evaluation scenarios are defined with 100% coverage expected. Install it when your agent will build or refactor n8n workflows programmatically rather than only clicking the UI.4.8kinstalls3N8n Node Configurationn8n Node Configuration is an agent skill for solo builders who automate backends with n8n and keep hitting mystery missing fields or validation errors in the node UI. It walks through property dependencies—the displayOptions mechanism in node schemas—so you know when fields appear, when they stay hidden, and how multiple conditions combine with AND logic. You use it while building or extending workflows that call HTTP APIs, CRM nodes, or custom community nodes where sendBody, method, authentication mode, or resource type toggles control the rest of the form. The skill reduces trial-and-error in the visual editor and helps agents generate JSON or fix node parameters that match what the schema actually exposes. It is procedural integration knowledge aimed at Claude Code, Cursor, and Codex users maintaining n8n graphs, not a replacement for n8n’s own node documentation for a specific vendor.4.4kinstalls4N8n Code Javascriptn8n-code-javascript is an agent skill that teaches solo builders how to write reliable JavaScript inside n8n Code nodes. It is for anyone automating lead routing, ETL, notifications, or internal ops who hits confusing `$json` shapes, wrong return formats, or loop bugs in SplitInBatches. The skill walks through mode selection, the full input API, HTTP via `$helpers`, date math with DateTime, and constraints when environment access or authenticated helpers are disabled. Use it whenever a workflow needs custom logic that stock nodes cannot express—aggregation, format conversion, batch filtering, or outbound API calls—so agents stop guessing n8n-specific semantics. It complements n8n expression skills by focusing on imperative JS, which is where most production workflows break in subtle ways.4kinstalls5N8n Validation Expertn8n-validation-expert is a checker skill for solo builders and small teams automating ops with n8n through AI agents. When validation tools return JSON error payloads, agents often churn on cosmetic warnings or mis-parse operator shapes; this skill encodes n8n’s validation philosophy—validate early, validate often—and walks through severity levels, fix hints, and which feedback blocks activation versus which can be deferred. It is built for the loop after programmatic workflow edits: expect multiple passes, short diagnosis time, and targeted field fixes rather than rewriting whole graphs. Use it while composing integrations in build, and again in ship when hardening workflows before go-live. Intermediate to advanced: you should already invoke n8n validation from your agent toolchain. It does not replace n8n docs for node-specific parameters but sharpens interpretation so fewer iterations waste tokens.3.8kinstalls6N8n Expression Syntaxn8n Expression Syntax is a focused agent skill for solo builders automating ops with n8n. Dynamic fields must use double curly braces; omit them and n8n stores `$json.email` as plain text, which is the top cause of “workflow runs but data is empty” bugs. The skill walks through `$json` for the current item, `$node["Exact Node Name"].json` for upstream steps, bracket notation for spaced keys, and safe nesting into arrays and webhook bodies. It is meant to be invoked while you map CRM rows, stripe webhooks, or internal APIs—not as a full workflow designer. Pair it with broader n8n node skills when you already know which integrations you need but expressions keep failing validation or runtime checks. Intermediate builders shipping internal agents or lightweight SaaS back-office flows get the fastest payoff when every branch references the right payload shape.3.6kinstalls7N8n Code Pythonn8n-code-python is a focused agent skill for solo builders who run n8n as their glue layer and need Python snippets that actually work inside beta Python Code nodes. The skill front-loads an honest default: JavaScript fits roughly ninety-five percent of n8n tasks because helper functions and Luxon are fully supported, while Python is reserved for explicit user requests or standard-library strengths like regex, hashlib, or statistics. When Python is the right call, you get canonical patterns for reading all items via _input, mutating json payloads, and returning the list structure n8n expects. That reduces trial-and-error around underscore-prefixed globals and keeps agents from hallucinating Node-style APIs in a constrained sandbox. Treat it as implementation guardrails during workflow builds—pair with your existing n8n JavaScript skill when agents default to the wrong language. It does not provision n8n hosting or design entire workflows end to end; it makes Python Code nodes correct and idiomatic.2.6kinstalls