From nickcrew-claude-ctx-plugin
Drafts clear professional emails for cold outreach, follow-ups, internal memos, client updates, and networking with optimal subject lines, tone, length, and CTAs.
npx claudepluginhub nickcrew/claude-cortexThis skill uses the workspace's default tool permissions.
This skill produces clear, purposeful emails calibrated to the right tone, length, and structure for the situation—whether you're reaching out cold to a potential partner, nudging a slow-to-respond client, or delivering difficult feedback to a colleague. It applies proven subject line formulas, places calls to action where they land hardest, and keeps emails as short as they need to be and no s...
Drafts professional emails using What-Why-How framework for software developers. Use for status updates, requests, escalations to colleagues, stakeholders, or leadership.
Drafts professional emails matching your writing style by analyzing sent emails via WorkIQ for tone, greetings, structure, and sign-offs. For replies, follow-ups, and proposals.
Drafts high-response cold emails to influencers using 4-principle framework (competency, ask, transparency, effort). Useful for outreach, pitches, networking to CEOs, investors, founders.
Share bugs, ideas, or general feedback.
This skill produces clear, purposeful emails calibrated to the right tone, length, and structure for the situation—whether you're reaching out cold to a potential partner, nudging a slow-to-respond client, or delivering difficult feedback to a colleague. It applies proven subject line formulas, places calls to action where they land hardest, and keeps emails as short as they need to be and no shorter. The goal is emails that get opened, read, and acted on.
copywriter skill for campaign copy)| Task | Approach |
|---|---|
| Subject line | Keep under 50 chars; use personalization, numbers, or questions |
| Formal tone | Full sentences, no contractions, "Dear [Name]", sign with full name |
| Casual tone | Contractions ok, first name greeting, conversational sign-off |
| Length | Cold email: 75–125 words; follow-up: 50–75 words; detailed request: up to 200 words |
| CTA | One CTA per email; make it specific and low-friction |
| Reply email | Acknowledge their last point before making your ask |
| Opener | Never start with "I hope this finds you well" |
Clarify the email's single purpose. Every email should do exactly one thing: make an ask, share information, confirm something, or respond to something. If you have two asks, send two emails. Identify: who is the recipient, what is the relationship, and what is the single desired outcome?
Write the subject line. The subject line determines whether the email gets opened.
Choose the right tone.
Structure the email.
Calibrate length.
For reply emails: Start by briefly acknowledging their message—one sentence. Then make your point or ask. Don't restate everything they said.
For difficult or sensitive emails: State the situation factually. Acknowledge impact. Offer a path forward. Avoid over-apologizing (it undermines the message) and avoid defensiveness.
Proofread for these specifics: Correct recipient name (check spelling), accurate subject line, working links if included, no "sent from my phone" auto-signatures if the email is formal.
Input: "Write a cold email to a product manager at Stripe asking for 20 minutes to discuss a UX research tool I'm building. I don't know them personally. Keep it short and genuine."
Output:
Subject: Quick question about Stripe's onboarding UX
Hi [Name],
I came across your talk at Config 2024 on reducing payment friction—the friction-mapping framework you described is exactly the kind of thinking I'm trying to support with a tool I'm building.
I'm developing a lightweight UX research platform that helps PM teams track friction points across user flows without drowning in session recordings. Given your focus on onboarding, I thought you'd either find it interesting or immediately tell me why it's a bad idea—either would be valuable.
Would you have 20 minutes in the next two weeks for a quick call?
Thanks for considering it, [Your Name]
Why it works:
Input: "I sent a proposal to a client last week and haven't heard back. Write a follow-up that's not annoying or pushy."
Output:
Subject: Re: Proposal for Q4 Campaign
Hi Sarah,
Just wanted to resurface this in case it got buried—no worries if the timing isn't right.
I'm happy to adjust the scope, timeline, or budget if anything in the proposal gave you pause. Otherwise, if you're still reviewing, I'll check back in another week.
Thanks, [Your Name]
Why it works:
Input: "Write an email to a junior team member letting them know their last report had unclear structure and needs revision. Be direct but kind."
Output:
Subject: Feedback on the Q3 Market Analysis Report
Hi Jamie,
Thanks for getting the Q3 report in on time—I know the data collection was a heavy lift.
I want to give you some direct feedback before we share it with the wider team: the current structure makes it hard to follow the main argument. Specifically, the executive summary doesn't match the conclusion, and the methodology section appears before context that would help readers understand why it matters.
I'd suggest:
Happy to walk through it together if that's helpful—just let me know. Revised version needed by Thursday EOD.
Thanks, [Your Name]