CtrlK
BlogDocsLog inGet started
Tessl Logo

n8n-expression-syntax

Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, mapping data between nodes, or referencing webhook data in workflows. Use this skill whenever configuring node fields that reference data from previous nodes — expressions are how n8n passes data between nodes, and getting the syntax wrong is the most common source of workflow errors. Also use when asked whether a complex expression hurts performance.

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

Highly actionable content with strong workflow sequencing, but it is verbose and self-repeating, and its progressive-disclosure references point to bundle files that are not present, leaving a monolithic body with broken navigation.

Suggestions

Create the referenced COMMON_MISTAKES.md and EXAMPLES.md bundle files (or remove the links) so the progressive-disclosure pointers resolve to real material.

Consolidate duplicated material — webhook .body access and the brace/quoting/node-name rules each appear in 3+ sections — into one canonical location to reduce token cost.

Trim re-explanation of generic JS concepts (dot vs bracket notation, array indexing, string methods) that Claude already knows, keeping only n8n-specific syntax and gotchas.

DimensionReasoningScore

Conciseness

Mostly efficient code examples, but the ~600-line body repeats material (webhook .body appears in multiple sections, validation rules duplicate the Common Mistakes table) and re-explains basic JS notions like dot vs bracket notation, costing tokens without adding skill-specific value.

2 / 3

Actionability

Extensive copy-paste-ready examples with explicit correct/incorrect pairs and concrete transforms (e.g. `{{ $json.body.name }}`, IIFE pattern, NoOp anchoring) give fully executable guidance.

3 / 3

Workflow Clarity

The transform gatekeeper presents a clearly ordered decision sequence (expression → IIFE → Code node) with explicit stop conditions, and the Set-node and branch-convergence sections include concrete quick tests and refactor steps that function as validation checkpoints.

3 / 3

Progressive Disclosure

The body references COMMON_MISTAKES.md and EXAMPLES.md, but no references/ directory or bundle files exist, so these are dangling pointers rather than real one-level-deep disclosures; the SKILL.md itself is a near-600-line monolith.

1 / 3

Total

9

/

12

Passed

Description

100%

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, specific description with concrete actions, natural trigger terms, and explicit 'Use when' guidance for both what and when. The only minor issue is slight verbosity in the last sentence, but it does not cross into fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Validate n8n expression syntax and fix common errors', 'accessing $json/$node variables', 'mapping data between nodes', 'referencing webhook data' — rather than vague language.

3 / 3

Completeness

Clearly states what it does ('Validate n8n expression syntax and fix common errors') and provides explicit 'Use when...' / 'Use this skill whenever...' trigger clauses, satisfying both what and when.

3 / 3

Trigger Term Quality

Good coverage of natural user phrasings such as '{{}} syntax', 'expression errors', 'mapping data between nodes', 'configuring node fields', and 'reference webhook data', which a user would naturally say.

3 / 3

Distinctiveness Conflict Risk

Highly specific n8n trigger surface (expressions, $json/$node, webhook .body) carves a clear niche unlikely to conflict with unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (600 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 4 missing

Warning

Total

14

/

16

Passed

Repository
czlonkowski/n8n-skills
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.