Agent skill

N8n Node Configuration

by davila7 in davila7/claude-code-templates

Operation-aware node configuration guidance. An agent skill from davila7/claude-code-templates.

MITAuto-check passedProductivity & Automation

Install N8n Node Configuration

skills CLI
$ npx skills add davila7/claude-code-templates --skill n8n-node-configuration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davila7/claude-code-templates n8n-node-configuration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/workflow-automation/n8n/n8n-node-configuration .claude/skills/n8n-node-configuration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
n8n-node-configuration
GitHub stars
32k
Used in
1 other repo
Token cost
~4k tokens
SKILL.md length
772 words
Files
4
Skills in repo
477
Repo updated
First seen
Licence
MIT

At a glance

Operation-aware node configuration guidance. An agent skill from davila7/claude-code-templates.

  • Works in 3 steps: Operation-Aware Configuration → Property Dependencies → Progressive Discovery
  • Configuring nodes
  • SKILL.md covers Configuration Philosophy, Core Concepts, Configuration Workflow and get_node_essentials vs…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

N8n Node Configuration is an agent skill from davila7/claude-code-templates. Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between getnodeessentials and getnodeinfo, or learning common configuration patterns by node type.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `DEPENDENCIES.md`, `OPERATION_PATTERNS.md` and `README.md`).

It sits in Productivity & Automation, covering Workflow automation. It works with n8n. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.

When your agent uses it

  • Configuring nodes
  • Understanding property dependencies
  • Determining required fields
  • Choosing between getnodeessentials and getnodeinfo

Example prompts

  • “/n8n-node-configuration”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Operation-Aware Configuration
  2. Property Dependencies
  3. Progressive Discovery

What it can do on your machine

Read from SKILL.md and the folder at commit 14680ec. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

N8n Node Configuration loads about 4k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 772 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davila7/claude-code-templates at commit 14680ec, republished under its MIT licence (© davila7). 772 words, ~4,015 tokens.

Download SKILL.mdSave it as .claude/skills/n8n-node-configuration/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
n8n-node-configuration
description
Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node_essentials and get_node_info, or learning common configuration patterns by node type.

n8n Node Configuration

Expert guidance for operation-aware node configuration with property dependencies.


Configuration Philosophy

Progressive disclosure: Start minimal, add complexity as needed

Configuration best practices:

  • get_node_essentials is the most used discovery pattern
  • 56 seconds average between configuration edits
  • 91.7% success rate with essentials-based configuration

Key insight: Most configurations need only essentials, not full schema!


Core Concepts

1. Operation-Aware Configuration

Not all fields are always required - it depends on operation!

Example: Slack node

javascript
// For operation='post'
{
  "resource": "message",
  "operation": "post",
  "channel": "#general",  // Required for post
  "text": "Hello!"        // Required for post
}

// For operation='update'
{
  "resource": "message",
  "operation": "update",
  "messageId": "123",     // Required for update (different!)
  "text": "Updated!"      // Required for update
  // channel NOT required for update
}

Key: Resource + operation determine which fields are required!

2. Property Dependencies

Fields appear/disappear based on other field values

Example: HTTP Request node

javascript
// When method='GET'
{
  "method": "GET",
  "url": "https://api.example.com"
  // sendBody not shown (GET doesn't have body)
}

// When method='POST'
{
  "method": "POST",
  "url": "https://api.example.com",
  "sendBody": true,       // Now visible!
  "body": {               // Required when sendBody=true
    "contentType": "json",
    "content": {...}
  }
}

Mechanism: displayOptions control field visibility

3. Progressive Discovery

Use the right tool for the right job:

  1. get_node_essentials (91.7% success rate)

    • Quick overview
    • Required fields
    • Common options
    • Use first - covers 90% of needs
  2. get_property_dependencies (for complex nodes)

    • Shows what fields depend on others
    • Reveals conditional requirements
    • Use when essentials isn't enough
  3. get_node_info (full schema)

    • Complete documentation
    • All possible fields
    • Use when essentials + dependencies insufficient

Configuration Workflow

Standard Process
1. Identify node type and operation
   ↓
2. Use get_node_essentials
   ↓
3. Configure required fields
   ↓
4. Validate configuration
   ↓
5. If dependencies unclear → get_property_dependencies
   ↓
