Agent skill

N8n Workflows

by vibeeval in vibeeval/vibecosystem

n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.

MITAuto-check passedProductivity & Automation

Install N8n Workflows

skills CLI
$ npx skills add vibeeval/vibecosystem --skill n8n-workflows -a claude-code

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

GitHub CLI
$ gh skill install vibeeval/vibecosystem n8n-workflows --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/vibeeval/vibecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/n8n-workflows .claude/skills/n8n-workflows && 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-workflows
GitHub stars
531
Token cost
~3.3k tokens
SKILL.md length
330 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.

  • Works in 5 steps: Deploy Notification → Issue Triage → PR Review Reminder → …
  • Tasks that involve Workflow automation
  • SKILL.md covers n8n MCP Server Kurulumu, Workflow Olusturma, Trigger Tipleri and Node Tipleri ve Kullanimi, plus 2 more sections
  • Calls curl, npm and docker; reaches api.github.com; needs N8N_BASIC_AUTH_PASSWORD and N8N_API_KEY

What it does

N8n Workflows is an agent skill from vibeeval/vibecosystem. n8n otomasyon workflow'lari. Webhook, cron trigger, API entegrasyon, CI/CD otomasyon.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Workflow automation, Scheduled and recurring tasks and Webhooks. It works with n8n and Model Context Protocol. The repository describes itself as: AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution. The licence is MIT.

When your agent uses it

  • Tasks that involve Workflow automation
  • Tasks that involve Scheduled and recurring tasks
  • Tasks that involve Webhooks

Example prompts

  • “/n8n-workflows”

Requirements

  • Node.js
  • Docker
  • A credential in N8N_API_KEY
  • A credential in N8N_WEBHOOK_TOKEN

Workflow steps

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

  1. Deploy Notification
  2. Issue Triage
  3. PR Review Reminder
  4. Daily Standup Collector
  5. Error Alert Pipeline

What it can do on your machine

Read from SKILL.md and the folder at commit 3b763b1. 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

    Shell commands in SKILL.md call:

    • curl
    • npm
    • docker
    • jq

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.github.com

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • N8N_BASIC_AUTH_PASSWORD
    • N8N_API_KEY
    • N8N_WEBHOOK_TOKEN

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

Context cost

N8n Workflows loads about 3.3k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 330 words of instructions outside code blocks.

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

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 vibeeval/vibecosystem at commit 3b763b1, republished under its MIT licence (© vibeeval). 330 words, ~3,324 tokens.

