n8n-architect

Use when the user explicitly wants to create, edit, validate, sync, or troubleshoot n8n workflows, asks about n8n nodes or automation, or wants to use n8n-as-code in the current context root.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

A highly actionable, well-sequenced operational manual with strong validation checkpoints and feedback loops. Its weaknesses are repetition that inflates token cost and a monolithic structure with no progressive disclosure into bundle files despite its length.

Suggestions

Deduplicate repeated command blocks (env status --json, env add/use, managed-instance create/start, 'stop after two repeated failures') by defining each once and cross-referencing, to tighten conciseness from 3 toward 4-5.

Extract large self-contained sections (e.g. 'Optional Native n8n MCP Assist' routing policy, AI/LangChain node rules, full Knowledge Commands list) into reference files under ./references/ and link one level deep, improving progressive_disclosure from 3.

Consolidate the repeated secret-handling rules ('do not print API keys', 'prefer --api-key-stdin', 'do not pass secrets inline') into a single 'Secret Handling' section referenced where needed.

Dimension	Reasoning	Score
Conciseness	The body is operationally dense with no concept padding, but it is ~520 lines with notable repetition (env status --json, env add blocks, managed-instance create/start commands, 'do not print API keys', and 'stop after two repeated failures' each appear multiple times), placing it at 'mostly efficient but could be tightened' rather than the minor-trim level of 4.	3 / 5
Actionability	Copy-paste-ready `npx --yes n8nac` commands, concrete TypeScript decorator examples, and specific flags (--api-key-stdin, --verify, --prod, --query) cover the common cases; placeholders like 'exact type from node-info' are intentionally parameterized by the schema-first rule, not pseudocode.	5 / 5
Workflow Clarity	Explicit numbered Bootstrap Order (8 steps) and Operating Loop (11 steps) with validation checkpoints (pull-before-edit, push --verify, conflict resolution modes, 'stop after two repeated failures') provide clear sequencing and feedback loops for destructive/batch operations.	5 / 5
Progressive Disclosure	Section headers give real structure, but no references/scripts/assets bundle files exist, the large 'Optional Native n8n MCP Assist' routing section and AI/LangChain rules are inlined in a ~520-line monolithic SKILL.md, and nothing points one level deep to separate files, matching 'some structure but content that should be separate is inline'.	3 / 5
	Total	16 / 20 Passed

Description

87%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, third-person description that explicitly pairs concrete capabilities with natural 'Use when...' trigger guidance and carves out a distinct n8n-as-code niche. Minor room to add more granular concrete verbs or synonyms, but it satisfies what/when and distinctiveness well.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('create, edit, validate, sync, or troubleshoot n8n workflows') plus 'n8n nodes' and 'n8n-as-code', matching the 'several specific actions; minor gaps' anchor rather than 5 since 'troubleshoot' is broad and the action count is below the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what (create/edit/validate/sync/troubleshoot workflows, nodes, n8n-as-code) and when ('Use when the user explicitly wants... asks about... or wants to...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural phrases users would say ('create an n8n workflow', 'asks about n8n nodes or automation', 'n8n-as-code') give good keyword coverage, but it lacks the synonym/file-extension breadth of the comprehensive anchor, so it sits at 4 not 5.	4 / 5
Distinctiveness Conflict Risk	'n8n workflows', 'n8n nodes', and 'n8n-as-code' define a clear niche with distinct triggers and minimal overlap with any other skill.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (523 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: EtienneLescot/n8n-as-code
Path: skills/n8n-architect/SKILL.md
Commit: 48821f7

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.