6. Add optional fields as needed
   ↓
7. Validate again
   ↓
8. Deploy
Example: Configuring HTTP Request

Step 1: Identify what you need

javascript
// Goal: POST JSON to API

Step 2: Get essentials

javascript
const info = get_node_essentials({
  nodeType: "nodes-base.httpRequest"
});

// Returns: method, url, sendBody, body, authentication required/optional

Step 3: Minimal config

javascript
{
  "method": "POST",
  "url": "https://api.example.com/create",
  "authentication": "none"
}

Step 4: Validate

javascript
validate_node_operation({
  nodeType: "nodes-base.httpRequest",
  config,
  profile: "runtime"
});
// → Error: "sendBody required for POST"

Step 5: Add required field

javascript
{
  "method": "POST",
  "url": "https://api.example.com/create",
  "authentication": "none",
  "sendBody": true
}

Step 6: Validate again

javascript
validate_node_operation({...});
// → Error: "body required when sendBody=true"

Step 7: Complete configuration

javascript
{
  "method": "POST",
  "url": "https://api.example.com/create",
  "authentication": "none",
  "sendBody": true,
  "body": {
    "contentType": "json",
    "content": {
      "name": "={{$json.name}}",
      "email": "={{$json.email}}"
    }
  }
}

Step 8: Final validation

javascript
validate_node_operation({...});
// → Valid! ✅

get_node_essentials vs get_node_info

Use get_node_essentials When:

✅ Starting configuration (91.7% success rate)

javascript
get_node_essentials({
  nodeType: "nodes-base.slack"
});

Returns:

  • Required fields
  • Common options
  • Basic examples
  • Operation list

Fast: ~18 seconds average (from search → essentials)

Use get_node_info When:

✅ Essentials insufficient

javascript
get_node_info({
  nodeType: "nodes-base.slack"
});

Returns:

  • Full schema
  • All properties
  • Complete documentation
  • Advanced options

Slower: More data to process

Decision Tree
┌─────────────────────────────────┐
│ Starting new node config?       │
├─────────────────────────────────┤
│ YES → get_node_essentials       │
└─────────────────────────────────┘
         ↓
┌─────────────────────────────────┐
│ Essentials has what you need?   │
├─────────────────────────────────┤
│ YES → Configure with essentials │
│ NO  → Continue                  │
└─────────────────────────────────┘
         ↓
┌─────────────────────────────────┐
│ Need dependency info?           │
├─────────────────────────────────┤
│ YES → get_property_dependencies │
│ NO  → Continue                  │
└─────────────────────────────────┘
         ↓
┌─────────────────────────────────┐
│ Still need more details?        │
├─────────────────────────────────┤
│ YES → get_node_info             │
└─────────────────────────────────┘

Property Dependencies Deep Dive

displayOptions Mechanism

Fields have visibility rules:

javascript
{
  "name": "body",
  "displayOptions": {
    "show": {
      "sendBody": [true],
      "method": ["POST", "PUT", "PATCH"]
    }
  }
}

Translation: "body" field shows when:

  • sendBody = true AND
  • method = POST, PUT, or PATCH
Common Dependency Patterns
Pattern 1: Boolean Toggle

Example: HTTP Request sendBody

javascript
// sendBody controls body visibility
{
  "sendBody": true   // → body field appears
}
Pattern 2: Operation Switch

Example: Slack resource/operation

javascript
// Different operations → different fields
{
  "resource": "message",
  "operation": "post"
  // → Shows: channel, text, attachments, etc.
}

{
  "resource": "message",
  "operation": "update"
  // → Shows: messageId, text (different fields!)
}
Pattern 3: Type Selection

Example: IF node conditions

javascript
{
  "type": "string",
  "operation": "contains"
  // → Shows: value1, value2
}

{
  "type": "boolean",
  "operation": "equals"
  // → Shows: value1, value2, different operators
}
Using get_property_dependencies

Example:

javascript
const deps = get_property_dependencies({
  nodeType: "nodes-base.httpRequest"
});

// Returns dependency tree
{
  "dependencies": {
    "body": {
      "shows_when": {
        "sendBody": [true],
        "method": ["POST", "PUT", "PATCH", "DELETE"]
      }
    },
    "queryParameters": {
      "shows_when": {
        "sendQuery": [true]
      }
    }
  }
}

