CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

n8n-code-javascript

Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/n8n-code-javascript/SKILL.md

The canonical home for this skill is n8n-code-javascript in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

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

The content is highly actionable with abundant executable examples, but it is significantly redundant and teaches generic JavaScript Claude already knows. Critically, it cites four reference files that do not exist in the bundle, so its progressive-disclosure structure fails in practice.

Suggestions

Remove duplicate treatments: state the webhook '.body' nesting and return-format rules once each instead of repeating them across Essential Rules, dedicated sections, and Error Prevention.

Cut generic JavaScript guidance ('Use Descriptive Variable Names', 'Prefer Array Methods Over Loops', 'Debug with console.log()') that Claude already knows, keeping only n8n-specific behavior.

Either bundle the referenced files (DATA_ACCESS.md, COMMON_PATTERNS.md, ERROR_PATTERNS.md, BUILTIN_FUNCTIONS.md) and trim the inlined duplicates from SKILL.md, or remove the dangling references.

DimensionReasoningScore

Conciseness

Noticeably verbose with repeated sections: webhook '.body' nesting is explained three times (Essential Rules #4, 'Critical: Webhook Data Structure', Error Prevention #5), return-format rules appear in three places, and the Best Practices section teaches generic JavaScript Claude already knows ('Use Descriptive Variable Names', 'Prefer Array Methods Over Loops', 'Debug with console.log()'). Not 3 because the padding spans multiple whole sections rather than occasional loose sentences.

2 / 5

Actionability

Fully executable, copy-paste-ready code throughout: Quick Start template, mode-selection examples, data-access patterns, correct/incorrect return-format pairs, $helpers.httpRequest, DateTime, and $jmespath examples covering the common cases. Not 4 because the examples are complete, runnable, and span the skill's typical usage.

5 / 5

Workflow Clarity

Clear sequencing (Quick Start → mode selection → data access → return format → patterns → errors) with a decision shortcut for mode choice and a 'Quick Reference Checklist' acting as a pre-deploy checkpoint. Not 5 because there is no explicit validate→fix→retry feedback loop or testing step; not 3 because sequence and checklist checkpoints are present.

4 / 5

Progressive Disclosure

The body repeatedly signals 'See: DATA_ACCESS.md', 'COMMON_PATTERNS.md', 'ERROR_PATTERNS.md', and 'BUILTIN_FUNCTIONS.md', but no bundle files exist — all references are dangling. Meanwhile the ~700-line body inlines the very content (patterns overview, built-in reference) it claims those files hold. Not 3 because references that resolve to nothing make navigation fail entirely; not 1 because section structure is present and references are clearly signaled.

2 / 5

Total

13

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 description: it states a concrete capability and follows with an explicit, well-scoped 'Use when' clause enumerating the skill's main activities. The only weakness is modest synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'using $input/$json/$node syntax', 'making HTTP requests with $helpers', 'working with dates using DateTime', 'troubleshooting Code node errors', 'choosing between Code node modes' — giving comprehensive coverage of the skill's domain. Not 4 because coverage spans data access, HTTP, dates, error handling, and mode selection with no significant gaps.

5 / 5

Completeness

Explicitly answers both 'what' ('Write JavaScript code in n8n Code nodes') and 'when' with concrete trigger phrases ('Use when writing JavaScript in n8n, using $input/$json/$node syntax... troubleshooting Code node errors, or choosing between Code node modes'). Matches the anchor-5 example structure closely.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: 'JavaScript', 'n8n', 'Code node', 'Code node errors', 'HTTP requests'. Not 5 because common variations and synonyms such as 'JS', 'scripting', or 'n8n workflow' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (n8n Code node JavaScript) with n8n-specific tokens like '$helpers' and '$input/$json/$node syntax' that other skills would not trigger on. Minimal conflict risk; not 4 because even closely related skills (e.g., n8n expression syntax) are distinguishable from these triggers.

5 / 5

Total

19

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/n8n-code-javascript/SKILL.md

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.