CtrlK
BlogDocsLog inGet started
Tessl Logo

debugging-executions

Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable debugging skill that gives exact tool calls and fields to inspect, organizes guidance by scenario, and includes an explicit re-run validation loop. No bundle files exist, but the single external reference is clearly signaled and one level deep, so progressive disclosure is appropriate for a simple skill.

DimensionReasoningScore

Conciseness

The body is lean and directive — every section gives actionable guidance with specific tool calls and fields to inspect, with no filler explaining concepts Claude already knows; the admonitions in the 'still fails' section are distinct behavioral corrections that earn their tokens rather than padding.

3 / 3

Actionability

Provides fully specified, executable tool calls with parameters — 'executions(action="debug")', 'executions(action="run") with inputData', and 'executions(action="get-resolved-node-parameters", executionId, nodeName)' — plus the exact subfields to check (failedNode.resolvedParameters, emptyResolutions, failedExpressions), making it copy-paste ready.

3 / 3

Workflow Clarity

Organizes guidance by scenario with an explicit re-run validation checkpoint ('Re-run the failing path... and inspect the real result before responding') and an error-recovery loop (re-run, check emptyResolutions first, distinguish unreconstructable-context from real bugs), satisfying the feedback-loop expectation for debugging operations.

3 / 3

Progressive Disclosure

For a sub-50-line single-purpose skill, the content is cleanly split into well-signaled sections with one clearly-flagged one-level-deep reference ('read knowledge-base/reference/trigger-input-data-shapes.md when a sandbox workspace is available'), meeting the simple-skill allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states a concrete domain and pairs it with explicit, natural-sounding load triggers covering both failure and wrong-output cases. It is only slightly limited on specificity because it names the domain and a couple of actions rather than a comprehensive list of concrete operations.

DimensionReasoningScore

Specificity

Names the domain ('workflow executions') and a couple of actions ('Debug failed or wrong-output workflow executions using executions tools'), but does not enumerate multiple distinct concrete actions the way the score-3 anchor does, so it stops at the 'names domain and some actions' level.

2 / 3

Completeness

Explicitly answers both what ('Debug failed or wrong-output workflow executions using executions tools') and when ('Load when the user reports execution failures, unexpected node output...'), matching the score-3 anchor that answers what AND when with explicit triggers.

3 / 3

Trigger Term Quality

Covers natural reporting phrases a user would say — 'execution failures', 'unexpected node output', 'empty parameter values after a successful run', 'a node showing a red or failed expression error' — giving good breadth of natural trigger terms rather than only jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (debugging workflow executions via the executions tool) with distinct, specific triggers unlikely to fire for unrelated skills; it would not conflict with generic document or code skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
n8n-io/n8n
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.