n8n-docs-assistant

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗

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.

packages/@n8n/instance-ai/skills/n8n-docs-assistant/SKILL.md

Download bundle ↓
master · 8bff5da1 bundle fileScanned 2026-09-15

SKILL.md

507 tokens · o200k_base · 2,201 bytes

n8n Docs Assistant

Use this skill when the user asks how to configure, set up, troubleshoot, or understand n8n behavior and the answer should come from current n8n docs.

Default Procedure

  1. Call n8n-docs(action="lookup") first for credential setup and direct n8n docs questions. Use search then read only when you need tighter control over candidate pages.
  2. For credential setup, pass intent: "credential-setup" and all available context fields: credentialType, credentialDisplayName, documentationUrl, oauthRedirectUrl, and nodeType.
  3. Read the returned document snippets before answering. If multiple pages were returned, prefer credential-specific pages over general credential UI pages.
  4. End the final answer with Source: [Page title](page URL) when one docs page was used, or Sources: when multiple docs pages were used. Use only pages returned by n8n-docs.

Credential Setup

  • Keep the answer tied to the credential modal the user is viewing.
  • If the setup needs an OAuth redirect/callback URL, tell the user to copy the OAuth Redirect URL from the modal unless oauthRedirectUrl is available in context.
  • If the answer involves secret values, tell the user where to paste them in the credential modal, but never ask them to paste secrets into chat.
  • For external provider console steps, summarize the n8n docs instructions. Do not navigate browser pages unless credential-setup-with-computer-use is explicitly needed and Computer Use browser tools are available.

Missing Docs

If docs lookup fails, say that current docs could not be loaded. Provide only generic n8n UI guidance that is visible from the product context, and avoid claiming provider-specific setup steps without docs evidence.

Discovery context

Discovered by repository scan. No exact path reference found in the snapshot’s root AGENTS.md.