Agent skill · software engineering · n8n-io
n8n:nathan
Deploy a temporary n8n test instance (or generate a local docker run command) via the internal "Nathan" bot, from the repo instead of Slack. Use after opening a PR to offer the user a live test instance, or whenever someone asks to spin up / deploy a test instance for a branch.
Why this skill is useful
Adds specific commands and workflows for deploying n8n test instances that the AI wouldn't reliably generate on its own.
What it needs
Requires localtunnel, pnpm installed locally. Requires n8n account access. About 3k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
Nathan — repo-local test instances Nathan is n8n's internal bot that deploys throwaway test instances from a branch or Docker image. It's normally driven from Slack (/nathan ...); this skill runs the same commands from the repo via pnpm nathan. Prerequisites No tunnel setup needed. Nathan replies asynchronously through a short-lived public tunnel that the script opens for you (npx localtunnel). A deploy to a new test-<name> also polls that instance URL directly, so it still reports success even if the tunnel drops. (Redeploying a name that's already up skips the poll — it can't tell the old instance from the new — so it falls back to the tunnel; prefer a fresh name when you need the reliable report.) A token in ~/.n8n/dev/nathan-token. If a command reports no token, ask the user for one — point them at the form (https://internal.users.n8n.cloud/form/d6d34a2f-4899-4ee8-afc8-f8c41a8a243d), where they log in with their n8n account and copy the token from the response — then save it for them (the script's interactive paste prompt needs a real terminal, so as an agent use the subcommand): Offer a test instance Only when it's worth it Use judgement — don't offer for every branch. Offer when the change is something a person would actually want to click through in a running instance: New features / feature branches UI / editor changes, node changes, workflow-execution or behaviour changes Larger or user-facing diffs Skip the offer (a test instance adds nothing) for: Dev tooling, CI, build config, scripts (like this one) Docs-only or tests-only changes Tiny bug fixes, no-behaviour-change refactors, dependency bumps When skipping, don't nag — at most mention once that a test instance is available on request. Offer after opening a PR, and re-offer on push After you open a PR for a branch that warrants it, offer a live test instance. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/nathan