agentleFS
BenPremBenPrem/business-brain/.claude/skills/email-composer/SKILL.md

email-composer

Skill1 starsChanged 3 months agoMITView on GitHub

Draft one-off operational emails to people the founder already knows - client status updates, vendor/partner requests, graceful declines. Trigger on write an email to [known contact], reply to [name], draft a check-in. ROUTING - recipient has a workspace record with NO active sales stage; active pipeline stage, use follow-up-nurture; no record at all, use cold-email; automated sequences, use a dedicated series skill.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    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
  1. Distinctive:

    Read the recipient's record first — the contact/client record in your workspace and recent activity notes for relationship state, open …

    line 21
  2. Distinctive:

    If any client has industry-specific compliance rules on file (financing language, regulated claims, legal disclaimers), check the email …

    line 27
  3. Distinctive:

    Update the matching task in <TASK SYSTEM> (comment + due date if it moved).

    line 57

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Email Composer

One-off operational emails to existing relationships: clients, vendors, partners.

Voice (non-negotiable)

Professional but approachable. "We" not "I" in anything client-facing (presents as a team). No emojis in client-facing email. Lead with the recipient's problem or need, not your own update. Banned filler (same list as cold-email): "I hope this email finds you well," "I wanted to reach out," "touch base," "circle back," "synergy," "leverage." Sign off with <YOUR NAME> or "<YOUR NAME> — <YOUR BUSINESS>." Never "Best regards."

Before drafting

Read the recipient's record first — the contact/client record in your workspace and recent activity notes for relationship state, open commitments, and the last touchpoint. Only ask the founder for context the records do not hold. Never state a fact about the relationship (dates, promises, amounts) you cannot see in a record — guessed facts in a real email are how trust dies.

If any client has industry-specific compliance rules on file (financing language, regulated claims, legal disclaimers), check the email against them before it goes anywhere.

Scenario shapes (not scripts)

Client status update. Subject is concrete: "<CLIENT> site — this week's progress." Body: (1) what shipped, plain-language bullets; (2) what is next plus any date that moved; (3) one clear ask, or "nothing needed from you." Flag risks early — never bury a slipped date.

Vendor / partner request. Subject names the deliverable: "<CLIENT> transfers — domain + business-profile status." Body: one line of context, the requested items as a checklist, a date ("does Friday work?"), and what it unblocks. Firm, courteous, zero filler. Cite prior commitments from the activity log, not memory.

Graceful decline. Thank them and name the specific thing declined; one honest sentence of reason (capacity, focus); leave a door open only if the founder actually wants one. Never commit future work as a softener.

Output

Subject + body, plus a 1-2 sentence note flagging anything that needs the founder's judgment (tone risk, implied commitments). The founder sends — the agent never sends directly.

After the founder sends

  1. Log an activity note in the workspace record: date, email-sent, a 1-2 sentence summary, any follow-up date. Verify the file exists on disk.
  2. Update the matching task in <TASK SYSTEM> (comment + due date if it moved).

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.