CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

workflow-builder

Load before calling workflow_builder_build_workflow. Once the user wants a workflow, load it before you ask about that workflow. Do not load it to ask about a request that does not yet say what to build. Use for new one-off workflows, edits, repairs and post-build verification of one workflow (not requests only to run or inspect a saved workflow), and for its credentials, model choices, evaluations and error workflow. For any other new workflow, load intent-recognition first when it is listed. If the workflow writes Data Tables, load data-table-manager first. Do a one-time request (no repeat or trigger words) now, without asking whether to repeat it; for one node, load one-off-operations and use execute_node.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 dense, highly operational skill body with an exemplary sequenced process, explicit validation checkpoints and bounded repair loops. The main issues are scattered duplication of credential rules, unfilled template placeholders in the Node Groups section, and one dangling reference (data-table-playbook).

Suggestions

Consolidate the credential guidance from step 4, "Credential Rules" and "SDK Code Rules" into one authoritative section to remove repetition.

Fill or remove the {{GROUPING_GUIDANCE_PLACEHOLDER}} and {{TOP_LEVEL_ITEM_CEILING_PLACEHOLDER}} tokens, since unresolved placeholders leave the Node Groups flow non-executable as written.

Add the missing references/data-table-playbook.md (or drop the reference to it), and give reference names explicit paths (e.g. references/error-workflows.md) for easier navigation.

DimensionReasoningScore

Conciseness

Telegraphic, fully operational prose with no explanation of concepts Claude already knows ("Each extra sequential turn resends the whole context" earns its tokens), matching the 4 anchor of efficient with minor trimmable instances. It is not the 5 because credential guidance is repeated in three places — step 4, "Credential Rules", and the newCredential() rule in "SDK Code Rules" — and not the 3 because there is no genuinely unnecessary explanation.

4 / 5

Actionability

Gives exact tool names, arguments and parameters ("call get_node_types with the exact node IDs… up to ten per call"), a concrete error code with remediation ("GROUPING_DECISION_MISSING… pass groupingDecision: 'not_warranted'"), and a real composition code sample — mostly executable guidance per the 4 anchor. It is not copy-paste ready (5) because the sample uses undefined handles (conditions, handleImportant, sendHolding) and the Node Groups section contains two unfilled {{..._PLACEHOLDER}} tokens, though it is clearly above the pseudocode-level 3.

4 / 5

Workflow Clarity

The 8-step Process is clearly sequenced with explicit validation checkpoints — wait for "preBuild: true", build runs graph/SDK-lint/schema checks, "fix every blocking error", trace every branch — plus bounded feedback loops in Verification ("one repair attempt per unique failure signature"; on "shouldEdit: true", make one batched repair and rebuild). This matches the 5 anchor's explicit validation with error-recovery loops; validation is present and thorough, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The References section gates each of the bundle's 14 reference files behind an explicit trigger, one level deep, and knowledge-base paths are named precisely — good structure per the 4 anchor. It is not the 5 because the "data-table-playbook" reference is cited but absent from references/ (a dangling pointer) and reference names appear in backticks without paths or links, leaving minor navigation gaps.

4 / 5

Total

17

/

20

Passed

Description

78%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 routing-heavy description with an explicit, well-bounded when-clause and excellent sibling-skill disambiguation. Its weakness is that the underlying capability is stated indirectly, and natural trigger vocabulary omits terms like n8n or automation that users would plausibly say.

Suggestions

State the core capability plainly in third person (e.g. "Builds, edits and verifies n8n workflows in TypeScript with @n8n/workflow-sdk") before the routing guidance, making the what as explicit as the when.

Add natural trigger synonyms users would say — "n8n", "automation" — to broaden keyword coverage.

Trim the load-ordering minutiae ("Do not load it to ask about a request that does not yet say what to build") into a single crisp condition to reduce redundancy.

DimensionReasoningScore

Specificity

Names several concrete capabilities — "edits, repairs and post-build verification", "credentials, model choices, evaluations and error workflow" — matching the 4 anchor's several specific actions with minor gaps. It is not the comprehensive 5 because the core what (building workflows in TypeScript with the SDK) is only implied via "Load before calling workflow_builder_build_workflow", and not the sparse 3 because it goes well beyond 1–2 actions.

4 / 5

Completeness

The when is explicit ("Use for new one-off workflows, edits, repairs and post-build verification… not requests only to run or inspect a saved workflow") while the what is present but indirect, fitting the 4 anchor where the when could be more explicit or the what more concrete. It is above the 3 anchor (what only weakly implied) and below the 5 anchor (both stated concretely with trigger phrases).

4 / 5

Trigger Term Quality

"workflow", "edits, repairs", "post-build verification", "credentials" and "error workflow" are natural phrases users would say, giving good keyword coverage per the 4 anchor. It falls short of the 5 anchor's comprehensive synonym coverage because common variations like "n8n" and "automation" are missing, yet sits above the 3 anchor's missing-common-variation level.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche with explicit exclusions and delegations ("not requests only to run or inspect a saved workflow", "load intent-recognition first", "load data-table-manager first", "load one-off-operations"), giving minimal conflict risk — a clean match for the 5 anchor rather than the 4 anchor's minor overlap risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

n8n-io/n8n

Path

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