post-build-flow

Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/@n8n/instance-ai/skills/post-build-flow/SKILL.md

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.

The body is highly actionable and its main workflow is sequenced with strong validation gates and feedback loops, appropriate for a destructive/live-run flow. The chief weakness is repetition of publish-readiness and mock-credential rules across several sections, which inflates length without adding clarity.

Suggestions

Consolidate the publish-readiness and mock-credential gating rules into a single canonical section and reference it from the other sections instead of restating the conditions each time.

Pull the credential-recipe field definitions (template, placeholders, docsUrl, testUrl, acceptedStatusCodes) into the references bundle as a separate file, leaving only the worked fal.ai example and the load-the-credential-recipe-research-skill instruction inline.

Dimension	Reasoning	Score
Conciseness	Almost all content is domain-specific n8n policy Claude does not already know, so it avoids explaining known concepts, but publish-readiness and mock-credential rules are restated across "Publishing and testing", "After build-workflow succeeds", "Claiming success", and "Mocked verification live-test follow-up", so it could be tightened.	3 / 5
Actionability	It gives concrete, executable tool calls with specific parameters (e.g. workflows(action="setup", reopenSkipped: ["slackApi"]), verify-built-workflow with triggerNodeName/fixtureOverrides) plus a copy-paste-ready JSON credentialHints example covering the common case.	5 / 5
Workflow Clarity	The 10-step "After build-workflow succeeds" sequence has explicit validation checkpoints (inspect the persisted workflow, judge nodesNotReached coverage), feedback loops (fix and re-verify, seed a test row and re-run, rebuild with fixtures), and clear conditional branching.	5 / 5
Progressive Disclosure	Clear section headers and anchor cross-links aid navigation, and the one external reference (references/trigger-input-data-shapes.md, a real file) is well-signaled and one level deep; most content is appropriately inline for a flow skill, with only minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

70%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 clearly states what the skill does and when it fires, with concrete trigger tokens and good disambiguation from sibling skills. Its main weakness is voice (an imperative "Load..." clause instead of consistent third person) and reliance on system jargon over natural user phrasing.

Suggestions

Rewrite the second sentence in third person to match the opening (e.g. "Loads after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.") to avoid the second-person penalty.

Add a couple of natural user-facing phrases (e.g. "verify a built workflow", "set up workflow credentials") alongside the system trigger tokens so the description matches language a user might actually say.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ("workflow verification and setup after build-workflow succeeds"), matching anchor 3, but the imperative second-person clause "Load after direct builds, when verificationReadiness requires action" triggers the −1 voice penalty, dropping it to 2.	2 / 5
Completeness	It explicitly answers both what ("Handles workflow verification and setup after build-workflow succeeds") and when ("when the message contains workflow-verification-follow-up or workflow-setup-required"; "Load after direct builds, when verificationReadiness requires action") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Relevant domain keywords appear (verification, setup, build-workflow, follow-up) but the dominant trigger tokens are system-internal jargon (workflow-verification-follow-up, verificationReadiness) rather than natural phrases a user would say, so common synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	The trigger conditions are highly specific system tokens tied to the post-build flow, and it explicitly disambiguates by handing one-off builds off to the one-off-operations skill, giving a clear niche with minimal conflict risk.	5 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (546 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: n8n-io/n8n
Path: packages/@n8n/instance-ai/skills/post-build-flow/SKILL.md
Commit: 7700b76

Reviewed: ~5 hours 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.