skillboardUpdated every 6 hours
skillboardHandles 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.
Post Build Flow Use this skill after succeeds on a direct orchestrator build, especially when the build result contains , or when the current message contains or . One off builds ( ) hand off to the skill instead — verification is optional there and completion is a live run with read back. If both sets of instructions are in context for a one off build, the one off flow wins. These instructions are in English, but user visible text you write while following them stays in the user's conversation…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/post-build-flow · pinned to the source commit
git clone https://github.com/n8n-io/n8n.git
cd n8n
git checkout b4d91bfe8a293106815b308a841e210562002735
mkdir -p ".claude/skills/post-build-flow"
cp -r "packages/@n8n/instance-ai/skills/post-build-flow" ".claude/skills/post-build-flow"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b4d91bfe8a29. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint 2e9bc6c94a4cbdfe