n8n-debugging
Skill1 starsChanged 3 months agoMITView on GitHub
Use when n8n workflows fail, return empty data, drop items silently, show expression errors, or when diagnosing executions with MCP explain/timeline tools.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- LucasGS520/Claude-Skillstheir own version, first seen Sep 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- LucasGS520/Claude-Skills★ 0same name
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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- n8n-agentsSkill
- n8n-ai-seo-geo-automationSkill
- n8n-binary-dataSkill
- n8n-code-nodesSkill
- n8n-credentials-securitySkill
- n8n-data-tablesSkill
- n8n-error-handlingSkill
- n8n-expressionsSkill
- n8n-loopsSkill
- n8n-mcp-toolingSkill
- n8n-node-configurationSkill
- n8n-production-opsSkill
- n8n-subworkflowsSkill
- n8n-workflow-lifecycleSkill
- using-n8n-skillsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
Prefer execution_explain / timeline tools when available.
- Distinctive: line 23
Check expressions against actual incoming JSON (not assumed schema).
- Distinctive: line 24
Verify connections (wrong branch, missing error wire).
≈ “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
n8n Debugging
Author: Taghi Molavi
#1 failure mode: silent item loss
Items become 0 between nodes with no hard error (IF route, empty HTTP body, Code return shape, Merge wait forever, wrong expression → filter).
Protocol
- Open execution; table of nodes with items in/out + errors.
- Prefer
execution_explain/ timeline tools when available. - Inspect first node where out < in (or out = 0).
- Check expressions against actual incoming JSON (not assumed schema).
- Verify connections (wrong branch, missing error wire).
- Fix → pin data → retest that node → retest flow.
Unresolved expressions
={{ ... }} left unresolved often means expression disabled or wrong field mode — lint/explain should flag.
Parameter verification
- typeVersion mismatch after n8n upgrade
- Operation-dependent fields left empty
- Credential attached but wrong environment
References
references/DIAGNOSTIC_TREE.md
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.