Load before calling workflow_builder_build_workflow. Once the user wants a workflow, load it before you ask about that workflow. Do not load it to ask about a request that does not yet say what to build. Use for new one-off workflows, edits, repairs and post-build verification of one workflow (not requests only to run or inspect a saved workflow), and for its credentials, model choices, evaluations and error workflow. For any other new workflow, load intent-recognition first when it is listed. If the workflow writes Data Tables, load data-table-manager first. Do a one-time request (no repeat or trigger words) now, without asking whether to repeat it; for one node, load one-off-operations and use execute_node.
Authors n8n database migrations. Use when creating or modifying files under packages/@n8n/db/src/migrations/, when the user asks to add a column, table, index, foreign key, or backfill, or when the user mentions DB migrations or TypeORM migrations.
Use the n8n CLI to manage workflows, credentials, executions, and more on an n8n instance. Use when the user asks to interact with n8n, automate workflows, manage credentials, or operate their instance from the command line.
Load before you build any new kept workflow or Agent. It decides which one to build, or what to ask first. Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embeds_other (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an agent tool). Must be used whenever the current turn requires choosing or reconsidering the intent of an automation request, including compound requests, independent automations introduced mid-build, one-off questions or reports that need external systems you cannot query directly, and requests that need clarification before an anchor can be chosen. An explicit Agent request routes to agent-builder before ask_user. Do not load for routine edits or extensions when the conversation already targets a workflow or Agent.
Load before calling the data table tools or parse-file. Use for natural standalone requests like "what data tables do I have?", "show/list my tables", or "what columns are in this table?", and whenever the user asks to list, show, create, inspect, import, seed, query, update, clean up, rename columns in, or delete data tables and rows, especially from CSV/XLSX/JSON attachments. Also load before building or planning workflows that create or write to Data Tables (then load workflow-builder before workflow_builder_build_workflow).
Load immediately after an Agent intent, before the first agent_builder_* call. Governs how you create, configure, test, and publish n8n Agents yourself with the agent_builder_* tools: targeting, prerequisites, initial build, config freshness, interactive setup, models, memory, tools, and reply style. Use directly for routine Agent follow-ups; rerun intent-recognition only when the requested artifact is no longer clear.
Finds repeated manual work in activity records and proposes automations with source evidence. Starts from a team Slack channel, a mailbox, an issue tracker, or supplied work records. The owner reviews each proposal. Use when the user wants automation opportunities found in their own or their team's actual activity: "mine this channel", "what could we automate", "find repeated manual work in these records". Do not use when the user already knows what to build, or wants ideas without granting read access; that is an interview, answer it directly.
Curated setups
Skills grouped for one workflow and installable with one command.