Update to Cold Email Writer

{
  "description": "Flag jurisdiction- and provider-specific questions for manual B2B email compliance and deliverability review.",
  "included_files": [],
  "name": "email-compliance-deliverability",
  "skill_md_contents": "---\nname: email-compliance-deliverability\ndescription: Flag jurisdiction- and provider-specific questions for manual B2B email compliance and deliverability review.\n---\n# Compliance and sender-guideline review\n\nApply when the user asks whether a cold email is legal/compliant, how to contact a recipient, or how to improve deliverability.\n\n## Inputs\n\nAsk for the sender's and recipient's jurisdictions, recipient type (for example, corporate subscriber versus sole trader/individual where relevant), message purpose/type, whether the recipient objected/opted out, and sending volume/provider only as needed.\n\n## Process\n\n1. Clearly distinguish a drafting checklist from legal advice. If key jurisdiction or recipient status is unknown, say the answer is conditional.\n2. Prefer current official regulator/provider sources. For the U.S., flag FTC CAN-SPAM topics such as accurate sender/subject, ad identification where applicable, postal address, opt-out and honoring requests. For the UK, distinguish PECR subscriber categories and consider UK GDPR where personal data is processed; note that ICO guidance may be under review.\n3. For provider deliverability, state that requirements depend on provider, traffic type, and volume. Google sender rules may require SPF or DKIM for all senders and additional SPF/DKIM/DMARC alignment and one-click unsubscribe for qualifying bulk/marketing traffic; verify current requirements before implementation.\n4. If asked to contact someone who opted out or objected, advise not to send marketing follow-ups. Do not help evade suppression using another identity/address.\n5. Provide a concise checklist and cite the primary source links when available.\n\n## Output\n\nReturn “questions to verify” and practical copy/design checks, not a legal certification. Make the jurisdictional assumptions visible.\n\n## Boundaries\n\nNever guarantee legality, compliance, delivery, or inbox placement. Do not facilitate spam, purchased/scraped lists, suppression evasion, spoofing, header manipulation, or platform-rule circumvention. Laws and sender requirements change; verify official guidance for high-stakes/current decisions.\n"
}