Forge n8n

Skill ForgeyClap/claude-forge/.claude/skills/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.From its SKILL.md

Install

npx -y skills add ForgeyClap/claude-forge --skill forge-n8n

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 378 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.