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

88%

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

85%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 content is highly actionable and workflow-sequenced with strong validation discipline, assuming Claude's competence throughout. Its main weaknesses are repeated command blocks across sections and a single-file monolith that would benefit from splitting detailed reference material into bundled files.

Suggestions

Split the Knowledge Commands catalog, AI/LangChain Node Rules, and Common Mistakes into separate reference files under ./references/ and link to them one level deep, leaving SKILL.md as a concise overview — this would raise progressive_disclosure and trim the monolith.

De-duplicate repeated command blocks: `env status --json`, `env add ... --workflows-path`, and the managed-instance `create`/`start` sequences each appear in multiple sections — reference one canonical block instead of restating.

Consolidate the Bootstrap Order, Environments, and Managed Local Runtime sections so the readiness decision tree is stated once, reducing token cost without losing the validation checkpoints.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanations of what n8n or TypeScript decorators are), but several commands are repeated across sections — `npx --yes n8nac env status --json`, `env add`, and the managed-instance `create`/`start` blocks appear two or three times — so not every token earns its place.

4 / 5

Actionability

It provides copy-paste-ready bash commands and a complete executable TypeScript workflow skeleton, plus exact parameter shapes such as `{ __rl: true, value: '...', mode: 'list' | 'id' | 'url' }`, covering the common authoring and sync cases.

5 / 5

Workflow Clarity

The Bootstrap Order and Operating Loop are numbered sequences with explicit validation checkpoints (`accessStatus: "ready"`, `push --verify`, `test-plan`), and destructive/batch operations have feedback loops (stop-and-inspect on conflict, stop after two repeated failures), so the destructive cap does not apply.

5 / 5

Progressive Disclosure

The file is well-sectioned with clear headers, but it is a ~530-line monolith with no bundle files and no one-level-deep references; content such as the long Knowledge Commands catalog, AI/LangChain rules, and Common Mistakes could be split into separate reference files for easier navigation.

3 / 5

Total

17

/

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, third-person description that names concrete actions and gives explicit trigger guidance covering multiple natural user phrasings. Its only gap is the absence of file-extension synonyms that would round out trigger-term coverage.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "create, edit, validate, sync, or troubleshoot n8n workflows" — giving comprehensive coverage of the domain rather than just naming it.

5 / 5

Completeness

It explicitly answers both "what" (create/edit/validate/sync/troubleshoot workflows) and "when" ("Use when the user explicitly wants… asks about n8n nodes… or wants to use n8n-as-code") with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes natural phrases users would say ("n8n workflows", "n8n nodes", "automation", "n8n-as-code") but omits synonyms and file extensions like ".workflow.ts", stopping short of comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The n8n-as-code / n8n-workflow niche is specific with distinct triggers, making overlap with unrelated skills minimal.

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

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