Download SKILL.mdSave it as .claude/skills/n8n-workflows/SKILL.md (or your agent's skills folder).
name
n8n-workflows
description
n8n otomasyon workflow'lari. Webhook, cron trigger, API entegrasyon, CI/CD otomasyon.

n8n Workflows

n8n MCP Server Kurulumu

NPM Kurulum
bash
npm install -g n8n
n8n start  # http://localhost:5678
Docker Kurulum
bash
docker run -d \
  --name n8n \
  -p 5678:5678 \
  -v n8n_data:/home/node/.n8n \
  -e N8N_BASIC_AUTH_ACTIVE=true \
  -e N8N_BASIC_AUTH_USER=admin \
  -e N8N_BASIC_AUTH_PASSWORD=<strong-password> \
  n8nio/n8n
MCP Server Config
json
{
  "mcpServers": {
    "n8n": {
      "command": "npx",
      "args": ["-y", "@anthropic/n8n-mcp-server"],
      "env": {
        "N8N_API_URL": "http://localhost:5678/api/v1",
        "N8N_API_KEY": "<n8n-api-key>"
      }
    }
  }
}
API Key Olusturma
n8n UI > Settings > API > Create API Key
Scope: workflow:read, workflow:write, execution:read

Workflow Olusturma

Temel Yapi
json
{
  "name": "My Workflow",
  "nodes": [
    {
      "name": "Trigger",
      "type": "n8n-nodes-base.webhook",
      "position": [250, 300],
      "parameters": {
        "path": "my-webhook",
        "httpMethod": "POST"
      }
    },
    {
      "name": "Process",
      "type": "n8n-nodes-base.function",
      "position": [450, 300],
      "parameters": {
        "functionCode": "return items.map(item => ({ json: { processed: true, ...item.json } }));"
      }
    }
  ],
  "connections": {
    "Trigger": {
      "main": [[{ "node": "Process", "type": "main", "index": 0 }]]
    }
  }
}
MCP ile Workflow Olustur
n8n.create_workflow({
  name: "Deploy Notification",
  nodes: [...],
  connections: {...},
  active: true
})
Workflow Listele
n8n.list_workflows({
  active: true,
  tags: ["production"]
})
Workflow Calistir
n8n.execute_workflow({
  workflow_id: "123",
  data: {
    environment: "production",
    version: "v1.2.3"
  }
})

Trigger Tipleri

Webhook Trigger
json
{
  "type": "n8n-nodes-base.webhook",
  "parameters": {
    "path": "deploy-hook",
    "httpMethod": "POST",
    "authentication": "headerAuth",
    "options": {
      "responseMode": "responseNode",
      "responseCode": 200
    }
  }
}
Cron Trigger
json
{
  "type": "n8n-nodes-base.cron",
  "parameters": {
    "triggerTimes": {
      "item": [
        { "mode": "everyDay", "hour": 9, "minute": 0 },
        { "mode": "custom", "cronExpression": "0 */6 * * *" }
      ]
    }
  }
}
Event Trigger'lar
TriggerKaynakKullanim
WebhookDis sistemGitHub push, Stripe payment
CronZamanlamaGunluk rapor, cleanup
Email (IMAP)EmailSupport ticket olusturma
RSSFeedIcerik izleme
TelegramBot mesajKomut isleme
GitHubRepo eventCI/CD tetikleme
SlackMesaj/mentionTeam notification
DatabaseRow changeData sync
Poll Trigger
json
{
  "type": "n8n-nodes-base.pollTrigger",
  "parameters": {
    "pollTimes": {
      "item": [{ "mode": "everyMinute", "minute": 5 }]
    },
    "url": "https://api.example.com/status"
  }
}

Node Tipleri ve Kullanimi

HTTP Request
json
{
  "type": "n8n-nodes-base.httpRequest",
  "parameters": {
    "url": "https://api.example.com/data",
    "method": "POST",
    "authentication": "predefinedCredentialType",
    "nodeCredentialType": "httpHeaderAuth",
    "sendBody": true,
    "bodyParameters": {
      "parameters": [
        { "name": "key", "value": "={{ $json.value }}" }
      ]
    },
    "options": {
      "timeout": 10000,
      "retry": { "maxRetries": 3, "retryInterval": 1000 }
    }
  }
}
Function Node (JavaScript)
json
{
  "type": "n8n-nodes-base.function",
  "parameters": {
    "functionCode": "const results = [];\nfor (const item of items) {\n  const data = item.json;\n  results.push({\n    json: {\n      name: data.name.toUpperCase(),\n      processed_at: new Date().toISOString()\n    }\n  });\n}\nreturn results;"
  }
}
IF Node (Kosul)
json
{
  "type": "n8n-nodes-base.if",
  "parameters": {
    "conditions": {
      "string": [
        {
          "value1": "={{ $json.status }}",
          "operation": "equal",
          "value2": "success"
        }
      ]
    }
  }
}
Switch Node
json
{
  "type": "n8n-nodes-base.switch",
  "parameters": {
    "dataType": "string",
    "value1": "={{ $json.priority }}",
    "rules": {
      "rules": [
        { "value2": "critical", "output": 0 },
        { "value2": "high", "output": 1 },
        { "value2": "low", "output": 2 }
      ]
    }
  }
}
Merge Node
json
{
  "type": "n8n-nodes-base.merge",
  "parameters": {
    "mode": "mergeByKey",
    "propertyName1": "id",
    "propertyName2": "userId"
  }
}
Yaygin Node'lar
NodeAmacOrnek
HTTP RequestAPI cagirREST endpoint
FunctionKod calistirData transform
IF/SwitchDallanmaKosula gore yonlendir
SetData ataField ekle/degistir
MergeBirlestirIki kaynak birlestir
Split In BatchesParcalaRate limiting
WaitBekleDelay/approval
Error TriggerHata yakalaHata notification
SlackMesaj gonderTeam bildirim
GmailEmail gonderNotification
Postgres/MySQLDB islemCRUD
RedisCacheKey-value store

API Entegrasyonu

Credential Yonetimi
n8n UI > Settings > Credentials > New Credential
Tipler: API Key, OAuth2, Basic Auth, Header Auth

// Workflow'da kullanim
"authentication": "predefinedCredentialType",
"nodeCredentialType": "slackApi"
REST API Cagirma
json
{
  "type": "n8n-nodes-base.httpRequest",
  "parameters": {
    "url": "https://api.github.com/repos/{{ $json.owner }}/{{ $json.repo }}/pulls",
    "method": "GET",
    "authentication": "predefinedCredentialType",
    "nodeCredentialType": "githubApi",
    "options": {
      "response": { "response": { "fullResponse": true } }
    }
  }
}
Pagination Handling
javascript
// Function node: paginated API cagirma
const allResults = [];
let page = 1;
let hasMore = true;

while (hasMore) {
  const response = await this.helpers.httpRequest({
    url: `https://api.example.com/items?page=${page}&per_page=100`,
    method: 'GET',
  });
  allResults.push(...response.data);
  hasMore = response.data.length === 100;
  page++;
}

return allResults.map(item => ({ json: item }));

Error Handling

Try/Catch Pattern
json
{
  "nodes": [
    {
      "name": "Try",
      "type": "n8n-nodes-base.httpRequest",
      "continueOnFail": true,
      "parameters": { "url": "https://api.example.com/data" }
    },
    {
      "name": "Check Error",
      "type": "n8n-nodes-base.if",
      "parameters": {
        "conditions": {
          "boolean": [
            { "value1": "={{ $json.error }}", "value2": true }
          ]
        }
      }
    },
    {
      "name": "Error Handler",
      "type": "n8n-nodes-base.slack",
      "parameters": {
        "channel": "#alerts",
        "text": "Workflow error: {{ $json.error.message }}"
      }
    }
  ]
}
Error Workflow
n8n UI > Workflow Settings > Error Workflow
Global error handler: her basarisiz workflow bu workflow'u tetikler

Error workflow node'lari:
1. Error Trigger → hata bilgisini al
2. Function → hatayi formatla
3. Slack/Email → bildirim gonder
4. HTTP Request → incident sisteme kaydet
Retry Stratejisi
json
{
  "parameters": {
    "options": {
      "retry": {
        "maxRetries": 3,
        "retryInterval": 2000,
        "retryOnTimeout": true
      }
    }
  }
}

Workflow Debugging

Execution Log
n8n.list_executions({
  workflow_id: "123",
  status: "error",
  limit: 10
})
Execution Detayi
n8n.get_execution({
  execution_id: "456",
  include_data: true
})
// Her node'un input/output data'sini gosterir
Debug Teknikleri
1. Manual execution: UI'da "Execute Workflow" tikla
2. Node output: Her node'un ciktisini incele
3. Expression editor: {{ $json.field }} ifadelerini test et
4. Console log: Function node'da console.log() kullan
5. Test webhook: Postman/curl ile webhook'u test et
6. Pin data: Test data'yi node'a sabitle (development icin)

CI/CD Entegrasyonu

GitHub Actions ile n8n
yaml
# .github/workflows/deploy.yml
name: Deploy
on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Deploy
        run: ./deploy.sh
      - name: Notify n8n
        run: |
          curl -X POST https://n8n.example.com/webhook/deploy-complete \
            -H "Content-Type: application/json" \
            -H "Authorization: Bearer ${{ secrets.N8N_WEBHOOK_TOKEN }}" \
            -d '{
              "repo": "${{ github.repository }}",
              "branch": "${{ github.ref_name }}",
              "commit": "${{ github.sha }}",
              "actor": "${{ github.actor }}"
            }'
