- Home
- Skills
- DevOps & Cloud
- Handover Sheet — every account and renewal your client owns
More screenshots
Works with the AI Agents you already use
Handover Sheet — every account and renewal your client owns
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
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.
| Account | Used for | In the shop's name | Monthly cost |
|---|---|---|---|
| Cloudflare | domain and DNS | ✅ | domain billed yearly |
| Shopify | online store, orders, payments page | ✅ | USD 39 |
| Stripe | payments and refunds | ✅ | fees per payment |
| AWS | nightly backups | ✅ | under USD 1 |
| Password manager | all logins, vault Bean & Kettle | ✅ | owner's plan |
| Render | back office and shop database | ⬜ before go-live | USD 13 |
| GitHub | the back office's code, backup job | ⬜ before go-live | free |
| Sentry | error alerts | ⬜ 2027-02-09 | free |
Renewal calendar
| When | What | Auto | Who pays | If it lapses |
|---|---|---|---|---|
| every month | Shopify Basic plan | yes | shop | the online store closes |
| every month | Render web service and database | yes | developer until transfer, then shop | the back office and the order database stop |
| every month | AWS storage | yes | shop | new backups stop; old ones are deleted after 30 days |
| about every 90 days | Security certificates for both addresses | yes, by Render and Shopify | included | browsers warn visitors |
| 2027-02-09 | End of support: Sentry moves to the shop; developer access is removed | — | — | — |
| 2027-03-14 | Domain beanandkettle.example | yes | shop | both addresses stop working |
Backups and restore
| Item | Current state |
|---|---|
| What | the whole shop database (orders, customers, products) |
| When | every night at 02:30 UTC |
| Where | AWS storage bean-and-kettle-backups, owner's AWS account |
| Kept for | 30 days; older copies are deleted automatically |
| Who can download | the owner (AWS sign-in); copies contain customer names and emails |
| Last restore test | 2026-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
| Account | Login kept in | 2-step codes | Recovery email |
|---|---|---|---|
| Cloudflare, Shopify, Stripe, AWS | owner's password manager, vault Bean & Kettle | owner's phone | owner's |
| Render, GitHub | developer's until transfer; then the owner's vault | owner's phone after transfer | owner's after transfer |
| Sentry | developer's until 2027-02-09 | developer's | developer's |
No password, key or recovery code is written in this document.
Transfers
| Item | Who does what | By | |
|---|---|---|---|
| ✅ | Domain and DNS | already in the owner's Cloudflare account | — |
| ✅ | Shopify, Stripe, AWS | already in the owner's name and paid by the shop | — |
| ⬜ | Render | owner creates a Render workspace; developer transfers both services and the owner adds the shop's card | before go-live |
| ⬜ | GitHub | developer transfers the repository to the shop's organisation; then runs the backup job once and checks AWS | before go-live |
| ⬜ | Sentry | developer moves the project to a Sentry organisation owned by the shop | 2027-02-09 |
| ⬜ | Developer access | developer leaves Cloudflare and Shopify; owner confirms | 2027-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
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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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
Allowed Hosts
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.