$npx -y skills add Xuxchloris/export_skills --skill email-craftingUse when a trade agent needs cold email, follow-up email, outreach copy, subject lines, reply drafts, personalization, multilingual trade email, or buyer-facing message drafts
| 1 | # Email Crafting |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | 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. |
| 6 | |
| 7 | ## When to Use |
| 8 | |
| 9 | 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. |
| 10 | |
| 11 | Do not use it to send email automatically. |
| 12 | |
| 13 | ## Inputs |
| 14 | |
| 15 | - Company research output |
| 16 | - Prospect score and priority |
| 17 | - Product context |
| 18 | - Tone rules from `TONE.yaml` |
| 19 | - Sender signature |
| 20 | |
| 21 | ## Outputs |
| 22 | |
| 23 | ```json |
| 24 | { |
| 25 | "subject": "", |
| 26 | "body": "", |
| 27 | "draft_status": "draft_ready|blocked_no_evidence", |
| 28 | "cta": "", |
| 29 | "personalization_evidence": [], |
| 30 | "review_notes": [] |
| 31 | } |
| 32 | ``` |
| 33 | |
| 34 | ## Procedure |
| 35 | |
| 36 | 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. |
| 37 | 2. Check `personalization_evidence`. If no fetched evidence is present, return `draft_status: "blocked_no_evidence"` and explain what evidence is missing. |
| 38 | 3. Do not invent company activity, buyer intent, product interest, contact names, or sourcing needs. |
| 39 | 4. Select one concrete personalization point from company research. |
| 40 | 5. Select one matching product value point from product context. |
| 41 | 6. Write a short subject line without spammy wording. |
| 42 | 7. Write 120-160 words unless the user requests a different length. |
| 43 | 8. Structure the body: |
| 44 | - opening line based on prospect evidence |
| 45 | - product relevance |
| 46 | - one proof point such as certification, specification, or manufacturing capability |
| 47 | - light CTA |
| 48 | - signature |
| 49 | 9. Add an opt-out line for regions where cold outreach compliance requires it. |
| 50 | 10. Return review notes for any uncertain claims. |
| 51 | |
| 52 | ## Verification |
| 53 | |
| 54 | - The email includes at least one evidence-backed personalization point. |
| 55 | - `blocked_no_evidence` is used when personalization evidence is missing. |
| 56 | - The email does not claim the prospect buys the product unless evidence says so. |
| 57 | - The email does not include unapproved prices. |
| 58 | - The CTA is light and specific. |
| 59 | - The output is a draft requiring human review. |
| 60 | |
| 61 | ## Common Mistakes |
| 62 | |
| 63 | | Mistake | Fix | |
| 64 | | --- | --- | |
| 65 | | Writing "I saw you are looking for..." without proof | Say "I noticed you carry..." only when visible | |
| 66 | | Overloading first email with specifications | Mention one relevant proof point | |
| 67 | | Using aggressive sales language | Keep it professional and low-friction | |
| 68 | | Sending to D-level prospects | Recommend not contacting them | |