Revenue snapshot
Summarise revenue for a period (new, expansion, churn, refunds, failed payments) against the last period, with a chart. Read-only.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone wants to know what came in over a week, month or quarter and why it moved — usually from Stripe or a billing export.
- 01
Fix the period, timezone and currency first, and state them at the top. Most arguments about revenue are arguments about where a day ends.
- 02
Read only. Never refund, cancel, retry a charge or edit a customer, even when the connection would allow it.
- 03
Pull each figure for this period and the last:
- total collected, and recurring revenue if there are subscriptions;
- new customers and what they brought in;
- upgrades and downgrades;
- cancellations and the revenue lost with them;
- refunds and disputes;
- failed payments still unpaid.
- 04
Show every figure beside last period's, with the change. Put the main series in a chart fence.
- 05
Explain the biggest moves, including dull causes: a billing date that moved, an annual renewal, a batch of refunds, a price change.
- 06
Mark a figure "missing" when you could not get it. Never estimate one to fill the gap.
- 07
Post it as a document, headline first, and the figures as a spreadsheet with post_spreadsheet. Offer to repeat it on a schedule, and ask before saving it.
Leave individual customer names out unless the person asks for them.
The whole SKILL.md: 37 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: revenue-snapshotdescription: "Summarise revenue for a period (new, expansion, churn, refunds, failed payments) against the last period, with a chart. Read-only."metadata: title: "Revenue snapshot" category: finance tags: [finance, revenue]--- ## When to use this Someone wants to know what came in over a week, month or quarter and why itmoved -- usually from Stripe or a billing export. ## How 1. Fix the period, timezone and currency first, and state them at the top. Most arguments about revenue are arguments about where a day ends.2. Read only. Never refund, cancel, retry a charge or edit a customer, even when the connection would allow it.3. Pull each figure for this period and the last: - total collected, and recurring revenue if there are subscriptions; - new customers and what they brought in; - upgrades and downgrades; - cancellations and the revenue lost with them; - refunds and disputes; - failed payments still unpaid.4. Show every figure beside last period's, with the change. Put the main series in a chart fence.5. Explain the biggest moves, including dull causes: a billing date that moved, an annual renewal, a batch of refunds, a price change.6. Mark a figure "missing" when you could not get it. Never estimate one to fill the gap.7. Post it as a document, headline first, and the figures as a spreadsheet with post_spreadsheet. Offer to repeat it on a schedule, and ask before saving it. Leave individual customer names out unless the person asks for them.
- Finance
Spend review
Review a card or bank export: categorise every line, flag duplicates, new subscriptions and price rises, and total spend against last month.
SKILL.md · App - Finance
Invoice follow-up
List overdue invoices by age and amount, and draft a reminder for each customer in a tone that fits how late it is. Sends nothing and promises nothing.
SKILL.md · App - Finance
Payouts against the bank
Match a period's Stripe payouts against the bank feed line by line, and list what does not match — a missing deposit, a duplicate charge, a fee that moved — with the refund or fix left for a person.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App