Token导航 LogoToken导航

Agent Skill · 研究检索

n8n-builder(n8n 建设者)

n8n-builder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

n8n-builder 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 48,042。

总安装 706周安装 30GitHub Stars 2下载 247核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:n8n-builder(n8n 建设者)
来源仓库:https://github.com/bsamiee/parametric_forge
仓库路径:skills/n8n-builder
安装命令:
npx skills add https://github.com/bsamiee/parametric_forge --skill n8n-builder
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/bsamiee/parametric_forge --skill n8n-builder

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

n8n-builder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于 n8n 工作流构建、自动化脚本开发和系统集成场景。通过关键词搜索、来源仓库和原始 README 核验具体用法,结合安装命令使用。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/n8n-builder

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/bsamiee/parametric_forge --skill n8n-builder;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

n8n-builder 怎么安装?

在终端执行 npx skills add https://github.com/bsamiee/parametric_forge --skill n8n-builder。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

n8n-builder 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

n8n-builder 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

n8n-builder 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

n8n-builder 用的人多吗?

公开数据是累计安装 706 次,近一周安装 30 次,下载 247 次,GitHub 2 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

n8n-builder 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
n8n-builder

n8n 建设者 · 本页

7062接触敏感数据MIT有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

[H1][N8N-BUILDER]

Dictum: *Schema compliance enables n8n import without runtime validation errors.*

Generate valid n8n workflow JSON.

Tasks:

  1. Read schema.md — Root structure, settings
  2. Read nodes.md — Node definition, typeVersion
  3. Read connections.md — Graph topology, AI types
  4. (dynamic values) Read expressions.md — Variables, functions
  5. (specific nodes) Read integrations.md — Node parameters
  6. Generate JSON — Apply template from workflow.template.md
  7. Validate — Run uv run.claude/skills/n8n-builder/scripts/validate-workflow.py

REFERENCE): index.md — File listing.


[0][N8N_2.0]

Dictum: *Breaking changes invalidate pre-2025 patterns.*

Breaking Changes (December 2025):

  • Database — PostgreSQL required; MySQL/MariaDB support dropped.
  • Python — "language": "python" removed; use "pythonNative" with task runners.
  • Security — ExecuteCommand and LocalFileTrigger disabled by default.
  • Code Isolation — Environment variable access blocked in Code nodes (N8N_BLOCK_ENV_ACCESS_IN_NODE=true).
  • Agent Type — Agent type selection removed (v1.82+); all agents are Tools Agent.

[1][SCHEMA]

Dictum: *Root structure enables n8n parser recognition and execution.*

Guidance:

  • AI Workflows — Require executionOrder: "v1" in settings; async node ordering fails without.
  • Portability — Credential IDs and errorWorkflow UUIDs are instance-specific; expect reassignment post-import.
  • Optional Fields — Include empty objects ("pinData": {}) over omission; prevents import edge cases.
  • Sub-Workflow Typing — Use workflowInputs schema on trigger nodes to validate caller payloads before execution.
  • pinData Limits — Keep under 12MB; large payloads slow editor rendering and cannot contain binary data.

Best-Practices:

  • [ALWAYS] Set "active": false on generation; activation is a deployment decision.
  • [NEVER] Hardcode credential IDs; use placeholder names for cross-instance transfer.

[2][NODES]

Dictum: *Unique identity enables deterministic cross-node references.*

Guidance:

  • Name Collisions — n8n auto-renames duplicates (Set→Set1); breaks $('NodeName') expressions silently.
  • Version Matching — typeVersion must match target n8n instance; newer versions may lack backward compatibility.
  • Error Strategy — Use onError: "continueErrorOutput" for fault-tolerant pipelines; default stops execution.
  • Node Documentation — Use notes field for inline documentation; notesInFlow: true displays on canvas.

Best-Practices:

  • [ALWAYS] Generate UUID per node before building connections; connections reference node.name.
  • [ALWAYS] Space nodes 200px horizontal, 150px vertical for canvas readability.

[3][CONNECTIONS]

Dictum: *Connection types enable workflow mode distinction at parse time.*

Guidance:

  • AI vs Main — AI nodes require specialized types (ai_tool, ai_languageModel); main causes silent tool invisibility.
  • Fan-out — Single output to multiple nodes executes in parallel; order within array is non-deterministic.
  • Multi-output — Array index maps to output port; IF node: index 0 = true branch, index 1 = false branch.
  • Single Model — Agent accepts exactly one ai_languageModel connection; multiple models conflict silently.
  • Memory Scope — ai_memory persists within single trigger execution only; no cross-session persistence.