Use this when: Validation fails and you don't understand why field is missing/required


Common Node Patterns

Pattern 1: Resource/Operation Nodes

Examples: Slack, Google Sheets, Airtable

Structure:

javascript
{
  "resource": "<entity>",      // What type of thing
  "operation": "<action>",     // What to do with it
  // ... operation-specific fields
}

How to configure:

  1. Choose resource
  2. Choose operation
  3. Use get_node_essentials to see operation-specific requirements
  4. Configure required fields
Pattern 2: HTTP-Based Nodes

Examples: HTTP Request, Webhook

Structure:

javascript
{
  "method": "<HTTP_METHOD>",
  "url": "<endpoint>",
  "authentication": "<type>",
  // ... method-specific fields
}

Dependencies:

  • POST/PUT/PATCH → sendBody available
  • sendBody=true → body required
  • authentication != "none" → credentials required
Pattern 3: Database Nodes

Examples: Postgres, MySQL, MongoDB

Structure:

javascript
{
  "operation": "<query|insert|update|delete>",
  // ... operation-specific fields
}

Dependencies:

  • operation="executeQuery" → query required
  • operation="insert" → table + values required
  • operation="update" → table + values + where required
Pattern 4: Conditional Logic Nodes

Examples: IF, Switch, Merge

Structure:

javascript
{
  "conditions": {
    "<type>": [
      {
        "operation": "<operator>",
        "value1": "...",
        "value2": "..."  // Only for binary operators
      }
    ]
  }
}

Dependencies:

  • Binary operators (equals, contains, etc.) → value1 + value2
  • Unary operators (isEmpty, isNotEmpty) → value1 only + singleValue: true

Operation-Specific Configuration

Slack Node Examples
Post Message
javascript
{
  "resource": "message",
  "operation": "post",
  "channel": "#general",      // Required
  "text": "Hello!",           // Required
  "attachments": [],          // Optional
  "blocks": []                // Optional
}
Update Message
javascript
{
  "resource": "message",
  "operation": "update",
  "messageId": "1234567890",  // Required (different from post!)
  "text": "Updated!",         // Required
  "channel": "#general"       // Optional (can be inferred)
}
Create Channel
javascript
{
  "resource": "channel",
  "operation": "create",
  "name": "new-channel",      // Required
  "isPrivate": false          // Optional
  // Note: text NOT required for this operation
}
HTTP Request Node Examples
GET Request
javascript
{
  "method": "GET",
  "url": "https://api.example.com/users",
  "authentication": "predefinedCredentialType",
  "nodeCredentialType": "httpHeaderAuth",
  "sendQuery": true,                    // Optional
  "queryParameters": {                  // Shows when sendQuery=true
    "parameters": [
      {
        "name": "limit",
        "value": "100"
      }
    ]
  }
}
POST with JSON
javascript
{
  "method": "POST",
  "url": "https://api.example.com/users",
  "authentication": "none",
  "sendBody": true,                     // Required for POST
  "body": {                             // Required when sendBody=true
    "contentType": "json",
    "content": {
      "name": "John Doe",
      "email": "john@example.com"
    }
  }
}
IF Node Examples
String Comparison (Binary)
javascript
{
  "conditions": {
    "string": [
      {
        "value1": "={{$json.status}}",
        "operation": "equals",
        "value2": "active"              // Binary: needs value2
      }
    ]
  }
}
Empty Check (Unary)
javascript
{
  "conditions": {
    "string": [
      {
        "value1": "={{$json.email}}",
        "operation": "isEmpty",
        // No value2 - unary operator
        "singleValue": true             // Auto-added by sanitization
      }
    ]
  }
}

Handling Conditional Requirements

Example: HTTP Request Body

Scenario: body field required, but only sometimes

Rule:

body is required when:
  - sendBody = true AND
  - method IN (POST, PUT, PATCH, DELETE)

How to discover:

javascript
// Option 1: Read validation error
validate_node_operation({...});
// Error: "body required when sendBody=true"

// Option 2: Check dependencies
get_property_dependencies({
  nodeType: "nodes-base.httpRequest"
});
// Shows: body → shows_when: sendBody=[true], method=[POST,PUT,PATCH,DELETE]

