How do I install the Forge N8n skill?

Run npx skillmds@latest add forgeyclap/forge-n8n-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Forge N8n safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Forge N8n?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Forge N8n free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Forge N8n?

ForgeyClap (@forgeyclap) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Forge N8n by forgeyclap — Agent Skill

Name: Forge N8n
Author: ForgeyClap

Forge N8n

Forge playbook for building and validating n8n automation workflows. Use when creating, fixing, or validating an n8n workflow — keywords: n8n, workflow, webhook, automation, node, trigger, schedule, cron, retry, error branch, credentials, validate_workflow. Orchestrates the ECC n8n skills and n8n MCP tools and enforces the validation gate before claiming production-ready.

ForgeyClap Updated Sep 22, 2026

File contents

Forge playbook — n8n / automation

This domain is skill + MCP driven, not agent-heavy. Do not spawn a crowd of agents. Do not duplicate ECC n8n skills — defer to them.

Hard rules

Validate before claiming production-ready: webhook method, input schema, credentials, auth/security, error branch present, retry behavior, test/prod separation.
Credentials live in n8n credential store / env — never hardcoded in nodes.
Imported/new workflows stay inactive until the owner approves activation.

Workflow

Consult n8n-mcp-tools-expert first (correct nodeType formats + tool selection).
Architecture from n8n-workflow-patterns; node setup from n8n-node-configuration; expressions from n8n-expression-syntax.
Code nodes → n8n-code-javascript (default) or n8n-code-python.
Gate: run validate_node / validate_workflow via n8n-validation-expert; resolve real errors (it knows the false positives).
For custom code/scripts you may run codex-reviewer (Codex, optional) — advisory, not a blocker.

Fan-out & flow

L2 fix/extend; L3 new multi-branch workflow. Mostly serial (a workflow is one artifact); parallelize only independent sub-workflows.

Ship-readiness (unique)

validate_workflow clean; webhook auth enabled; secrets in credentials (not hardcoded); error + retry paths exist; test vs prod URLs separated; a manual test execution shown. Then run the ship-readiness n8n checklist. Never claim production-ready without passing validation; no live activation without owner approval.

---name: forge-n8n-2description: Forge playbook for building and validating n8n automation workflows. Use when creating, fixing, or validating an n8n workflow — keywords: n8n, workflow, webhook, automation, node, trigger, schedule, cron, retry, error branch, credentials, validate_workflow. Orchestrates the ECC n8n skills and n8n MCP tools and enforces the validation gate before claiming production-ready.---# Forge playbook — n8n / automationThis domain is **skill + MCP driven, not agent-heavy.** Do **not** spawn a crowd of agents. **Do not duplicate ECC n8n skills — defer to them.**## Hard rules- Validate before claiming production-ready: webhook method, input schema, credentials, auth/security, **error branch present**, retry behavior, **test/prod separation**.- Credentials live in n8n credential store / env — never hardcoded in nodes.- Imported/new workflows stay **inactive** until the owner approves activation.## Workflow1. Consult `n8n-mcp-tools-expert` **first** (correct nodeType formats + tool selection).2. Architecture from `n8n-workflow-patterns`; node setup from `n8n-node-configuration`; expressions from `n8n-expression-syntax`.3. Code nodes → `n8n-code-javascript` (default) or `n8n-code-python`.4. **Gate:** run `validate_node` / `validate_workflow` via `n8n-validation-expert`; resolve real errors (it knows the false positives).5. For custom code/scripts you *may* run `codex-reviewer` (Codex, optional) — advisory, not a blocker.## Fan-out & flowL2 fix/extend; L3 new multi-branch workflow. Mostly **serial** (a workflow is one artifact); parallelize only independent sub-workflows.## Ship-readiness (unique)`validate_workflow` clean; webhook auth enabled; secrets in credentials (not hardcoded); error + retry paths exist; test vs prod URLs separated; a manual test execution shown. Then run the `ship-readiness` n8n checklist. **Never** claim production-ready without passing validation; no live activation without owner approval.

Frequently asked questions