Best-Practices:

  • [ALWAYS] Match connection key AND type property; mismatches cause silent failures.
  • [NEVER] Connect AI tools via main type; agent cannot discover them.
  • [NEVER] Connect multiple language models to single agent; use Model Selector node for dynamic selection.

[4][EXPRESSIONS]

Dictum: *Dynamic evaluation eliminates hardcoded parameters.*

Guidance:

  • Static vs Dynamic — Prefix = signals evaluation; without it, value is literal string including {{}}.
  • Pinned Data — Test mode pins lack execution context; .item fails, use .first() or .all()[0] instead.
  • Complex Logic — IIFE pattern {{(function(){return...})()}} enables multi-statement evaluation.
  • Scope Confusion — $json accesses current node input only; use $('NodeName').item.json for other nodes.

Best-Practices:

  • [ALWAYS] Use $('NodeName') for cross-node data; $json only accesses current node input.
  • [ALWAYS] Escape quotes in JSON strings or use template literals to prevent invalid JSON.
  • [NEVER] Assume .item works in all contexts; pinned data testing requires explicit accessors.

[5][INTEGRATIONS]

Dictum: *Node type selection determines integration capability.*

Guidance:

  • Trigger Selection — Webhook for external calls, scheduleTrigger for periodic; choose based on initiation source.
  • AI Tool Visibility — Sub-workflow tools require description parameter; agent uses it for tool selection reasoning.
  • Code Language — Use "pythonNative" for Python; "python" is deprecated.
  • Error Propagation — Use stopAndError node for controlled failures; triggers designated error workflow.
  • 2025 Features — MCP nodes enable cross-agent interoperability; Guardrails nodes enforce AI output safety.
  • Output Parser — outputParserStructured jsonSchema must be static; expressions in schema are ignored silently.
  • Batch Processing — Use splitInBatches for large datasets to prevent memory exhaustion; process in chunks.

Best-Practices:

  • [ALWAYS] Set responseMode: "lastNode" for webhook→response patterns; ensures output reaches caller.
  • [ALWAYS] Include description on HTTP nodes used as AI tools; undocumented tools are invisible to agent.
  • [ALWAYS] Include unique webhookId per workflow to prevent path collisions across workflows.

[6][RAG]

Dictum: *RAG pipelines ground LLM responses in domain-specific knowledge.*

Guidance:

  • Vector Store Selection — Simple for development; PGVector/Pinecone/Qdrant for production persistence.
  • Embedding Consistency — Same embedding model required for insert and query; mismatch causes semantic drift.
  • Chunk Strategy — Recursive Character splitter recommended; splits Markdown/HTML/code before character fallback.
  • Memory vs Chains — Only agents support memory; chains are stateless single-turn processors.
  • Retriever Modes — MultiQuery for complex questions; Contextual Compression for noise reduction.

Best-Practices:

  • [ALWAYS] Match embedding model between document insert and query operations.
  • [ALWAYS] Use ai_memory connection type for memory nodes; main silently fails.
  • [NEVER] Use Simple Vector Store in production; data lost on restart, global user access.

[7][VALIDATION]

Dictum: *Pre-export validation prevents n8n import failures.*

Script:

uv run .claude/skills/n8n-builder/scripts/validate-workflow.py workflow.json
uv run .claude/skills/n8n-builder/scripts/validate-workflow.py workflow.json --strict

Checks (12 automated):

  • root_required — name, nodes, connections present
  • node_id_unique / node_name_unique — no duplicates
  • node_id_uuid — valid UUID format
  • conn_targets_exist — connection targets reference existing nodes
  • conn_ai_type_match — AI connection key matches type property
  • settings_exec_order_ai — LangChain workflows require executionOrder: "v1"
  • settings_caller_policy / node_on_error — enum value validation

Guidance:

  • API Deployment — Use POST then PUT pattern; single POST may ignore settings due to API bug.
  • Performance — saveExecutionProgress: true triggers DB I/O per node; disable for high-throughput (>1000 RPM).
  • Source Control — Strip instanceId when sharing; credential files contain stubs only, not secrets.

平台分布

Claude Code

28.36%
按下载量换算70

OpenCode

24.41%
按下载量换算60

Antigravity

17.41%
按下载量换算43

Gemini CLI

11.68%
按下载量换算29

Codex

8.24%
按下载量换算20

Cursor

3.9%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills