Email crafting

Skill Xuxchloris/export_skills/skills/email-crafting

Use when a trade agent needs cold email, follow-up email, outreach copy, subject lines, reply drafts, personalization, multilingual trade email, or buyer-facing message draftsFrom its SKILL.md

Install

npx -y skills add Xuxchloris/export_skills --skill email-crafting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 538 tokens by cl100k_base, as published. Nobody here has run it

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

Confirm the prospect priority is A or B. For C prospects, write only if the user explicitly asks. For D prospects, recommend no outreach.
Check personalization_evidence. If no fetched evidence is present, return draft_status: "blocked_no_evidence" and explain what evidence is missing.
Do not invent company activity, buyer intent, product interest, contact names, or sourcing needs.
Select one concrete personalization point from company research.
Select one matching product value point from product context.
Write a short subject line without spammy wording.
Write 120-160 words unless the user requests a different length.
Structure the body:
- opening line based on prospect evidence
- product relevance
- one proof point such as certification, specification, or manufacturing capability
- light CTA
- signature
Add an opt-out line for regions where cold outreach compliance requires it.
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

What ships with it: 1 file

480 B alongside SKILL.md

references/

email-style-guide.md480 B