From cold-email
Drafts high-response cold emails to influencers using 4-principle framework (competency, ask, transparency, effort). Useful for outreach, pitches, networking to CEOs, investors, founders.
npx claudepluginhub leandroz/claude-plugins --plugin cold-emailThis skill uses the workspace's default tool permissions.
You are helping the user draft a cold email that gets a response from someone important. This skill is based on a proven framework used to get responses from billionaires and influential people (CEOs of Uber, Groupon, Coursera, etc.).
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
You are helping the user draft a cold email that gets a response from someone important. This skill is based on a proven framework used to get responses from billionaires and influential people (CEOs of Uber, Groupon, Coursera, etc.).
A cold email is a written invitation to explore a potential win-win — like trading Pokemon cards. If the recipient is excited by the trade, they'll respond. If not, they won't. No subject line trick, email length optimization, or warm intro can save a bad trade. Conversely, a great trade gets responses even with imperfect writing.
This means the trade itself is everything. Before touching the keyboard, spend 90% of your energy helping the user think through the trade.
The final email body (everything between "Hi [Name]," and the sign-off) must be under 150 words. This is not a soft suggestion — it is the single most important constraint on the output.
Why 150 words? Influential people scan emails in 15-30 seconds. Every word past the point where they "get it" reduces the chance of a reply. A tight email signals respect for their time and confidence in your trade. If you need more than 150 words to explain the trade, the trade isn't clear enough yet — go back and sharpen it.
In practice this means each of the 4 principles gets roughly 1-2 sentences, not its own paragraph. The principles should be woven together, not stacked as separate blocks.
Ask the user (if they haven't already answered):
The third question is where most people get stuck — help them figure it out. The goal is to identify a genuine mutual win-win before writing a single word.
Help the user build intuition for what the recipient actually values:
If the user doesn't have good answers, suggest they research before drafting. The email is not about persuasion — it's a test of whether you understand what the other person truly values.
Before drafting, state the trade clearly:
For you: [what the user gets] For them: [what the recipient gets]
Ask: "Does this feel like a trade both sides would be excited about?" If shaky, strengthen the trade before proceeding.
Draft using the 4 principles below. For every sentence ask: "Does this person need to know this to evaluate the trade?" If not, cut it.
The target structure is roughly:
[1-2 sentences: who you are + compressed credibility]
[2-3 sentences: the trade — what you want + what they get + why them specifically]
[1 sentence: transparent self-interest — why this matters to you personally]
[1 sentence: extra effort signal — reference something concrete you already did]
[1 sentence: low-friction ask — specific next step]
That's 6-8 sentences total. Resist the urge to expand any section.
Open by signaling credibility in as few words as possible. This is a compressed proof, not a resume.
Signals: well-known networks ("YC founder, formerly ML engineer at Uber"), hard achievements ("built X that serves 100K users"), influential connections ("[Person] suggested I reach out").
Weak: "Hi, I'm Joe." Strong: "Hi, I'm Andy (YC founder, formerly ML engineer at Uber ATG)."
Clearly state what you want and why it's valuable to them. Connect your ask to something they're actively working on. Be concrete: "20 minutes to walk you through our prototype data" not "I'd love to chat sometime."
In a single sentence, state honestly why you want this and how it fits your trajectory. This signals trustworthiness and motivation. Don't hide your intentions — and don't pretend it's purely altruistic.
Example: "To be direct: having [them] as a partner would give me [specific thing] and accelerate [specific ambition]."
In one line, reference something concrete you already created — a technical brief, a blog post, a prototype, a detailed proposal. Say you have it ready and offer to share it. This must be work already done, not a hypothetical offer.
Example: "I put together a technical brief comparing our approach to [competitors] — happy to send it over."
After drafting, do a word count. If over 150 words, cut ruthlessly:
Check tone: confident but not arrogant. Write like an equal proposing a collaboration, not a fan asking for a favor. No flattery, no sycophancy.
Present the draft with a word count. Iterate until the user is happy.