CtrlK
BlogDocsLog inGet started
Tessl Logo

n8n-code-python

Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.

56

Quality

66%

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-python/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill provides solid, actionable Python code examples for n8n Code nodes with good coverage of data access patterns, return formats, and common pitfalls. However, it is significantly over-verbose: the 'use JavaScript instead' message is repeated excessively, basic Python concepts are over-explained, and substantial content is duplicated between the main file and referenced companion files. The progressive disclosure structure is partially undermined by inlining content that should live exclusively in the referenced files.

Suggestions

Remove redundant 'consider JavaScript first' messaging - state it once at the top and remove the 4+ other repetitions throughout the document to save significant tokens.

Eliminate the inline Standard Library Reference section and Error Prevention section since these duplicate STANDARD_LIBRARY.md and ERROR_PATTERNS.md - replace with brief 'See X.md' references only.

Remove explanations of basic Python concepts Claude already knows (what .get() does, what list comprehensions are, why safe dictionary access matters) and just show the correct patterns.

Cut the 'Integration with Other Skills' section entirely - Claude can discover skill relationships without being told, and this section adds ~30 lines of zero-actionability content.

DimensionReasoningScore

Conciseness

Significantly verbose. The repeated 'consider JavaScript first' messaging appears 5+ times. Extensive explanations of concepts Claude already knows (what list comprehensions are, what .get() does, what standard library modules do). The 'When to Use Python vs JavaScript' section, 'Integration with Other Skills' section, and 'Best Practices' section all contain information Claude inherently understands. Many patterns are shown in both correct and incorrect forms redundantly across multiple sections.

2 / 5

Actionability

Provides concrete, executable Python code examples throughout. The code snippets are copy-paste ready with proper n8n syntax (_input.all(), return format, etc.). Minor gap: some patterns like the debug tip (print to browser console) could use more specificity, and the workarounds section for missing libraries is more directional than executable.

4 / 5

Workflow Clarity

This is primarily a reference/pattern skill rather than a multi-step workflow skill, so the single-task exception partially applies. However, the checklist at the end provides a validation sequence, and the mode selection guide gives clear decision logic. The skill lacks explicit validation/verification steps for testing code output - there's no 'run and verify' feedback loop described for the code writing process itself.

3 / 5

Progressive Disclosure

References to DATA_ACCESS.md, COMMON_PATTERNS.md, ERROR_PATTERNS.md, and STANDARD_LIBRARY.md are well-signaled throughout with 'See:' callouts. However, no bundle files were provided, so these references cannot be verified. The main file itself is very long (~400+ lines) with substantial content that could be offloaded to the referenced files (e.g., the full Standard Library Reference section duplicates what STANDARD_LIBRARY.md should contain, and the error patterns section duplicates ERROR_PATTERNS.md content).

3 / 5

Total

12

/

20

Passed

Description

82%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.

This is a solid skill description with a clear 'Use when' clause and strong distinctiveness for its niche (Python in n8n). Its main weakness is that the 'what' portion is somewhat vague—it says 'write Python code' but doesn't enumerate specific capabilities like data transformation, API response handling, or error management. The trigger terms are good but could include a few more natural variations.

Suggestions

Add 2-3 specific concrete actions beyond 'write Python code,' such as 'transform data between nodes,' 'parse API responses,' or 'handle errors in workflows' to improve specificity.

Consider adding natural synonym variations like 'n8n python script,' 'n8n automation code,' or 'pyodide' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Python code in n8n Code nodes) and mentions a couple of concrete elements like '_input/_json/_node syntax' and 'Python limitations,' but doesn't list specific actions like 'parse JSON responses,' 'transform data,' or 'handle errors.' The description is more about context than concrete actions.

3 / 5

Completeness

Clearly answers both 'what' (write Python code in n8n Code nodes) and 'when' (explicit 'Use when' clause with multiple concrete trigger scenarios: writing Python in n8n, using specific syntax patterns, working with standard library, understanding limitations).

5 / 5

Trigger Term Quality

Includes good natural keywords like 'Python,' 'n8n,' 'Code nodes,' '_input/_json/_node syntax,' and 'standard library.' Missing some variations users might say like 'n8n python script,' 'n8n automation,' or 'pyodide,' but covers the core terms well.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Python specifically within n8n Code nodes. The mention of n8n-specific syntax like '_input/_json/_node' and the n8n platform context makes it very unlikely to conflict with general Python coding skills or other automation platform skills.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

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

Warning

Total

9

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.