Agent skill · n8n-io
agent-builder
Load before calling build-agent for a new or existing n8n Agent. Governs prerequisite creation, faithful handoff of the user's request, agent targeting across turns, builder questions, testing, and publishing. Use directly for routine follow-ups when the conversation already targets an Agent; rerun intent-recognition only when the requested artifact is no longer clear.
What it needs
About 4k tokens when loaded.
What this skill does
Agent Builder Routing Use this skill after intent-recognition chooses an agent-anchored design, or when the conversation already targets an Agent and the user is continuing that build. Do not rerun intent recognition for routine Agent edits or extensions. Use build-agent only for Agent artifacts. When the conversation opens from an existing Agent in the editor and the user asks to change its configuration or capabilities, that is an agent-anchored request — target that Agent and call build-agent. Do not reroute to workflow-builder, and do not spawn a workflow to satisfy a capability change on the Agent. Supported channels & unsupported requests list-agent-capabilities returns every chat channel n8n Agents support, each with capabilities, useIntegrationWhen, and useNodeToolWhen. It is the authoritative source the orchestrator can read before building; a channel absent from its result is unsupported for agents. When the user asks for a channel that is not supported (e.g. WhatsApp, Microsoft Teams), do not forward it to the builder as a channel to configure and do not fake it by adding the platform as an agent tool. Explain the channel is unsupported for agents, offer the supported alternatives, and ask which to use — or whether the user explicitly wants that unsupported platform as the conversation surface, in which case offer the agent-entrypoint workflow bridge described in Prerequisites (it connects the platform trigger to Message an Agent; it is not a channel config). Only forward a channel to build-agent once it is a supported type or the user has chosen an alternative. Faithful handoff Treat message as a faithful handoff of the user's request, not an Agent build specification authored by you. Forward the user's wording as close to verbatim as possible. Include only: Requirements, constraints, and implementation choices the user explicitly stated. Explicit answers or decisions from earlier turns that are necessary for the current request. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/agent-builder