n8n-io n8n
COMMUNITYLABSCO SUMMARY
Nine skills are the operational side: workflow-builder and planning create and edit workflows from a workspace source file, data-table-manager handles the CSV/XLSX/JSON-backed Data Tables feature, debugging-executions reads failed or wrong-output runs, credential-setup-with-computer-use walks a user through fetching OAuth client IDs and secrets from a provider's console, and n8n-cli and n8n-docs-assistant cover instance management and product questions from n8n's own docs. Eighteen more skills, everything carrying the "n8n:" prefix, are for people working on n8n itself: authoring database migrations, adding RBAC scope decorators to REST endpoints, checking whether a community PR is ready for review, writing ESLint rules for the community-node plugin, and drafting Instance-AI eval cases, among others.
If you came here to automate workflows with an agent, the "n8n:" group is not for you and can be ignored entirely; if you're contributing to the n8n repository, the reverse is true. Of the 28 live skills, 10 need nothing beyond the agent, 4 require an account credential, 4 talk to an MCP service, and 7 assume a local tool is already installed; the classifier could not verify the remaining 3.
READ THE FULL ANALYSIS
One skill we can't describe. n8n ships 28 skills, but only 27 carry a description in their frontmatter — the 28th has none, so it isn't represented in the counts above by name. That is a gap in what n8n published, not one we introduced.
ALSO IN THIS PACKAGE
n8n
n8n Claude Code plugin — shared skills, commands, and agents for n8n development
developer
Use this agent for any n8n development task - frontend (Vue 3), backend (Node.js/TypeScript), workflow engine, node creation, or full-stack features. The agent automatically applies n8n conventions and best practices.
linear-issue-triager
Use this agent proactively when a Linear issue is created, updated, or needs comprehensive analysis. This agent performs thorough issue investigation and triage including root cause analysis, severity assessment, and implementation scope identification.
WHAT'S INSIDE
27 showing · 27 totalNothing else to set up — install it and go.
credential-setup-with-computer-use
Opens a real browser and walks through the provider's own website with you to create the keys n8n needs, lifting each secret straight off the page so it is never pasted into a chat.
data-table-manager
n8n can keep its own simple tables of rows and columns, and this looks after them — creating, filling, querying and clearing them — with column names a workflow can still read later.
debugging-executions
When an automation fails, or quietly hands back nothing at all, this tracks down the actual cause and insists on a fresh run to prove the fix instead of declaring victory.
n8n-cli
Operates an n8n automation server from a terminal rather than its web interface, so anything you would otherwise click can be put in a script.
n8n-docs-assistant
Answers a question about setting up or running n8n out of n8n's current documentation, and names the page it came from, rather than reciting it from memory.
n8n:community-pr-readiness-check
The gate an outside contribution passes before a human reviews it — agreement signed, title and description in order, tests present — after which it is routed to a team or closed with a reason.
n8n:content-design
Writes and checks the small pieces of text an interface is made of: button labels, error messages, tooltips, and the screen you see when there is nothing there yet.
n8n:conventions
A cheat sheet of the house rules for writing code inside n8n's own codebase, for when you want the pattern reminded rather than the whole handbook reread.
n8n:create-community-node-lint-rule
Adds a new automatic code check for community-built n8n nodes — the check itself, its tests, its place in the rule list, and its documentation page.
n8n:create-instance-ai-eval
n8n has an AI that builds workflows for its users. This writes a test case for that AI, tried against a real build first so it only goes red when the AI genuinely cannot do the job.
n8n:create-issue
Files a bug or a feature request where n8n's team actually tracks it, written onto their house template in short, plain English.
n8n:create-pr
n8n's build rejects a pull request whose title is not in the house format, so this writes the title and fills in the description before the request is opened.
n8n:create-skill
A skill is a short document that teaches an AI assistant one specific job, and this is how to write one so the assistant actually finds it and follows it.
n8n:db-migrations
Changing n8n's database means writing a migration that has to work on two different database engines and get past a review team — this is the rulebook for getting one through.
n8n:experiments
n8n tries a new editor feature on a slice of its users first, and this handles the code behind one of those trials — from setting it up to deleting it once the trial is over.
n8n:human-like-code-review
Reads a proposed change the way an experienced reviewer would — the problem first, then the code — and leaves the feedback in a file for you to work through.
n8n:linear-issue
Everything hanging off one work ticket, gathered in a single pass: the discussion, the screenshots, the videos turned into text, the linked code, and how big the job looks.
n8n:loom-transcript
Paste the link to a Loom screen recording and get back, in writing, everything that was said in it.
n8n:node-add-oauth
Lets people connect an n8n integration by signing in to the service with their own account, instead of hunting down an API key to paste in.
n8n:protect-endpoints
Every route into n8n has to check what the caller is actually allowed to do, and this is the rule for attaching that check — miss it and you have shipped a way around permissions.
n8n:reproduce-bug
Turns a bug report into a repeatable proof that the bug is real, so the next person is working from evidence rather than a description.
n8n:setup-mcps
Wires an assistant into the ticket tracker, documents and design files an n8n engineer works in day to day.
n8n:spec-driven-development
A feature's written plan is supposed to still be true after the code ships, and this is the discipline of keeping the two honest with each other.
planned-task-runtime
When a long job finishes quietly in the background, this decides what happens next: one clean summary if it worked, another attempt at only the part that failed if it did not.
planning
A request that needs several automations, built in a particular order, gets laid out as a plan and put in front of you before any of it is built.
post-build-flow
The step between an automation being built and an automation being trusted: nothing here counts as working until it has actually run.
workflow-builder
Builds or changes a single n8n automation, written out as code rather than dragged together by hand on the canvas.
HOW TO GET IT
npx skills add n8n-io/n8nnpx skills add n8n-io/n8n --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.