weekly-saas-finance
Skill14 starsChanged 3 months agoMITView on GitHub
Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Weekly SaaS Finance”. A useful skill states the six fields from Skills and routines. The owner needs a weekly memo of collected revenue, renewals in window, and past-due — not refunds and not dunning. Collected total has source pointers. No refund was issued. No dunning mail was sent. Missing weeks are labeled missing, not backfilled. Weekly memo: collected, renewals, past-due, questions,…
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- convert/claude.mdCLAUDE.md
- docs/llms.txtllms.txt
- audit-subscriptionsSkill
- cited-researchSkill
- cloud-bill-noteSkill
- collate-feature-asksSkill
- coordinate-launchSkill
- daily-digestSkill
- defend-calendarSkill
- design-bot-templateSkill
- detect-docs-driftSkill
- diff-competitorsSkill
- draft-call-followupSkill
- draft-changelogSkill
- draft-issueSkill
- draft-newsletterSkill
- draft-security-answersSkill
- draft-sqlSkill
- draft-support-replySkill
- garden-memorySkill
- harden-repoSkill
- incident-timelineSkill
- install-teamSkill
- interrogate-assumptionsSkill
- investigate-perfSkill
- log-promisesSkill
- package-evidenceSkill
- plan-tripSkill
- prep-meetingSkill
- queue-socialSkill
- ramp-new-hireSkill
- rank-account-healthSkill
- recommend-media-reallocSkill
- reconcile-expensesSkill
- remix-contentSkill
- reproduce-bugSkill
- research-accountsSkill
- review-pr-riskSkill
- route-workSkill
- sanitize-shareSkill
- scout-x-threadsSkill
- source-talentSkill
- sweep-ciSkill
- triage-inboxSkill
- vendor-renewalsSkill
- watch-aeoSkill
- watch-brandSkill
- write-win-lossSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Write the memo to /workspace/saas-finance.md.
- Distinctive: line 40
Do not refund. Do not send dunning.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Weekly SaaS Finance
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Weekly SaaS Finance”.
A useful skill states the six fields from Skills and routines.
1. When to use it
The owner needs a weekly memo of collected revenue, renewals in window, and past-due — not refunds and not dunning.
2. Required inputs and access
- Gmail billing or finance labels
- Last week's memo if it exists in /workspace
- Named customer list if the owner attached one
3. Sequence of work
- Scan mail for payments received, renewal notices, and past-due notices in the week.
- Total collected with source pointers. List renewals in window. List past-due with source.
- Compare to last week if a memo exists. Do not guess ARR from memory.
- Draft an internal memo. Do not send customer-facing dunning.
- Write the memo to /workspace/saas-finance.md.
4. How to validate the result
Collected total has source pointers. No refund was issued. No dunning mail was sent. Missing weeks are labeled missing, not backfilled.
5. What to return
Weekly memo: collected, renewals, past-due, questions, action log.
6. What requires approval
Do not refund. Do not send dunning. Do not change invoices, credits, or tax settings.
Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.