Cold Email Personalizer

What this skill does

Takes a generic cold-email template and a recipient's company URL, fetches public context, and rewrites the opener with a specific, evidence-grounded sentence. Output is the personalized email plus a list of evidence sources.

Inputs

• template: the email template with placeholders like {{first_name}}, {{company}}, {{specific_opener}}.
• recipient_first_name, recipient_company, recipient_url (company site or LinkedIn).
• Optional value_prop: a one-line product pitch.

Steps

1. Fetch the URL with a polite User-Agent header and --max-time 10 via curl. Save HTML to /tmp/recipient.html.
2. Extract usable context: <title>, meta description, recent blog or news headlines (<h1>, <h2> near the homepage hero; for LinkedIn public pages, the about section).
3. Search for evidence the company recently shipped/changed something: keywords announce, launch, now available, dates in the last 60 days.
4. Pick one piece of evidence as the opener anchor. Discard generic facts (founding year, employee count) — they aren't differentiating.
5. Compose the specific opener: 1-2 sentences referring to the evidence, then linking it to the value prop. Avoid clichés ("hope this finds you well"). Use the recipient's name only if recipient_first_name is provided.
6. Substitute placeholders in the template.
7. Detect compliance smells: confirm the email contains a physical mailing address line and an unsubscribe path. If absent, append a CAN-SPAM compliance footer.
8. Truncate to under 120 words total.
9. Output the email plus a "Evidence" sidebar listing the URL, the quoted snippet, and the date observed.

Output

A markdown document with two sections: ## Email (paste-ready text) and ## Evidence (URLs + quoted snippets). Stdout prints word count and a verdict on whether the opener is sufficiently specific (not generic).

Verification

Re-read the email and check the opener mentions a fact unique to the company — replace with another piece of evidence if the chosen one is generic ("you're a SaaS company" doesn't count). Grep the email for the recipient's name, company name, and the value-prop keywords to confirm presence. Run a spam-check (e.g., mail-tester.com style heuristics) and ensure no obvious spam triggers ("FREE!!!", excessive exclamation).

Edge cases

• LinkedIn URL behind login wall: fall back to the company's main website if available.
• Site with JS-only rendering: curl gets an empty body; switch to a headless-browser fetch via Playwright.
• Site with no recent updates (static homepage): fall back to a generic but tailored opener referencing the product category, and surface the lack of evidence.
• Recipient's company is on a public deny-list (sanctions, scams): refuse to generate the email and explain.