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

81%

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

70%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 body is highly actionable with strong sequenced workflows and validation feedback loops, but it is a monolithic inline document with cross-section repetition and no progressive disclosure into reference files.

Suggestions

Extract the long Optional Native n8n MCP Assist routing policy and the Knowledge Commands catalog into reference files (e.g. references/native-mcp.md, references/knowledge-commands.md) and link to them from SKILL.md to improve progressive disclosure and reduce inline length.

De-duplicate repeated directives such as the env status --json readiness workflow and the "stop after two failures" rule by defining each once and cross-referencing, tightening conciseness.

Resolve command placeholders like {{N8NAC_CMD}} to a concrete default or document the substitution step up front so examples read as copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Largely lean operational text that assumes competence, but several directives repeat across sections (env status workflow, "stop after two failures", MCP routing policy restated multiple times) beyond minor trimming, placing it just below the efficient anchor.	3 / 5
Actionability	Concrete bash commands and executable TypeScript examples cover common authoring/sync/validate/test/credential cases, but template placeholders ({{N8NAC_CMD}}) and "/* exact type from node-info */" slots make it mostly rather than fully copy-paste ready.	4 / 5
Workflow Clarity	Bootstrap Order, Sync Discipline, Operating Loop, and Testability Protocol are clearly sequenced with explicit validation checkpoints (--verify, test-plan, readiness gating) and error-recovery feedback loops (conflict resolve, two-failure stop, credential retry).	5 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in a ~530-line SKILL.md with no external references; section structure is decent but substantial reference-suitable content (MCP routing, knowledge-command catalog) is not split out.	3 / 5
	Total	15 / 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 strong: it states concrete actions, gives explicit trigger guidance, and occupies a clearly distinct n8n niche. The only gap is missing synonyms/file extensions that would push trigger-term coverage to fully comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("create, edit, validate, sync, or troubleshoot n8n workflows") tied to a named domain, matching the comprehensive-coverage anchor; not 4 because the workflow-lifecycle verbs are broad and not merely minor gaps.	5 / 5
Completeness	Explicitly answers what (create/edit/validate/sync/troubleshoot 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	Strong natural terms ("n8n workflows", "n8n nodes", "automation", "n8n-as-code") but missing synonyms and file extensions (e.g. ".workflow.ts"), so it sits at the good-but-incomplete anchor rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The n8n product name and n8n-as-code niche form a clear, distinct trigger surface with minimal overlap risk against unrelated skills.	5 / 5
	Total	19 / 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 (537 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: EtienneLescot/n8n-as-code
Path: packages/skills/src/agent-skills/n8n-architect/SKILL.md
Commit: cc7f42e

Reviewed: 9 days 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.