forge-n8n
Skill2 starsChanged 36 days agoMITView on GitHub
Forge: building and validating n8n automation workflows: n8n, workflow, webhook, trigger, cron, retry, error branch, credentials, validate_workflow.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- ForgeyClap/Forge-Coreedited, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- ForgeyClap/Forge-Core★ 214% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository74 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormingSkill
- claude-md-improverSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- forge-agent-reportSkill
- forge-agentSkill
- forge-apiSkill
- forge-botsSkill
- forge-brainstormSkill
- forge-cliSkill
- forge-cmsSkill
- forge-code-reviewSkill
- forge-councilSkill
- forge-dataSkill
- forge-debugSkill
- forge-deeplearnSkill
- forge-docdriftSkill
- forge-doctorSkill
- forge-ecommerceSkill
- forge-electronSkill
- forge-extensionSkill
- forge-figmaSkill
- forge-fullstackSkill
- forge-gameSkill
- forge-graded-verifySkill
- forge-guardianSkill
- forge-heartbeatSkill
- forge-intakeSkill
- forge-integrationSkill
- forge-mcp-clientsSkill
- forge-migrationSkill
- forge-mindmapSkill
- forge-mlopsSkill
- forge-mobileSkill
- forge-nightshiftSkill
- forge-paymentsSkill
- forge-prdSkill
- forge-predictionSkill
- forge-projectbrainSkill
- forge-prompt-coachSkill
- forge-qualitySkill
- forge-ragSkill
- forge-registrySkill
- forge-reportSkill
- forge-routerSkill
- forge-scoutSkill
- forge-scrapingSkill
- forge-scribeSkill
- forge-skill-testingSkill
- forge-snapshotSkill
- forge-verifySkill
- forge-voiceSkill
- forge-websiteSkill
- forge-worktreesSkill
- frontend-designSkill
- grillingSkill
- grill-meSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Gate: run validate_node / validate_workflow via n8n-validation-expert.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
- Expressions are null-safe: use optional chaining,
??for defaults (not||, which also replaces 0 and empty text), andArray.isArray()before looping. - Webhook-triggered workflows answer early with a Respond to Webhook node and do slow work afterwards, so the caller never times out.
Workflow
- Consult
n8n-mcp-tools-expertfirst (correct nodeType formats + tool selection). - Architecture from
n8n-workflow-patterns; node setup fromn8n-node-configuration; expressions fromn8n-expression-syntax. - Code nodes →
n8n-code-javascript(default) orn8n-code-python. - Gate: run
validate_node/validate_workflowvian8n-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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

