personalize-email
SkillGenerate 1-3 personalized email variants for a single prospect. The composition bar adapts to the use case — cold_outbound demands a signal → pain → positioning chain; follow-ups / recaps / renewals lean on prior context and next-step framing. Supports cold_outbound, discovery_follow_up, demo_recap,
Install
git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git ~/.claude/skills/personalize-emailWhat is personalize-email?
Generate 1-3 personalized email variants for a single prospect. The composition bar adapts to the use case — cold_outbound demands a signal → pain → positioning chain; follow-ups / recaps / renewals lean on prior context and next-step framing. Supports cold_outbound, discovery_follow_up, demo_recap, re_engagement, renewal, expansion, objection_handling. Returns subject lines and mobile-readable bodies with a rationale chain. Use for sales prospecting, lead generation, account-based selling, buyer-intent-driven outreach, B2B prospecting. Triggers on phrases like "write a cold email", "personalize an email", "draft outreach", "follow up on this prospect", "email this prospect", "outbound to X", "send a chaser".
What this can do
Capabilities declared in this component's own frontmatter — not inferred.
Inherit all session tools
Declares no tool restrictions — inherits every session tool
~180 tokens of context used while enabled, before you invoke anything
Documentation
README · ~13 min readPersonalize Email
Generate personalized email variants. Calls get_gtm_context(detailed: true) unconditionally, resolves the prospect, runs a relationship-context pre-flight, pulls signals + CRM context, and composes 1-3 variants tuned to the chosen use case. Iteratively refinable.
The bar — adapts by use case
The composition bar depends on what the email is trying to do. Don't force a cold-outbound frame onto a follow-up.
| Use case | Anchor for the variant | Pain-bridge required? |
|---|---|---|
cold_outbound | Signal → pain → positioning chain (specific, recent, verifiable signal; concrete inferred pain; GTM-context value prop) | Yes — mandatory |
re_engagement | Fresh new signal since the last contact → reconnection frame | Yes (lightweight — the signal IS the reason to reach back) |
discovery_follow_up | Prior conversation reference → next-step framing | No (the prior touchpoint replaces the pain bridge) |
demo_recap | Recap of what was shown / heard → concrete next step | No |
Reviews
Log in to leave a review.
No reviews yet — be the first.
Explore related
Other things in this space — across every part of the ecosystem, not just skills.
Skillssimilar to this one
All skills →hook-development
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse,
32.8K stars
access
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.
32.8K stars
Claude-to-IM-skill
Bridge Claude Code / Codex to IM platforms — chat with AI coding agents from Telegram, Discord, or Feishu/Lark.
2.8K stars
MCP Servers
All mcp servers →slack-mcp-server
The most powerful MCP Slack Server with no permission requirements, Apps support, GovSlack, DMs, Group DMs and smart history fetch logic.
1.8K stars
yuna0x0-hackmd-mcp
Interact with your HackMD notes and teams seamlessly. Manage your notes, view reading history, and…
64 stars
gmail
Read emails, send messages, and manage labels in your Gmail account.
58 stars
Plugins
All plugins →discord
Discord messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /discord:access.
32.9K stars
telegram
Telegram messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.
32.9K stars
imessage
iMessage messaging bridge with built-in access control. Reads chat.db directly, sends via AppleScript. Manage pairing, allowlists, and policy via /imessage:access.
32.9K stars