BF 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.
Write Python code in n8n Code nodes.
As a process F 34/100 · Will not run — References files that are not bundled: DATA_ACCESS.md, ERROR_PATTERNS.md, STANDARD_LIBRARY.md
How to improve
- The text references files that are not there: add them or drop the references.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: DATA_ACCESS.md - warning
missing-refreference to a missing file: ERROR_PATTERNS.md - warning
missing-refreference to a missing file: STANDARD_LIBRARY.md - warning
missing-refreference to a missing file: COMMON_PATTERNS.md - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "risk"
Process rating: all ten parameters 34/100
Will not run. References files that are not bundled: DATA_ACCESS.md, ERROR_PATTERNS.md, STANDARD_LIBRARY.md
- 0Tools and files. 4 referenced file(s) missing: DATA_ACCESS.md, ERROR_PATTERNS.md, STANDARD_LIBRARY.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 4398 tokens
- 85Steps. 81 steps, 3 vague phrases
- 100Consistency. Name and required fields are in place
- low 16 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 192: enough signal without eating the budget
- +4Structure: 53 headings
- +3Step-by-step instructions: 81 items
- +4Has examples (30 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.