More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    n8n Client Handoff Proof Pack

    1

    Turn one exported n8n workflow into a clear five-file client handoff packet with dependency inventory, review blockers, acceptance scenarios and tamper-evident hashes.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    n8n Client Handoff Proof Pack

    n8n Client Handoff Proof Pack

    Example session with this skill installed

    Create a client handoff proof packet for ./workflow.json using ./acceptance-spec.json. Put the result in a new ./client-handoff directory. Do not run or modify the workflow, connect to n8n, or expose credential IDs or secret values.

    • Read your context and instructions
    • Compiled the n8n client handoff
    • Generated the data export

    Handoff status: READY

    The packet is ready for client human review. READY does not certify production safety and does not claim that the workflow was executed.

    Workflow inventory

    • Workflow: Lead Intake Handoff Demo
    • Nodes: 2
    • Connections: 1
    • Flow: Manual Trigger → Prepare Lead
    • Community-node dependencies: none detected
    • Credential IDs exposed: 0
    • Suspected literal secrets: none detected in this sample

    Client setup

    The client must create or select each required credential in the client-owned n8n instance. Secret values are not copied into the packet. Referenced environment variables and dependency questions are listed for human review.

    Acceptance matrix

    ScenarioExpected resultEvidence status
    Valid lead inputPrepare the normalized lead recordPending client-observed execution
    Missing required fieldFollow the agreed failure pathPending client-observed execution

    Generated files

    1. handoff.json — authoritative structured result
    2. HANDOFF.md — readable client summary
    3. credential-requirements.csv — setup responsibilities without credential IDs
    4. test-matrix.csv — manual acceptance scenarios
    5. evidence-receipt.json — SHA-256 integrity hashes

    Next steps

    Open HANDOFF.md with the client, configure credentials only inside the client-owned n8n instance, run the pending acceptance cases, and record the observed evidence before deployment.

    credential-requirements.csv

    CSV · data export

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    Finishing an n8n build is only part of client delivery. The client still needs to know what the workflow contains, which credentials and variables they must configure, how they should test it, and what remains unverified.

    This Skill reads one local n8n workflow JSON export and an optional acceptance specification, then creates:

    1. handoff.json, the authoritative handoff record;
    2. HANDOFF.md, the readable client summary;
    3. credential-requirements.csv, without credential IDs;
    4. test-matrix.csv, the manual acceptance-test matrix; and
    5. evidence-receipt.json, the SHA-256 integrity receipt.

    It flags incomplete handoff information, community-node dependencies, pinned data, disconnected nodes, malformed connections and suspected literal secrets. Statuses are deterministic: BLOCK, REVIEW, or READY for client human review.

    The Skill runs locally with Python's standard library. It does not connect to n8n, access accounts or credentials, execute a workflow, test third-party APIs, repair workflow logic or certify production readiness.

    Best for:

    • n8n freelancers preparing milestone or final delivery
    • small automation studios standardizing client handoffs
    • technical operators receiving a workflow from another builder

    Requirements:

    • A workflow JSON exported by an authorized user
    • Python 3.11 or newer
    • Optional acceptance-spec JSON for the strongest packet
    • Human review and live testing before deployment

    Limitations:

    • Secret detection is heuristic and cannot prove an export is secret-free.
    • Inputs are limited to 5 MiB each and are parsed locally in memory.
    • The packet records pending human tests; it never fabricates successful execution evidence.
    • Source authenticity, business correctness, live API availability, performance and production safety remain outside scope.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.

    • Static local inspection only: the Skill does not execute the workflow, call third-party APIs, or certify production readiness.
    • Secret detection is heuristic and cannot prove an export is secret-free.
    • Inputs are limited to 5 MiB each and are parsed locally in memory.
    • Acceptance tests remain pending until a human runs them and records evidence.
    • Source authenticity, business correctness, live API availability and performance remain outside scope.

    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 buying a skill.

    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 2 months ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    ./**

    Uses the local terminal to run Python. Reads only the workflow JSON and optional acceptance-spec JSON selected by the user, then writes one new handoff directory inside the current working directory. No browser, network, secret-store or environment-variable access.

    Listed2 months ago

    What's inside

    Frequently Asked Questions

    No. It creates handoff evidence and identifies static delivery blockers or review items.

    No. It reads only the local files you choose to provide.

    No. READY means the handoff packet contains enough information for client human review.

    No. V1 is a one-time downloadable Skill. Future compatibility changes, if any, will be evaluated separately and are not promised.

    New in Workflow Automation