// Option 3: Try minimal config and iterate
// Start without body, validation will tell you if needed
Show full SKILL.md (309 more words)Show less
Example: IF Node singleValue

Scenario: singleValue property appears for unary operators

Rule:

singleValue should be true when:
  - operation IN (isEmpty, isNotEmpty, true, false)

Good news: Auto-sanitization fixes this!

Manual check:

javascript
get_property_dependencies({
  nodeType: "nodes-base.if"
});
// Shows operator-specific dependencies

Configuration Anti-Patterns

❌ Don't: Over-configure Upfront

Bad:

javascript
// Adding every possible field
{
  "method": "GET",
  "url": "...",
  "sendQuery": false,
  "sendHeaders": false,
  "sendBody": false,
  "timeout": 10000,
  "ignoreResponseCode": false,
  // ... 20 more optional fields
}

Good:

javascript
// Start minimal
{
  "method": "GET",
  "url": "...",
  "authentication": "none"
}
// Add fields only when needed
❌ Don't: Skip Validation

Bad:

javascript
// Configure and deploy without validating
const config = {...};
n8n_update_partial_workflow({...});  // YOLO

Good:

javascript
// Validate before deploying
const config = {...};
const result = validate_node_operation({...});
if (result.valid) {
  n8n_update_partial_workflow({...});
}
❌ Don't: Ignore Operation Context

Bad:

javascript
// Same config for all Slack operations
{
  "resource": "message",
  "operation": "post",
  "channel": "#general",
  "text": "..."
}

// Then switching operation without updating config
{
  "resource": "message",
  "operation": "update",  // Changed
  "channel": "#general",  // Wrong field for update!
  "text": "..."
}

Good:

javascript
// Check requirements when changing operation
get_node_essentials({
  nodeType: "nodes-base.slack"
});
// See what update operation needs (messageId, not channel)

Best Practices

✅ Do
  1. Start with get_node_essentials

    • 91.7% success rate
    • Faster than get_node_info
    • Sufficient for most needs
  2. Validate iteratively

    • Configure → Validate → Fix → Repeat
    • Average 2-3 iterations is normal
    • Read validation errors carefully
  3. Use property dependencies when stuck

    • If field seems missing, check dependencies
    • Understand what controls field visibility
    • get_property_dependencies reveals rules
  4. Respect operation context

    • Different operations = different requirements
    • Always check essentials when changing operation
    • Don't assume configs are transferable
  5. Trust auto-sanitization

    • Operator structure fixed automatically
    • Don't manually add/remove singleValue
    • IF/Switch metadata added on save
❌ Don't
  1. Jump to get_node_info immediately

    • Try essentials first
    • Only escalate if needed
    • Full schema is overwhelming
  2. Configure blindly

    • Always validate before deploying
    • Understand why fields are required
    • Check dependencies for conditional fields
  3. Copy configs without understanding

    • Different operations need different fields
    • Validate after copying
    • Adjust for new context
  4. Manually fix auto-sanitization issues

    • Let auto-sanitization handle operator structure
    • Focus on business logic
    • Save and let system fix structure

Detailed References

For comprehensive guides on specific topics:


Summary

Configuration Strategy:

  1. Start with get_node_essentials (91.7% success)
  2. Configure required fields for operation
  3. Validate configuration
  4. Check dependencies if stuck
  5. Iterate until valid (avg 2-3 cycles)
  6. Deploy with confidence

Key Principles:

  • Operation-aware: Different operations = different requirements
  • Progressive disclosure: Start minimal, add as needed
  • Dependency-aware: Understand field visibility rules
  • Validation-driven: Let validation guide configuration

Related Skills:

  • n8n MCP Tools Expert - How to use discovery tools correctly
  • n8n Validation Expert - Interpret validation errors
  • n8n Expression Syntax - Configure expression fields
  • n8n Workflow Patterns - Apply patterns with proper configuration

© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in cli-tool/components/skills/workflow-automation/n8n/n8n-node-configuration of davila7/claude-code-templates.

  • SKILL.md
  • DEPENDENCIES.md
  • OPERATION_PATTERNS.md
  • README.md

Open the folder on GitHubat commit 14680ec

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.

Compare with similar skills

N8n Node Configuration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

