CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

v3-migration

Fix an existing workflow so it keeps working on n8n 3.0: replace removed nodes, rebuild removed AI Agent modes, rewrite removed expression helpers and review behavior changes flagged by the migration report. Load it when the user asks to migrate or update a workflow for n8n 3.0 or v3.

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a tight, expert-level instruction skill: every section carries n8n-3.0-specific knowledge, the guidance is executable down to exact parameter names and expressions, and the process sequence is clear. The only gaps are minor: the save-time validation loop is not an explicit final Process step, and the node-replacement catalog could be split into a reference file.

DimensionReasoningScore

Conciseness

The body is dense with n8n-version-specific facts Claude cannot know (mode mappings, parameter renames, expression rewrites) and contains zero padding or explanation of general concepts; every line earns its place, matching the lean-and-efficient anchor.

5 / 5

Actionability

Guidance is copy-paste concrete throughout: exact mode names ("Run Once for All Items"), exact rewrites (`item` to `item.json`, `getWorkflowStaticData(type)` to `$getWorkflowStaticData(type)`), exact expression syntax (`$fromAI('<name>', '<description>', '<type>')`, `$('<node name>').itemMatching(index)`), and per-node replacement recipes covering the common cases.

5 / 5

Workflow Clarity

The three-step Process is clearly sequenced with a decision checkpoint ("ask one focused question with ask_user before you edit") and the report's save-time re-check is stated as the built-in verification ("re-checks a workflow each time it is saved, so a correct fix closes the finding by itself"). It falls short of the 5 anchor because an explicit 'save and confirm the finding closes' step is never integrated into the Process sequence itself — the validation loop is described as context rather than as a step.

4 / 5

Progressive Disclosure

The skill is a single well-sectioned file with clear headers (Scope, Process, Node replacements, AI Agent modes, Behavior changes) and no nested references, which suits its moderate size. It stays at 4 rather than 5 because the ~60-line node-replacement catalog is reference material that could arguably live in a one-level-deep references/ file, leaving SKILL.md as a leaner overview.

4 / 5

Total

18

/

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.

The description is concrete, version-scoped, and answers both what it does and when to load it with explicit trigger phrases. Its only minor weakness is trigger-term coverage that omits a few natural variants like "upgrade" or "port".

DimensionReasoningScore

Specificity

"replace removed nodes, rebuild removed AI Agent modes, rewrite removed expression helpers and review behavior changes flagged by the migration report" lists multiple concrete actions that map one-to-one to the skill's actual scope (node replacements, agent modes, expression rewrites, behavior-change review), matching the comprehensive-coverage anchor rather than the 4 anchor's 'minor gaps'.

5 / 5

Completeness

The 'what' is explicit ("Fix an existing workflow so it keeps working on n8n 3.0" plus four concrete sub-tasks) and the 'when' is explicit with trigger phrases ("Load it when the user asks to migrate or update a workflow for n8n 3.0 or v3"), exactly matching the both-answered-with-concrete-triggers anchor.

5 / 5

Trigger Term Quality

Triggers include "migrate", "update", "n8n 3.0" and the synonym "v3", giving good natural coverage; a user might also say "upgrade my workflow", "port to n8n 3" or "n8n version 3", which keeps it just short of the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow (migrating existing n8n workflows specifically to 3.0/v3) and the triggers are version-specific, so it is clearly distinguishable from a general n8n workflow-builder skill; it would not fire for ordinary workflow creation or editing requests.

5 / 5

Total

19

/

20

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.

Validation — 15 / 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

Path

packages/@n8n/instance-ai/skills/v3-migration/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.