Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Load n8n-docs via load_tool before calling it (search "n8n docs" if not visible). Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions opened from the credential modal.
Install
npx skillscat add n8n-io/n8n/n8n-docs-assistant Install via the SkillsCat registry.
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.
Before calling n8n-docs, load it via load_tool (search "n8n docs" if it is
not visible).
Default Procedure
- Load
n8n-docsviaload_toolif needed, then calln8n-docs(action="lookup")
first for credential setup and direct n8n docs questions. Usesearchthenreadonly when you need tighter control over candidate pages. - For credential setup, pass
intent: "credential-setup"and all available
context fields:credentialType,credentialDisplayName,documentationUrl,oauthRedirectUrl, andnodeType. - Read the returned document snippets before answering. If multiple pages were
returned, prefer credential-specific pages over general credential UI pages. - End the final answer with
Source: [Page title](page URL)when one docs
page was used, orSources:when multiple docs pages were used. Use only
pages returned byn8n-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 unlessoauthRedirectUrlis 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 unlesscredential-setup-with-computer-useis
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.