CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

90%

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

The canonical home for this skill is n8n-architect in EtienneLescot/n8n-as-code

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 body with concrete commands, working TypeScript examples, and strong validation feedback loops. The main weakness is progressive disclosure — the large amount of reference-style material (command catalogs, node rules) is inlined rather than split into one-level-deep bundle files.

Suggestions

Move the long command catalogs (e.g. 'Knowledge Commands', 'Managed Local Runtime' command lists) into a references/ file and link to it from SKILL.md, so the body stays a concise overview with one-level-deep references.

De-duplicate recurring phrases like 'Run npx --yes n8nac env status --json' and 'stop after two repeated failures with the same diagnostic' by stating each rule once and back-referencing it.

Consider extracting the TypeScript authoring rules (decorators, .uses() AI connections, workflow-map navigation) into a references/authoring.md to reduce body length and token load.

DimensionReasoningScore

Conciseness

Lean and free of padding about concepts Claude already knows — it is dense n8n-as-code specifics throughout — but there is noticeable repetition (e.g. 'env status --json' and 'stop after two repeated failures' recur across sections) that could be tightened, keeping it just below the score-5 'every token earns its place' bar.

4 / 5

Actionability

Fully executable guidance: exact `npx --yes n8nac ...` and `npx --yes @n8n-as-code/n8n-manager ...` commands with flags, plus copy-paste-ready TypeScript decorator examples and AI sub-node wiring patterns covering the common cases.

5 / 5

Workflow Clarity

Clear numbered sequences ('Bootstrap Order', 'Operating Loop') with explicit validation checkpoints (`--verify`, `--json`, `test-plan`), error-feedback loops ('stop after two repeated failures with the same diagnostic'), and dedicated conflict-resolution and destructive-op safeguards.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections, but the skill is a large single-file monolith (no references/, scripts/, or assets/ bundle files exist) so everything is inlined; the simple-skill exception does not apply at this length, keeping it just below the score-5 one-level-deep-reference bar.

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.

A strong, specific, third-person description that cleanly answers both 'what' and 'when' and occupies a distinct niche. The only minor gap is somewhat repetitive keyword vocabulary centered on 'n8n' with limited synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create, edit, validate, sync, or troubleshoot n8n workflows' — giving comprehensive coverage of the skill's capabilities, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both what (create/edit/validate/sync/troubleshoot workflows) and when via the 'Use when the user explicitly wants...' trigger clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural terms ('n8n workflows', 'n8n nodes', 'automation', 'n8n-as-code') a user would say, but the vocabulary is narrow around 'n8n' with few synonyms or file-extension-style triggers, leaving a few natural variations missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche — n8n-as-code workflow management — with distinct triggers that are unlikely to fire for unrelated skills, giving minimal conflict risk.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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