CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

n8n-docs-assistant

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.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured instruction skill: it specifies exact tool-call parameters, context fields, output citation format, and failure handling without padding. The only trims are the duplicated intro line and the under-specified search/read path.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no concept explanations, but the opening paragraph ('Use this skill when the user asks how to configure, set up, troubleshoot, or understand n8n behavior') nearly duplicates the frontmatter description and could be trimmed, matching anchor 4 rather than 5.

4 / 5

Actionability

The primary path is executable with exact call syntax ('n8n-docs(action="lookup")', 'intent: "credential-setup"', named context fields, and a concrete citation format), but the 'search'/'read' alternative is only loosely specified ('Use search then read only when you need tighter control') without call syntax, matching anchor 4 (minor gaps) rather than 5.

4 / 5

Workflow Clarity

The Default Procedure is a clearly sequenced 4-step workflow with an explicit checkpoint ('Read the returned document snippets before answering. If multiple pages were returned, prefer credential-specific pages') and an error-recovery fallback in the Missing Docs section, matching anchor 5. This is a non-destructive docs-lookup skill, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no bundle files, and organized into clear sections (Default Procedure, Credential Setup, Missing Docs); per the simple-skill scoring note, well-organized sections with no need for external references score 5.

5 / 5

Total

18

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names a clear n8n-specific niche, uses third-person voice, and pairs a concrete 'what' with an explicit 'Use when' trigger clause including credential-setup specifics. Trigger coverage is good but could add common n8n user vocabulary like 'workflow' or 'self-host'.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas ('product, setup, credential, node, hosting, API, and usage questions') and a specific action ('which OAuth scopes or permissions a provider app needs'), but the primary verb 'Answers ... questions' is slightly generic, matching anchor 4 rather than the fully comprehensive anchor 5.

4 / 5

Completeness

It clearly answers both 'what' ('Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs') and 'when' with explicit concrete trigger phrases ('Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior'), matching anchor 5; it exceeds anchor 4 because the 'when' clause is explicit and detailed rather than vague.

5 / 5

Trigger Term Quality

Natural user phrases are well covered ('configure, set up, troubleshoot', 'credential setup', 'OAuth scopes or permissions'), but common n8n terms a user would naturally say such as 'workflow', 'automation', or 'self-host' are absent, matching anchor 4 (good coverage, a few natural terms missing) rather than 5.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — every clause is anchored to 'n8n' and its docs, including niche triggers like 'which OAuth scopes or permissions a provider app needs' — so conflict with other skills is minimal, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

n8n-io/n8n

Path

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

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.