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 immediately after an Agent intent, before the first agentbuilder call. Governs how you create, configure, test, and publish n8n Agents yourself with the agentbuilder tools: targeting, prerequisites, initial build, config freshness, interactive setup, models, memory, tools, and reply style. Use directly for…
Load before calling datatables 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…
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error. Also load when a live run you started for the user fails with an error from…
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 embedsother (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an…
Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions — including which OAuth scopes or permissions a provider app needs.
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and workflowbuildercreatetasks silence rules. Load whenever any of these tags appear or after calling workflowbuildercreatetasks.
ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first. If workflowbuildercreatetasks is not visible, load it via loadtool (search "create tasks"). Do NOT use for new one-off workflows…
Load before calling workflowbuilderbuildworkflow. Default path for all single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. Write or edit a workspace source file, run workflow-sdk validate via workspaceexecutecommand, then call…
Load when the request depends on what is already on this instance rather than on what the user just typed: a short or ambiguous opener ("fix it", "carry on", "what should I look at"), a reference to earlier work in a new conversation, or any question about what has recently run or broken.
Load before workflowbuilderbuildworkflow and before scoping or planning new workflows and feature additions, including requests spanning multiple workflows. Implement one increment per user message. Finish setup and inspect a successful real execution before offering another increment. Then wait for the next user…
Offer the three most common automations for a user as a single-choice card, from your own knowledge of their team and their apps, then build the one they choose once they confirm, or offer more. The system preloads it on onboarding threads, where the opening card already asked the user about themselves. Use it on…
★not rated 208k▲
+785
changed todayA87 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: