Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Impertio-Studio/n8n-Claude-Skill-Package --skill n8n-errors-executiongit clone --depth 1 https://github.com/Impertio-Studio/n8n-Claude-Skill-PackageWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/impertio-studio/n8n-claude-skill-package/n8n-errors-execution)<a href="https://agentmods.dev/skills/impertio-studio/n8n-claude-skill-package/n8n-errors-execution"><img src="https://agentmods.dev/badge/skills/impertio-studio/n8n-claude-skill-package/n8n-errors-execution/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/impertio-studio/n8n-claude-skill-package/n8n-errors-execution"><img src="https://agentmods.dev/badge/skills/impertio-studio/n8n-claude-skill-package/n8n-errors-execution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00110 | $0.01983 |
| Opus 5 | $0.00055 | $0.00992 |
| Sonnet 5 | $0.00022 | $0.00397 |
| Haiku 4.5 | $0.00011 | $0.00198 |
Grade A, and why
n8n-errors-execution scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
n8n Error Handling & Execution Failures
Quick Reference
| Mechanism | Scope | Purpose | Configuration |
|---|---|---|---|
| Error Workflow | Workflow-level | Catch any unhandled failure, notify/recover | Workflow Settings > Error Workflow |
| continueOnFail | Per-node | Allow workflow to continue despite node failure | Node Settings > Continue On Fail |
| Retry on Fail | Per-node | Automatically retry transient failures | Node Settings > Retry On Fail |
| Stop And Error | Explicit node | Deliberately fail workflow with custom message | Add Stop And Error node |
Error Handling Decision Tree
Workflow execution fails
├── Is the failure transient (API timeout, rate limit)?
│ ├── YES → Enable Retry on Fail on that node
│ │ Config: maxTries=3, waitBetweenTries=1000ms
│ │ └── Still fails after retries? → Falls to Error Workflow
│ └── NO → Continue below
├── Should the workflow continue despite this node failing?
│ ├── YES → Enable continueOnFail on that node
│ │ └── Check $json.error in next node for fallback logic
│ └── NO → Continue below
├── Is this a business logic validation failure?
│ ├── YES → Use Stop And Error node to fail explicitly
│ │ └── Error Workflow receives the custom error message
│ └── NO → Continue below
└── Unhandled failure
└── ALWAYS configure an Error Workflow to catch it
└── Error Trigger → Slack/Email/Database notification
The 4 Error Handling Patterns
Pattern 1: Error Workflow with Notifications
When: ALWAYS set up as a safety net for every production workflow.
Main Workflow → (fails) → Error Trigger → Slack/Email notification
Setup:
- Create a new workflow with an Error Trigger node as the start
- Add notification nodes (Slack, Email, HTTP Request to logging service)
- In the main workflow, open Workflow Settings
- Select the error workflow from the Error Workflow dropdown
- One error workflow can serve multiple production workflows
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 194 lines · 110 tokens per session scan A 39572bf5f940
n8n-errors-execution is a skill published in the GitHub repository Impertio-Studio/n8n-Claude-Skill-Package (3 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 1,983 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
qgis-errors-data-loading
Use when diagnosing data loading failures, invalid layers, or provider connection errors. Prevents silent failures from unchecked layer validity and incorrect URI formats. Covers invalid layer detection, URI format errors, encoding issues, GeoPackage locking, connection failures, and performance. Keywords: invalid…
qgis-errors-projections
Use when diagnosing CRS/projection errors, coordinate mismatches, or datum transformation issues. Prevents silent data corruption from wrong CRS assignment and coordinate order confusion. Covers wrong EPSG selection, lat/lon vs lon/lat, datum warnings, on-the-fly reprojection pitfalls, and fix patterns. Keywords: CRS…
threejs-errors-performance
Use when a Three.js scene has performance problems: low FPS, memory leaks, too many draw calls, or high GPU memory usage. Prevents the common mistake of forgetting dispose(), creating objects in the render loop, or not using InstancedMesh for repeated objects. Covers disposal patterns, draw call optimization…
threejs-errors-rendering
Use when a Three.js scene renders incorrectly: black screen, invisible objects, wrong colors, z-fighting, or broken shadows. Prevents the common mistake of wrong color space, missing material.side, or forgetting updateProjectionMatrix. Covers all common rendering errors with diagnosis steps and fix patterns. Keywords…
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…