Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    n8n Brief-to-Build Pipeline

    1

    Plan, build, QA, document and hand over n8n workflows end-to-end: importable JSON, a deterministic validator, a client handover doc and a Telegram alert.

    $5.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    n8n Brief-to-Build Pipeline

    n8n Brief-to-Build Pipeline

    Example session with this skill installed

    Every morning at 9am, pull new leads from a Google Sheet, score them with AI, and send a summary to Slack.

    • Read your context and instructions
    • Compiled the n8n brief-to-build pipeline

    Plan saved (01_plan.json) \u2192 workflow built (02_workflow.json, with Error Trigger + credential placeholders) \u2192 QA: PASS (validate_workflow.py + logic review) \u2192 client handover written (04_client_handover.md) \u2192 Telegram alert sent: 'Workflow ready \u2014 link your Google Sheets, OpenAI and Slack credentials, then run one test.'

    Plan saved (01_plan.json

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Plan, build, QA, document and hand over n8n workflows end-to-end: importable JSON, a deterministic validator, a client handover doc and a Telegram alert.

    What's included

    • n8n-workflow-builder: End-to-end n8n workflow delivery pipeline for freelancers and agencies. Turns a plain-English automation idea into an importable n8n workflow JSON, validates it with a deterministic checker plus a logic review, writes a plain-English client handover document, and sends a Telegram "ready" alert. Use when the user says "build me an n8n workflow", "I want an n8n automation that...", "create a flow for...", "validate/check this workflow JSON", "write the client handover for this workflow", or describes any multi-step automation (triggers, APIs, databases, AI agents, messaging) to be built in n8n.
    • n8n-builder: Converts a structured n8n workflow plan (JSON from n8n-planner) into a complete, valid, production-ready n8n workflow JSON. Use this skill after n8n-planner has produced a plan at ./n8n-build-state/01_plan.json, or when the user says "build the workflow", "generate the n8n JSON", "produce the workflow file", or "turn this plan into n8n". ALWAYS read references/n8n-syntax-rules.md before writing any JSON to avoid silent-failure traps.
    • n8n-documenter: Creates client-facing documentation for a completed n8n workflow, explaining in plain English what it does, how it works step-by-step, the logic behind decisions, and benefits/use cases. Use this skill after n8n-qa-validator has approved a workflow (status PASS), or when the user asks to "document this workflow", "write the client explanation", "create the handover doc", or "generate the PDF content". Outputs structured Markdown ready to convert to PDF.
    • n8n-notifier: Sends a Telegram alert when an n8n workflow has been built, validated, and documented — telling the user what was built, how to test it, and any credentials needed. Use this skill LAST in the n8n build pipeline, after n8n-qa-validator has passed (status PASS) and n8n-documenter has produced the handover doc. Also use when the user explicitly says "notify me", "send the Telegram alert", or "wrap it up and ping me".
    • n8n-planner: Designs a complete n8n workflow plan from a natural-language request, producing a structured JSON plan before any workflow JSON is written. Use this skill FIRST in the n8n build pipeline whenever the user describes an automation they want built, says things like "build me a workflow", "I want an n8n automation that...", "create a flow for...", or describes any multi-step process involving triggers, APIs, databases, AI agents, or messaging platforms. Always run before n8n-builder.
    • n8n-qa-validator: Reviews a freshly-built n8n workflow JSON and produces a structured QA report detecting broken connections, empty parameters, missing credentials handling, and unhandled failure points. Use this skill after n8n-builder has produced a workflow at ./n8n-build-state/02_workflow.json, or when the user asks to "validate the workflow", "check for issues", "QA the build", or "make sure nothing's broken before I import". Always runs before n8n-notifier in the pipeline.

    Does not execute workflows inside n8n (static validation only: import, link credentials and run one test before delivery). Node versions are a snapshot verified 12 Nov 2026. Nodes without a template (Switch, Notion, HubSpot, etc.) are built from n8n's definitions and reported as unverified.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    Requires

    Python 3
    An n8n instance (to import workflows)
    Python

    Permissions

    Allowed Hosts

    api.telegram.org (optional alerts)
    your own n8n instance (optional push)

    File Scopes

    ./n8n-build-state/
    (read/write)
    .gitignore
    (adds
    config.json
    entry)

    Reads optional tokens from ./n8n-build-state/config.json and never prints them. Network calls only happen if you configure Telegram or n8n push.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    No. It builds and statically validates the workflow JSON. You import it into n8n, link your own credentials and run one test execution before handing it to a client.

    Verified against the n8n source on 12 Nov 2026 for 23 common nodes. Older versions still import and are reported as 'outdated', not broken. Nodes without a template are reported as unverified.

    No. It is optional. You can use just the planner, builder, validator and documenter. Telegram alerts and pushing to your n8n instance only run if you add the keys to a config file.

    Yes. Run any single stage, for example 'validate this workflow JSON' or 'write the client handover for this workflow'.

    New in Workflow Automation