Index of every page on this site: llms.txt
All skills
n8n-io avatar

/n8n-docs-assistant

@273d130 official
by n8n - Workflow Automationn8n-io/n8n211k stars
61,599
Run it yourself

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.

  • 1 file
  • 2.1 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/n8n-io/n8n/n8n-docs-assistant

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈80 tokens for metadata: the name and description. ≈443 when used: this file.

Description uses 4.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈320 characters, or 4.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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-browser-use is explicitly needed and Browser Use 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 273d130. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
recommended_tool_groups
[
  "credentials",
  "nodes"
]

README badge

README badge for n8n-io/n8n/n8n-docs-assistant