agentleFS
nathan8823nathan8823/fairbill/.claude/skills/send-letter/SKILL.md

send-letter

Skill1 starsChanged 4 months agoMITView on GitHub

Produce a formal letter and get it sent by certified mail (online service or USPS counter). Use for debt validation, 501(r) assertions, formal disputes, settlement offers, and anything the user may later need to prove was received.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start from the right template in templates/letters/.

    line 14

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Formal letters + certified mail

Email is for speed; certified mail is for proof. Use paper when the letter asserts a legal right, sets a deadline, makes a settlement offer, or answers a collector.

Produce the letter

  1. Start from the right template in templates/letters/; personalize completely from the case file.
  2. Formal letter layout: user's name/address, date, provider's billing address (from the bill — verify; disputes often go to a PO box that differs from the payment address), RE: Patient <name>, Account #<number>, Date(s) of service <dates>.
  3. Include the magic line where applicable: "This account is disputed. Please note the dispute in your records." And always: "Please respond in writing to the address above."
  4. Save as markdown in cases/<case>/letters/, then render a PDF for mailing. Check what's available and use the first that works: pandoc x.md -o x.pdf, wkhtmltopdf, weasyprint, or macOS textutil -convert html + cupsfilter. If nothing is installed, have the user open the .md and print to PDF — don't block on tooling.
  5. User reviews and approves the final PDF before anything is sent.

Send it — two paths (user picks)

Online (~$8–12, no post office trip):

  • docupost.com — upload PDF, ~$7 + postage for Certified Mail
  • simplecertifiedmail.com — certified specialist, per-letter pricing
  • mailform.io — upload + Certified w/ Return Receipt

Walk the user through upload; you fill nothing on these sites yourself unless the user explicitly asks and the data isn't payment credentials.

USPS counter (~$5–10): Print the PDF → post office → "Certified Mail with Return Receipt" (the green card, or electronic return receipt). Cheaper, same proof.

Aftermath

  • Tracking number, send date, and service used → case.md.
  • Certified article number goes in the case file AND on the user's copy of the letter.
  • Delivery confirmation (usps.com/tracking) → note the delivered date; that date starts their response clock. No response by deadline → follow-up letter cites "my letter delivered <date>, certified article #<number>" — that sentence is what escalation rungs are built from.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.