- Home
- Skills
- Technical Documentation
- DB Handover — a database report your client can read
More screenshots
Works with the AI Agents you already use
DB Handover — a database report your client can read
Turns your project's database into a plain-language handover document for the client: what each table holds, how they connect (ER diagram), what the statuses mean, where personal data lives, and the agreed actions.
$5
DB Handover — a database report your client can read
Example session with this skill installed
Write a database handover document for my client from this project. The reader is the shop owner, not a developer.
- Read your context and instructions
- Compiled the db handover
- Generated the document
Bean & Kettle online shop: Database handover
Version 2026-11-09 ·
Database SQLite ·
Source live database (read-only; no application code was provided) ·
For the shop owner
Fictional example. Bean & Kettle is a made-up coffee-gear shop; all names and numbers are invented.
At a glance
This database holds what the online shop needs to take and track orders: who your customers are, what you sell, and every checkout with the products in it. It holds
no payment card details.
| Area | Table | One row is… | Rows |
|---|---|---|---|
| Customers | customers | one customer account (3 are internal test accounts) | 180 |
| Catalogue | products | one product you sell | 8 |
| Orders | orders | one checkout, including cancelled and refunded ones | 759 |
| Orders | order_items | one product line inside a checkout | 1,537 |
Orders run from January to October 2026.
erDiagram
customers ||--o{ orders : "places"
orders ||--|{ order_items : "contains"
products ||--o{ order_items : "appears in"
Table by table
Orders (orders)
What it stores: one row per checkout, whatever happened to it afterwards.
| Field | Meaning | Example | Rules |
|---|---|---|---|
customer_id | Who placed the order | 42 | must be an existing customer |
status | Where the order is now | shipped | see "Status values" below |
created_at | When the checkout happened | 2026-10-03T21:15:00Z | UTC time |
total | Order value | 62.00 | equals the sum of its product lines (checked on all 759 orders) |
Watch out:
- Cancelled and refunded orders are still here. Revenue = paid + shipped only.
- Times are stored in UTC, so reports group orders by UTC day and month, not by your local day.
Order lines (order_items)
| Field | Meaning | Example | Rules |
|---|---|---|---|
qty | How many | 2 | whole number |
unit_price | Price charged per unit | 48.00 | copied from the product price at checkout; later price changes don't affect it |
Watch out: when you add up sales from this table, don't also add the order total; you would count the same money twice.
(Customers and Products sections follow the same layout in the full document.)
Status values and business rules
| Value | Meaning | Orders | Counts as revenue? |
|---|---|---|---|
paid | Payment received, not shipped yet | 239 | yes |
shipped | Sent to the customer | 398 | yes |
cancelled | Cancelled before shipping | 76 | no |
refunded | Money returned to the customer | 46 | no |
Personal and sensitive data
- Personal fields:
customers.name,customers.email. - No passwords are stored: customers check out as guests. No payment card data is stored here.
- Backups and exports contain customer names and emails: store them as carefully as the live system.
Recommended actions
| Current state | Action | Who | When |
|---|---|---|---|
| 3 internal test accounts (10 orders) sit alongside real customers | Keep them for testing; all revenue figures already leave them out | developer | ongoing |
| Reports group orders by UTC day and month | Switch report grouping to the shop's local time | developer | phase 2 |
| Orders have no field for the payment provider's refund reference | Add one when refunds are saved | developer | before go-live |
| Backups and exports contain customer names and emails | Limit backup downloads to the owner account | shop owner | before go-live |
Delivered as db-handover.md plus a print-ready db-handover.html (cover, contents, ER diagram). The full example is in examples/ inside the package.
db-handover.html
PDF · document
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
The project is done, and the client asks: "So what's in the database?" You can send them a schema dump, or you can send them this.
DB Handover reads your schema (live database, read-only, or your migrations / ORM models) and writes db-handover.md, a handover document written for the client, not for developers:
- At a glance: every table in plain words ("one row = one checkout, including cancelled ones"), row counts, and a Mermaid ER diagram.
- Table by table: key fields in business language, made-up example values, rules, and the "watch out" notes people always get wrong (cancelled orders still in the table, times in UTC, amounts in cents).
- Status values and business rules: what each status means and what sets it.
- Personal and sensitive data: where emails and names live, how passwords are stored, what to protect in backups.
- Recommended actions: current state · action · who · when, so the client sees decisions, not loose ends.
- Asks you first: anything the schema can't tell (what a column really means, whether test accounts stay) is put to you in one batch before writing. The client gets facts in your name, never guesses or open questions.
Safe for client delivery
- Read-only. Never copies real personal values, secrets or hostnames into the document; examples are made up.
- No internal notes (TODO, drafts, developer names) in the client version.
- A final checklist runs before handover.
Every document also comes as a styled single-file HTML, print-ready for PDF. Writes in your language (English, Chinese, Japanese and more).
See examples/db-handover-example.md for the full document it produced for a fictional coffee-gear shop.
Works with Claude Code, Codex CLI, Gemini CLI, Cursor and other agents that can read files and run shell commands.
Meaning comes from names, code and data; tables with cryptic names and no code mean more questions for you before writing. Very large schemas are documented by business area; you may need to point it at the relevant ones.
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 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 8 days ago
Requires
Permissions
Reads your schema files or connects read-only to a database you name, runs the included render script to produce the HTML, and writes the handover document into your project folder. It never writes to the database.