draft-collection-email
Skill3 starsChanged 7 days agoApache-2.0View on GitHub
Draft an on-voice customer email (dunning nudge or dispute reply) from Ledgerly seed data. Use when a demo asks for customer-facing copy — e.g. "write the overdue email for INV-1043" — so the model stays in the Fieldnote fiction and never invents a price or a real company.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ledgerly/AGENTS.mdAGENTS.md
- ledgerly/.cursor/rules/disposable-demo-prs.mdcCursor rule
- ledgerly/.cursor/rules/ledgerly.mdcCursor rule
- ledgerly/.cursor/rules/multitask-no-wrapper.mdcCursor rule
- add-dashboard-widgetSkill
- choose-cursor-workflowSkill
- dispatch-subagentsSkill
- hand-to-cloud-agentSkill
- present-runbooksSkill
- reset-demo-stateSkill
- stage-linearSkill
- start-ledgerlySkill
- write-prisma-querySkill
- standard-bug-fixSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 8
Write the email Avery Quinn (Billing ops, Fieldnote Workspace) would send.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Draft a collection or dispute email
Write the email Avery Quinn (Billing ops, Fieldnote Workspace) would send. Ground every fact in the seed; invent nothing.
Pull facts first
- Invoice/customer facts from
prisma/seed.ts(or the running API:http://127.0.0.1:43173/api/invoices/inv_1043). Contact names and.exampleemails are in the seed. - Plan names and prices only from
lib/plans.ts: Starter $49, Growth $99, Scale $249. - Days overdue: compute against the frozen clock (23 Aug 2026,
lib/clock.ts) — e.g.inv_1043due 9 Aug is 14 days past due.
Voice (from .cursor/rules)
Calm, specific, short. "Invoice" and "credit", never "synergy". No exclamation marks, no discount offers, no legal threats.
Hard rules
- Name the plan; quote the price only if it is one of the three catalog prices.
- Fictional parties only — seed customers,
.exampleaddresses, signed "Avery Quinn, Billing ops, Fieldnote Workspace". - Dispute replies must not promise a credit above the plan price. Read the catalog from
lib/plans.ts.
Output shape
Subject line + body under 140 words + one clear ask (confirm payment date, or confirm the plan on the signed order). Offer to save it into the invoice's collection-note field (app/invoices/[id]/page.tsx) only if the user asks to persist it.
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.