Claude Code'dan Workflow Tetikleme
bash
# Webhook ile tetikle
curl -X POST http://localhost:5678/webhook/my-workflow \
  -H "Content-Type: application/json" \
  -d '{"action": "deploy", "version": "v1.2.3"}'

# API ile tetikle
curl -X POST http://localhost:5678/api/v1/workflows/123/execute \
  -H "X-N8N-API-KEY: <api-key>" \
  -H "Content-Type: application/json" \
  -d '{"data": {"key": "value"}}'
Workflow Export/Import (GitOps)
bash
# Export (backup)
curl -s http://localhost:5678/api/v1/workflows \
  -H "X-N8N-API-KEY: <key>" | jq '.' > workflows-backup.json

# Import
curl -X POST http://localhost:5678/api/v1/workflows \
  -H "X-N8N-API-KEY: <key>" \
  -H "Content-Type: application/json" \
  -d @workflow.json

Ornek Workflow'lar

1. Deploy Notification
Trigger: Webhook (GitHub Actions'dan)
  → Function: Deploy bilgisini formatla
  → Slack: #deployments kanalina bildir
  → IF: Production deploy mi?
    → YES: Telegram'a da bildir
    → NO: Sadece Slack
json
{
  "name": "Deploy Notification",
  "nodes": [
    {
      "name": "Webhook",
      "type": "n8n-nodes-base.webhook",
      "parameters": { "path": "deploy-notify", "httpMethod": "POST" }
    },
    {
      "name": "Format",
      "type": "n8n-nodes-base.function",
      "parameters": {
        "functionCode": "const d = items[0].json;\nreturn [{ json: { text: `Deploy: ${d.repo} (${d.branch}) by ${d.actor}\\nCommit: ${d.commit.substring(0,7)}` } }];"
      }
    },
    {
      "name": "Slack",
      "type": "n8n-nodes-base.slack",
      "parameters": { "channel": "#deployments", "text": "={{ $json.text }}" }
    }
  ]
}
2. Issue Triage
Trigger: GitHub (issue opened)
  → Function: Label belirle (title/body analizi)
  → GitHub: Label ata
  → IF: Bug mu?
    → YES: Slack #bugs kanalina bildir, P1 ise mention
    → NO: Backlog'a ekle
3. PR Review Reminder
Trigger: Cron (her gun 10:00)
  → GitHub: Acik PR'lari listele
  → IF: 24+ saat review bekleyen var mi?
    → YES: Slack'te reviewer'a mention at
    → NO: Bos geç
4. Daily Standup Collector
Trigger: Cron (her gun 09:00)
  → Slack: #standup kanalina soru gonder
  → Wait: 2 saat
  → Slack: Cevaplari topla
  → Function: Ozet olustur
  → Notion: Standup sayfasina kaydet
5. Error Alert Pipeline
Trigger: Webhook (app error handler'dan)
  → Function: Error dedup (son 5dk ayni hata var mi)
  → IF: Yeni hata mi?
    → YES:
      → Switch (severity):
        → Critical: PagerDuty + Slack + Telegram
        → High: Slack + Email
        → Low: Slack only
    → NO: Counter artir, sessiz kal

Best Practices

Workflow Tasarimi
KuralAciklama
Tek sorumlulukHer workflow tek bir is yapsin
Error handlingHer dis API call'da continueOnFail
IdempotentAyni input, ayni output (retry-safe)
TimeoutHTTP request'lere timeout koy
Rate limitSplit In Batches ile API limit'e uy
CredentialHardcode yapma, n8n credential store kullan
NamingNode isimlerini aciklayici yap
TestingPin data ile test et, sonra production'a al
Guvenlik
1. Webhook'lara authentication ekle (header auth veya HMAC)
2. Credential'lari n8n credential store'da tut
3. Sensitive data'yi log'lama
4. Network: n8n'i public internet'e ACMA (reverse proxy kullan)
5. API key'leri environment variable'dan al
6. Workflow export'larinda credential'lar OLMAZ (import sonrasi set et)
Performans
1. Batch processing: Split In Batches node kullan
2. Parallel execution: baska node'lara dallan
3. Caching: Redis node ile sik kullanilan data'yi cache'le
4. Pagination: Buyuk data set'lerde sayfalama yap
5. Timeout: Uzun workflow'lara timeout koy (workflow settings)
6. Cleanup: Eski execution log'larini sil (Settings > Pruning)

Anti-Patterns

Anti-PatternDogru Yol
Monolithic workflowKucuk, tek sorumluluk workflow'lar
No error handlingcontinueOnFail + error workflow
Hardcoded credentialsn8n credential store
No retryRetry config ekle
Polling every secondWebhook kullan veya 5min+ interval
No dedupDuplicate event kontrolu ekle
No monitoringExecution log + error alert workflow

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

Files

Just SKILL.md in skills/n8n-workflows of vibeeval/vibecosystem.

Open the folder on GitHubat commit 3b763b1

Compare with similar skills

N8n Workflows 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 Workflows compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
N8n Workflows this skillvibeeval/vibecosystem531—~3.3kAutomated safety check: PassMIT
N8n Workflow Patternsdavila7/claude-code-templates32k1 repos~2.8kAutomated safety check: PassMIT
N8naiskillstore/marketplace4301 repos~1.6kAutomated safety check: PassNone
Schedule Recipemohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
n8n Workflow Patternsczlonkowski/n8n-skills6.4k—~5.1kAutomated safety check: PassMIT
Makeericrisco/rsc-harness167—~3.1kAutomated safety check: NotesMIT

Similar skills

  • N8n Workflow Patterns

    davila7/claude-code-templates

    Proven workflow architectural patterns from real n8n workflows.

    32k GitHub starsUsed in 1 repo~2.8k tokens
    Productivity & AutomationAuto-check passed
  • N8n

    aiskillstore/marketplace

    n8n workflow automation patterns and API integration. An agent skill from aiskillstore/marketplace.

    430 GitHub starsUsed in 1 repo~1.6k tokens
    Productivity & AutomationAuto-check passed
  • Schedule Recipe

    mohitagw15856/pm-claude-skills

    Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • n8n Workflow Patterns

    czlonkowski/n8n-skills

    Architecture patterns for n8n workflows covering webhooks, HTTP APIs, databases, AI agents, scheduled jobs and batch processing, with advice on choosing between them.

    6.4k GitHub stars~5.1k tokensUpdated 22 days ago
    Productivity & AutomationAuto-check passed
  • Make

    ericrisco/rsc-harness

    A skill your agent uses when operating Make.com (formerly Integromat) programmatically — driving its REST API v2 or the Make MCP server from code or an agent to create, read, update, activate, run…

    167 GitHub stars~3.1k tokensUpdated today
    Backend & APIsAuto-check: notes
  • 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

More from vibeeval/vibecosystem

All 12 skills in this repo
  • Agent Benchmark

    vibeeval/vibecosystem

    Framework for measuring and tracking agent response quality over time.

    531 GitHub stars~2.9k tokensUpdated 2 mo ago
    Auto-check passed
  • Differential Review

    vibeeval/vibecosystem

    Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format.

    531 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed
  • Factcheck Guard

    vibeeval/vibecosystem

    A skill your agent uses when making any factual claim about the codebase — existence, absence, or behavior.

    531 GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Fp Check

    vibeeval/vibecosystem

    Systematic false positive verification for security findings.

    531 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed
  • Notepad System

    vibeeval/vibecosystem

    A skill your agent uses when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks.

    531 GitHub stars~1.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Property Based Testing

    vibeeval/vibecosystem

    Property-based testing (PBT) patterns with fast-check (JS/TS), Hypothesis (Python), and gopter (Go).

    531 GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed

Questions about N8n Workflows

What does N8n Workflows do?

n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem. N8n Workflows is an agent skill from vibeeval/vibecosystem. n8n otomasyon workflow'lari.

When should I use N8n Workflows?

N8n Workflows fits situations like: tasks that involve Workflow automation; tasks that involve Scheduled and recurring tasks; tasks that involve Webhooks.

How do I install N8n Workflows in Claude Code?

Run `npx skills add vibeeval/vibecosystem --skill n8n-workflows -a claude-code`. Or copy the skill folder (skills/n8n-workflows in vibeeval/vibecosystem) into .claude/skills/n8n-workflows in your project. Claude Code loads it when a task matches its description.

How do I install N8n Workflows in Codex?

Run `npx skills add vibeeval/vibecosystem --skill n8n-workflows -a codex`. Or copy the skill folder (skills/n8n-workflows in vibeeval/vibecosystem) into .agents/skills/n8n-workflows in your project. Codex loads it when a task matches its description.

Can I use N8n Workflows 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 vibeeval/vibecosystem --skill n8n-workflows -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-workflows, .gemini/skills/n8n-workflows, .github/skills/n8n-workflows and .opencode/skills/n8n-workflows in your project.

What does N8n Workflows need to run?

Going by SKILL.md and its folder, N8n Workflows needs the command-line tools its instructions call (curl, npm, docker and jq) and credentials named N8N_BASIC_AUTH_PASSWORD, N8N_API_KEY and N8N_WEBHOOK_TOKEN. Our summary lists: Node.js; Docker; A credential in N8N_API_KEY; A credential in N8N_WEBHOOK_TOKEN.

Does N8n Workflows access the network?

SKILL.md names 1 domain. In commands or code: api.github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is N8n Workflows 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 Workflows use?

N8n Workflows 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 Workflows use?

About 3.3k tokens (SKILL.md is roughly 13k 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 Workflows?

Skills that share tags, products or a category with N8n Workflows: N8n Workflow Patterns (davila7/claude-code-templates, 32k stars), N8n (aiskillstore/marketplace, 430 stars), Schedule Recipe (mohitagw15856/pm-claude-skills, 1.4k stars) and n8n Workflow Patterns (czlonkowski/n8n-skills, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains N8n Workflows?

vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 8, 2026.

Source: vibeeval/vibecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.