skills/email-drafter/SKILL.md
Use this skill when drafting professional or personal emails—cold outreach, follow-ups, internal memos, client communication, or any message that needs to be clear and effective. Trigger phrases: 'write an email to', 'draft a follow-up', 'help me email'. Do NOT use for mass marketing email campaigns (use copywriter skill) or legal/formal notices requiring specific language.
npx skillsauth add nickcrew/claude-cortex email-drafterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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]
development
Product vision, roadmap development, and go-to-market execution with structured prioritization frameworks. Use when evaluating features, planning product direction, or assessing market fit.
development
Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `cortex git commit` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.
development
Use this skill when writing product requirements documents, prioritizing features, creating user stories, defining acceptance criteria, or setting product metrics. Trigger phrases: 'write a PRD for', 'prioritize this feature backlog', 'write user stories for', 'help me define acceptance criteria', 'what metrics should we track for'. Not for writing code, designing UI mockups, or conducting user research interviews.
tools
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.