More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Handover Sheet — every account and renewal your client owns

    1

    Six months after delivery the domain lapses, the hosting bill is still on your card, and the client calls asking where the backups are.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Handover Sheet — every account and renewal your client owns

    Handover Sheet — every account and renewal your client owns

    Example session with this skill installed

    Write the operations handover sheet for my client: every account, domain and renewal this project depends on, and what still needs to move into their name. Support ends in 3 months.

    • Read your context and instructions
    • Compiled the handover sheet

    Bean & Kettle back office: Operations handover

    Handover date 2026-11-09 ·

    For the shop owner ·

    Support period until 2027-02-09 ·

    Sources project files, developer's records

    Fictional example. Services were found by scanning the included project; ownership, costs and dates are the fictional developer's answers.

    At a glance

    Verdict: The system depends on 8 accounts. 5 are already in the shop's name; hosting and code move to the shop before go-live, and error alerts at the end of support on 2027-02-09. The next yearly renewal is the domain on 2027-03-14, with auto-renew on.

    AccountUsed forIn the shop's nameMonthly cost
    Cloudflaredomain and DNS✅domain billed yearly
    Shopifyonline store, orders, payments page✅USD 39
    Stripepayments and refunds✅fees per payment
    AWSnightly backups✅under USD 1
    Password managerall logins, vault Bean & Kettle✅owner's plan
    Renderback office and shop database⬜ before go-liveUSD 13
    GitHubthe back office's code, backup job⬜ before go-livefree
    Sentryerror alerts⬜ 2027-02-09free

    Renewal calendar

    WhenWhatAutoWho paysIf it lapses
    every monthShopify Basic planyesshopthe online store closes
    every monthRender web service and databaseyesdeveloper until transfer, then shopthe back office and the order database stop
    every monthAWS storageyesshopnew backups stop; old ones are deleted after 30 days
    about every 90 daysSecurity certificates for both addressesyes, by Render and Shopifyincludedbrowsers warn visitors
    2027-02-09End of support: Sentry moves to the shop; developer access is removed———
    2027-03-14Domain beanandkettle.exampleyesshopboth addresses stop working

    Backups and restore

    ItemCurrent state
    Whatthe whole shop database (orders, customers, products)
    Whenevery night at 02:30 UTC
    WhereAWS storage bean-and-kettle-backups, owner's AWS account
    Kept for30 days; older copies are deleted automatically
    Who can downloadthe owner (AWS sign-in); copies contain customer names and emails
    Last restore test2026-11-08 by the developer, into a test database: all 759 orders restored and matched the live database

    Watch out: backups are made by the job in the code repository. After the code moves to the shop's GitHub account, the developer runs the job once and checks that the new copy appears in AWS.

    Logins and recovery

    AccountLogin kept in2-step codesRecovery email
    Cloudflare, Shopify, Stripe, AWSowner's password manager, vault Bean & Kettleowner's phoneowner's
    Render, GitHubdeveloper's until transfer; then the owner's vaultowner's phone after transferowner's after transfer
    Sentrydeveloper's until 2027-02-09developer'sdeveloper's

    No password, key or recovery code is written in this document.

    Transfers

    ItemWho does whatBy
    ✅Domain and DNSalready in the owner's Cloudflare account—
    ✅Shopify, Stripe, AWSalready in the owner's name and paid by the shop—
    ⬜Renderowner creates a Render workspace; developer transfers both services and the owner adds the shop's cardbefore go-live
    ⬜GitHubdeveloper transfers the repository to the shop's organisation; then runs the backup job once and checks AWSbefore go-live
    ⬜Sentrydeveloper moves the project to a Sentry organisation owned by the shop2027-02-09
    ⬜Developer accessdeveloper leaves Cloudflare and Shopify; owner confirms2027-02-09

    Sign-off

    • ⬜ I can sign in to Cloudflare, Shopify, Stripe and AWS with logins from our vault.
    • ⬜ Every monthly and yearly bill above is on the shop's card, or has a transfer date.
    • ⬜ I know where the backups are and who can download them.

    The full sheet also covers domain and DNS, hosting and database, outside services and recommended actions, plus a developer appendix with the scan (16 findings). Delivered as handover-sheet.md plus a print-ready HTML with a signature block.

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

    About this skill

    Six months after delivery the domain lapses, the hosting bill is still on your card, and the client calls asking where the backups are. Handover Sheet writes the page that prevents all three.

    • Finds the pieces for you: a scanner reads your deploy configs and scripts (Render, Vercel, Docker, GitHub Actions, EC2 / PM2 / nginx / crontab), dependencies, setting names and scheduled jobs, and lists every hosting provider, domain and outside service it finds. Real secret files are never opened.
    • Real dates, not guesses: certificate end dates and domain expiry are read live (TLS + public RDAP) and stamped "checked on".
    • Ownership settled before writing: whose account, whose card, who still has admin. Everything the files can't tell is asked in one batch, so the client reads facts.
    • Renewal calendar sorted by date, with what happens in business words if each one lapses.
    • Backups and restore: where, how often, how long they're kept, who can download them, and the last tested restore.
    • Where secrets travel: keys printed into logs, settings files copied from a developer's laptop, old .env copies, each listed as current state plus an action.
    • Transfers checklist: ✅ already in the client's name · ⬜ still to move, with who and by when, plus a sign-off the client ticks on receipt.
    • Never a secret on paper: logins are recorded by where they're kept (the client's password manager), never the password, key or recovery code.

    The included example is a real run on a small fictional shop: the scanner finds 16 items across hosting, domains, services and a nightly backup job; the sheet turns them into 8 accounts, 5 already in the shop's name and 3 with transfer dates.

    Every sheet also comes as a styled single-file HTML, print-ready for PDF. Writes in your language (English, Chinese, Japanese and more).

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Expiry checks need public domain names and internet access; for private or fictional names the dates come from you. Costs and account owners are only as accurate as your answers.

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

    Accounts
    Rdap
    Software
    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access

    Allowed Hosts

    rdap.org

    Reads project files (never real secret files), queries public certificate and RDAP records for domains you own, and writes the sheet into your project folder. It never signs in to a provider or changes DNS.

    Listed8 days ago

    What's inside

    Frequently Asked Questions

    No. It reads .env.example-style templates for setting names only; real secret files are listed as present and never opened.

    No. It reads project files and public records only; plans, costs and owners come from you.

    The sheet covers the fixed IP instead: what it is bound to (for example a partner's allow-list), what happens if the server is replaced, and whether the site runs without HTTPS.

    Render, Vercel, Netlify, Fly.io, Heroku-style, Docker, Cloudflare Workers, Firebase, self-managed servers (EC2, PM2, nginx, crontab), GitHub/GitLab/Bitbucket pipelines, plus common services (Stripe, Shopify, AWS, Sentry, SendGrid, Twilio, Supabase, Anthropic, OpenAI…). Anything else you name is added by hand.

    A software company in Taiwan that builds, hands over and rescues business systems. Contact: youllook@gmail.com

    New in DevOps & Cloud