Live todaysip_action: generate_report
Client reporting twin
Produces the recurring client report and emails it, with a signed receipt as proof of delivery.
- Buyer
- Agencies and freelancers who owe clients a weekly or monthly report.
- Adapter needed
- Gmail (live)
- Time back
- 4–8 hours / month per client
- Monetisation
- Subscription / retainer · Bundle into a monthly retainer, invoiced outside the platform
Why someone pays for this
The receipt is the differentiator: you can prove the report went out on time, which is exactly what retainer disputes are about.
Starting manifest
SKILL.md
---
name: Client Report
category: reporting
sip_action: generate_report
adapter: gmail:live
risk: medium
requires_approval: true
visibility: private
---
# Client Report
## What it does
Generate the agreed recurring report for one client and email it to the
recipient recorded on the task.
## Deterministic rules
- Only use metrics from connected sources; never estimate a missing number
- State the reporting period explicitly in the first line
- Never send to any address other than the recipient on the task
- Attach the receipt verify link in the footer
Tutorial steps
- 1Create one skill per report format; keep the scope narrow.
- 2Connect Gmail and record the client recipient on the task.
- 3Delegate a dry run, check the delivery log, then promote to live.
- 4Send the client the verify link with the first real report.
The Decision Card must show
- ·Low risk for internal data; medium once it sends to an external client.
What the receipt proves
The report content hash, the recipient and the send time.
Honest limits
- It reports on connected data only — it cannot pull from a system you have not connected.
- Delivery failures are recorded, not hidden.