n8n Architect
Create, edit, validate, sync, and troubleshoot n8n workflows as TypeScript code, with schema-first node knowledge.
- What
- Create, edit, validate, sync, and troubleshoot n8n workflows as TypeScript code, with schema-first node knowledge.
- Cost
- Free
- Needs
- Prerequisites, read first: Node.js with npx available, and n8n-as-code available through npx. This skill drives `npx --yes n8nac` as its primary interface, and `npx --yes @n8n-as-code/n8n-manager` only for managed local instance lifecycle, tunnels, and workflow presentation. Installing the SKILL.md file alone does NOT give you n8n: without npx and without an n8n environment, the workflow commands will fail. You also need one n8n target, chosen by you: either a remote n8n instance (host URL plus API key) or a managed local instance (Docker is needed for the managed local runtime). No paid service is required for the skill itself.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a skill for treating n8n workflows as code instead of clicking them together in a browser. It drives the n8n-as-code command line, n8nac, through a strict operating loop: resolve the workspace from the backend before touching anything, pull a workflow before editing it, author it as a TypeScript file, validate it locally, push it with verification, then test it and present the resulting link. The discipline that holds the whole thing together is schema first. The agent never guesses a node parameter, an operation, or a type version. It looks up exact node schemas, searches bundled examples for a pattern, and only then writes code, which keeps AI-authored workflows aligned with what the connected n8n version actually supports. Sync is handled the same way code is handled: workflow files stay the source of truth in Git, pull and push keep the local files and the remote instance in step, and conflicts have an explicit handling path instead of a silent overwrite. Environments are explicit too: a remote n8n URL with its own API key, or a managed local instance, each bound to its own workflow folder, with credentials passed through stdin and never printed back. An optional native n8n MCP assist can complement the flow for live discovery and execution inspection, but the skill is clear that it does not replace the local command line, the bundled knowledge, the TypeScript files, or Git. By @EtienneLescot, listed here with credit to its creator. Honest caveats: the repo describes its own scale as 537 nodes with full schemas and 7,700+ templates, figures Skill Harbor has not independently verified; the skill assumes an agent that can run shell commands and Node tooling, and it stops after two repeated failures with the same diagnostic instead of looping; and a public tunnel for a managed local instance must never be enabled unless the user explicitly asks for it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
n8n Architect is a free Muse skill that treats n8n workflows as TypeScript code instead of clicking them together in a browser. It looks up exact node schemas before writing code, validates locally, pushes with verification, and keeps workflow files as the source of truth in Git, so local files and the remote instance stay in step.
Install
Copy the install package below, then paste it into MusePrerequisites, read first: Node.js with npx available, and n8n-as-code available through npx. This skill drives `npx --yes n8nac` as its primary interface, and `npx --yes @n8n-as-code/n8n-manager` only for managed local instance lifecycle, tunnels, and workflow presentation. Installing the SKILL.md file alone does NOT give you n8n: without npx and without an n8n environment, the workflow commands will fail. You also need one n8n target, chosen by you: either a remote n8n instance (host URL plus API key) or a managed local instance (Docker is needed for the managed local runtime). No paid service is required for the skill itself. Install "n8n Architect" for me. A skill for n8n workflows as code: context-root protocol, schema-first node research, TypeScript workflow authoring, local validation, Git-style sync, push with verification, testing, and presentation. Repository folder: https://github.com/EtienneLescot/n8n-as-code/tree/main/skills/n8n-architect 1. Fetch the SKILL.md file from that folder into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). It must never contain hardcoded secrets. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "n8n-architect". 4. Verify with no workflow changes: frontmatter valid, file in place, and `npx --yes n8nac --help` runs. Do NOT create, start, or connect any n8n instance yet, and do NOT enable any public tunnel. 5. Report what was installed, where, and what I still need to do myself: choose a remote n8n URL or a managed local instance, and if remote, provide the host and API key through stdin only (never inline in a shell command, never printed back). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never write n8nac-config.json, managed instance files, or credential files by hand. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.