N8n Node Configuration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
N8n Node Configuration this skilldavila7/claude-code-templates32k1 repos~4kAutomated safety check: PassMIT
N8n Docs Assistantn8n-io/n8n207k—~550Automated safety check: PassCustom licence
Planningn8n-io/n8n207k—~2.5kAutomated safety check: PassCustom licence
Suggest Automationsn8n-io/n8n207k—~2kAutomated safety check: PassCustom licence
N8n Add Workflowkhanhduyvt0101/workflows110—~1.3kAutomated safety check: PassNone
Intent Recognitionn8n-io/n8n207k—~7.1kAutomated safety check: PassCustom licence

Similar skills

  • Official

    Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs.

    207k GitHub stars~550 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Planning

    n8n-io/n8n

    Official

    ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first.

    207k GitHub stars~2.5k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Official

    Offer the three most common automations for a user as a single-choice card, from your own knowledge of their team and their apps, then build the one they choose once they confirm, or offer more.

    207k GitHub stars~2k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • N8n Add Workflow

    khanhduyvt0101/workflows

    Add a new n8n workflow template to the repository. An agent skill from khanhduyvt0101/workflows.

    110 GitHub stars~1.3k tokensUpdated 4 mo ago
    Productivity & AutomationAuto-check passed
  • Official

    Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embedsother…

    207k GitHub stars~7.1k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Airtable Automation

    claude-office-skills/skills

    Airtable database automation - views, automations, integrations, and workflow triggers

    499 GitHub stars~2.7k tokensUpdated 8 mo ago
    Productivity & AutomationAuto-check passed

More from davila7/claude-code-templates

All 477 skills in this repo
  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    32k GitHub starsUsed in 12 repos~3.5k tokens
    Auto-check: notes
  • Neuropixels Data Analysis

    davila7/claude-code-templates

    Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.

    32k GitHub starsUsed in 10 repos~2.8k tokens
    Auto-check passed
  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    32k GitHub starsUsed in 9 repos~5.1k tokens
    Auto-check: notes
  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    32k GitHub starsUsed in 3 repos~1.9k tokens
    Auto-check passed
  • CAPA Officer

    davila7/claude-code-templates

    Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.

    32k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    32k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

Works with

Questions about N8n Node Configuration

What does N8n Node Configuration do?

Operation-aware node configuration guidance. An agent skill from davila7/claude-code-templates. N8n Node Configuration is an agent skill from davila7/claude-code-templates. Operation-aware node configuration guidance.

When should I use N8n Node Configuration?

N8n Node Configuration fits situations like: configuring nodes; understanding property dependencies; determining required fields; choosing between getnodeessentials and getnodeinfo.

How do I install N8n Node Configuration in Claude Code?

Run `npx skills add davila7/claude-code-templates --skill n8n-node-configuration -a claude-code`. Or copy the skill folder (cli-tool/components/skills/workflow-automation/n8n/n8n-node-configuration in davila7/claude-code-templates) into .claude/skills/n8n-node-configuration in your project. Claude Code loads it when a task matches its description.

How do I install N8n Node Configuration in Codex?

Run `npx skills add davila7/claude-code-templates --skill n8n-node-configuration -a codex`. Or copy the skill folder (cli-tool/components/skills/workflow-automation/n8n/n8n-node-configuration in davila7/claude-code-templates) into .agents/skills/n8n-node-configuration in your project. Codex loads it when a task matches its description.

Can I use N8n Node Configuration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill n8n-node-configuration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/n8n-node-configuration, .gemini/skills/n8n-node-configuration, .github/skills/n8n-node-configuration and .opencode/skills/n8n-node-configuration in your project.

What does N8n Node Configuration need to run?

SKILL.md names no scripts, command-line tools or credentials: N8n Node Configuration is instructions for the agent only.

Does N8n Node Configuration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is N8n Node Configuration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does N8n Node Configuration use?

N8n Node Configuration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does N8n Node Configuration use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to N8n Node Configuration?

Skills that share tags, products or a category with N8n Node Configuration: N8n Docs Assistant (n8n-io/n8n, 207k stars), Planning (n8n-io/n8n, 207k stars), Suggest Automations (n8n-io/n8n, 207k stars) and N8n Add Workflow (khanhduyvt0101/workflows, 110 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains N8n Node Configuration?

davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,463 GitHub stars. The repository holds 477 skills in this directory. The repository was last updated on October 8, 2026.

Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.