Email Crafting

Email Crafting

Overview

Write concise B2B trade emails grounded in prospect evidence and product facts. The core rule is that personalization must be earned by research, not invented.

When to Use

Use this skill when the user asks for a first-touch email, follow-up sequence, reply to inquiry, catalog offer, sample discussion, or buyer-facing message.

Do not use it to send email automatically.

Inputs

• Company research output
• Prospect score and priority
• Product context
• Tone rules from TONE.yaml
• Sender signature

Outputs

{
  "subject": "",
  "body": "",
  "draft_status": "draft_ready|blocked_no_evidence",
  "cta": "",
  "personalization_evidence": [],
  "review_notes": []
}

Procedure

1. Confirm the prospect priority is A or B. For C prospects, write only if the user explicitly asks. For D prospects, recommend no outreach.
2. Check personalization_evidence. If no fetched evidence is present, return draft_status: "blocked_no_evidence" and explain what evidence is missing.
3. Do not invent company activity, buyer intent, product interest, contact names, or sourcing needs.
4. Select one concrete personalization point from company research.
5. Select one matching product value point from product context.
6. Write a short subject line without spammy wording.
7. Write 120-160 words unless the user requests a different length.
8. Structure the body:

• opening line based on prospect evidence
• product relevance
• one proof point such as certification, specification, or manufacturing capability
• light CTA
• signature

1. Add an opt-out line for regions where cold outreach compliance requires it.
2. Return review notes for any uncertain claims.

Verification

• The email includes at least one evidence-backed personalization point.
• blocked_no_evidence is used when personalization evidence is missing.
• The email does not claim the prospect buys the product unless evidence says so.
• The email does not include unapproved prices.
• The CTA is light and specific.
• The output is a draft requiring human review.

Common Mistakes

| Mistake | Fix | | --- | --- | | Writing "I saw you are looking for..." without proof | Say "I noticed you carry..." only when visible | | Overloading first email with specifications | Mention one relevant proof point | | Using aggressive sales language | Keep it professional and low-friction | | Sending to D-level prospects | Recommend not contacting them |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Xuxchloris
• Source: Xuxchloris/hermes-export-skills
• License: MIT

Install and usage instructions live in the source repository linked above.