# N8n Architect

Use when the user explicitly wants to create, edit, validate, sync, or troubleshoot n8n...

- Repository: https://github.com/EtienneLescot/n8n-as-code (1638 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add EtienneLescot/n8n-as-code --skill n8n-architect -g -a claude-code -y`
Codex: `npx skills add EtienneLescot/n8n-as-code --skill n8n-architect -g -a codex -y`
Cursor: `npx skills add EtienneLescot/n8n-as-code --skill n8n-architect -g -a cursor -y`
Gemini CLI: `npx skills add EtienneLescot/n8n-as-code --skill n8n-architect -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add EtienneLescot/n8n-as-code`

## Description

Use when the user explicitly wants to create, edit, validate, sync, or troubleshoot n8n workflows, asks about n8n nodes or automation, or wants to use n8n-as-code in the current context root.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# n8n Architect

Use this skill for all n8n-as-code work: workspace readiness, environments, managed local instances, tunnels, workflow authoring, validation, sync, push, and pull.

Use `{{N8NAC_CMD}}` as the primary interface. Use `{{N8N_MANAGER_CMD}}` only for local managed runtime lifecycle, tunnels, and workflow presentation commands that are explicitly exposed by n8n-manager.

## Context Root Protocol

- Treat the current context root as the directory containing `n8nac-config.json`, `AGENTS.md`, `.agents/skills`, and the configured `workflowsPath`.
- {{N8NAC_CONTEXT_ROOT_HINT}}
- Before any n8n work, first run `{{N8NAC_CMD}} update-ai` from the context root, then read `AGENTS.md`. `update-ai` is designed to create or refresh the n8n-as-code block without destroying existing user or agent instructions.
- Use the exact `n8nac command` and `n8n-manager command` listed in `AGENTS.md`. Those context-root commands override the portable examples in this skill.
- Run every `{{N8NAC_CMD}} env ...`, `{{N8NAC_CMD}} workspace ...`, `{{N8NAC_CMD}} list`, `pull`, `push`, `validate`, `test`, and `update-ai` command from the context root unless the user explicitly gives another context root.
- `AGENTS.md` is bootstrap context only, not a source of configuration truth.
- Do not infer environment, project, or `workflowsPath` from `AGENTS.md`.
- Before n8n work, resolve the effective context from the backend:

```bash
{{N8NAC_CMD}} env status --json
```

- Use the returned `workflowsPath` for workflow files. It is the configured workflow directory for the active environment.
- Do not reconstruct `workflowsPath` from environment name/id, `instanceIdentifier`, `instanceUserIdentifier`, `projectId`, `projectName`, or legacy sync fields.
- Never write `n8nac-config.json`, `~/.n8n-manager`, or n8n-manager secret files by hand.

## Workspace Readiness

Resolve the effective environment through the backend before workflow work:

```bash
{{N8NAC_CMD}} env status --json
```

The rest: https://github.com/EtienneLescot/n8n-as-code/blob/HEAD/packages/skills/src/agent-skills/n8n-architect/SKILL.md