← Cold Email WriterCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Cold Email Writer
Snapshot Sep 30, 2026 · 23:17 UTC · version 0.1.1
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "personalization-integrity",
"description": "Personalize B2B outreach using only grounded recipient and sender facts.",
"included_files": [],
"skill_md_contents": "---\nname: personalization-integrity\ndescription: Personalize B2B outreach using only grounded recipient and sender facts.\n---\n# Evidence-based personalization\n\nApply when drafting or editing an email that refers to a particular person, company, role, event, product, or business need.\n\n## Inputs\n\nUse details the user provides or material explicitly included in the current conversation. Note provenance for each personalizing detail when useful.\n\n## Process\n\n1. Separate verified/provided facts from assumptions and generic industry context.\n2. Connect one relevant fact to the sender's specific offer; avoid superficial flattery or unrelated personal details.\n3. Never infer sensitive traits, private contact details, intent, budget, pain, or authority without evidence.\n4. If a relevant claim is unsupported or time-sensitive, omit it or ask the user to verify it. Do not browse/scrape private profiles or automate collection.\n5. Avoid pretending to have met, followed, read, or researched the recipient unless that is true and supplied.\n\n## Output\n\nReturn the personalized line/email and, when needed, a short “verify before sending” list with the exact uncertain statement.\n\n## Quality and boundaries\n\nPersonalization should be accurate, relevant, respectful, and easy to substantiate. Never fabricate familiarity, social proof, prior contact, customer results, or a business problem. Do not use data that appears obtained through unauthorized scraping.\n"
}SHA-256: 8e4d7e001fd917939b3d4fea49a0ba44f2b7efe704796f2fe953cd0353568246