Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Client Handoff Package

    1

    Audit a project for secrets, internal notes and tool traces before you hand it to a client, then generate the client README, .env.example and a handoff PDF.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Client Handoff Package

    Client Handoff Package

    Example session with this skill installed

    I need to deliver the project to the client. Please audit the repo for secrets or AI traces and prepare the handoff package.

    • Read your context and instructions
    • Compiled the client handoff package
    • Generated the document

    I have completed the audit and prepared the handoff package for the project. The audit identified two blockers (an internal CLAUDE.md and a local path warning) which were resolved by excluding them from the final export.

    Handoff Audit & Package Summary

    CategoryStatusDetails
    SecretsPassNo active API keys or .env files detected.
    Tool TracesClearedRemoved "Generated by Claude" headers from 3 files.
    Internal FilesExcludedCLAUDE.md and .cursor/ removed from delivery.
    Local PathsFixedReplaced /Users/dev/project with relative paths.
    DocumentationGeneratedREADME.md, .env.example, and HANDOFF.pdf created.

    Delivery Package Content

    delivery_2023-10-27.zip
    ├── src/
    ├── public/
    ├── .env.example
    ├── HANDOFF.pdf
    ├── LICENSE
    ├── package.json
    └── README.md
    

    The HANDOFF.pdf includes project overview, tech stack, and deployment instructions tailored for the business owner. The README.md provides technical setup steps for their internal team.

    Next steps

    1. Review the generated HANDOFF.pdf to ensure the business details are correct.
    2. Transfer the production API keys via your secure password manager.
    3. Send the delivery_2023-10-27.zip archive to the client.

    HANDOFF.pdf

    PDF · document

    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

    Deliver the code, not your working notes

    The most embarrassing handoff mistakes are small: a .env.local in the zip, a CLAUDE.md or .cursor/ folder, "Co-Authored-By" lines in git history, a /Users/you/... path in a config. Client Handoff Package finds them before the client does, then writes the documents a business owner actually needs.

    1. Audit (read-only)

    One command scans the project and exits with code 1 when blockers exist:

    ClassExamplesSeverity
    Secrets.env* files, private key blocks, API key patterns (AIza, ghp_, sk-, AKIA, xox)Blocker
    Internal filesCLAUDE.md, AGENTS.md, .claude/, .cursor/, stray notes and .md filesBlocker
    Tool traces"Co-Authored-By", "Generated with", assistant or tool names in source and commentsBlocker
    Local paths/Users/..., C:\Users\...Warning
    LeftoversTODO, FIXME, console.log in srcWarning

    2. Export clean

    Remove or relocate blockers and deliver a git archive export: it holds tracked files only, so ignored files and node_modules never leave your machine. If your history carries tool traces, you ship a fresh export instead of the repository.

    3. Write the documents

    Templates for a plain-language client README, a .env.example and a handoff document, with simple {{placeholders}}. The reader is the business owner, not a developer. A script converts the handoff document to PDF with headless Chrome.

    4. Final check

    Re-run the audit on the unzipped archive, open the PDF, and confirm the client can run the project from the README alone. Credentials travel through a password manager or a separate channel, never in the package.

    Requirements

    Node 18+, git, and Google Chrome or Chromium for the PDF step. Works with Claude Code and any agent that follows the SKILL.md standard.

    Requires Node.js and headless Chrome for PDF generation. Git history cleanup is not automated; the skill suggests fresh archives instead.

    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 15 days ago

    Requires

    Node.js
    Git

    Permissions

    Terminal / Shell
    Write Files
    Listed15 days ago

    What's inside

    Frequently Asked Questions

    This skill automatically scans your codebase for sensitive data like API keys, hardcoded file paths, and internal AI tool metadata, then generates a clean, client-ready ZIP archive and professional PDF documentation.

    Yes, the skill uses 'git archive' to ensure only tracked files are included, and it specifically identifies and removes internal files like CLAUDE.md and local environment configurations.

    This skill requires a Node.js environment and a headless Chrome instance for PDF generation; it is compatible with AI agents that support local file system access and terminal execution.

    The skill provides a read-only audit of your Git history; if it detects sensitive traces in past commits, it will recommend a clean export rather than attempting to rewrite your repository's history.

    You receive the full skill package including the audit scripts, professional Markdown-to-PDF templates, and automated cleanup workflows ready to be integrated into your agent.

    The skill uses specialized pattern matching and secret detection logic that is more reliable than a standard LLM prompt, which can often overlook hidden files or deeply nested console logs.

    New in Business & Operations