← ClaudeAtlas

email-criticlisted

Stress-tests a customer email the user has already drafted and returns a straight verdict plus a tightened version, checked against the source transcript, the account plan and their voice principles rather than in a vacuum. Trigger whenever the user pastes or points at a draft email and asks any of: "is this good", "would you send this", "review this email", "critique this", "tighten this", "make this better", "does this sound right", "too long?", "what would you change", or shares a draft with no instruction at all - a bare draft is a request for a read on it. Also trigger when they say an email "feels off" or ask how a customer will take it. Use this for drafts that already exist; use call-recap-follow-up when the input is a recording and no draft has been written yet.
CSPulse/cs-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill CSPulse/cs-skills
# Email Critic The user has a draft. The job is to tell them whether to send it, and if not, why and what to send instead. The bar is not "is this polished". Polished emails fail all the time. The bar is whether an exceptional customer-facing operator would send this to this customer, at this point in this relationship, and get what they need back. --- ## What this needs **Minimum: the draft.** Paste it and the review runs. With nothing else to check against, the review covers the writing but not the facts, and it says so rather than implying otherwise. **Better with** the call transcript, the thread being replied into, account or contact notes, and a voice guide. Each one moves a check from "cannot verify" to "verified", and the accuracy check is the one that catches real damage. Missing context never blocks the review. It changes what the review can honestly claim. --- ## Before you judge it Two things first, and skipping them is what makes email feedback useless. **Know what the email is for.** A recap, a nudge, an escalation, an ask, a piece of bad news, a note designed to be forwarded to someone's legal team. Each has a different shape and a different failure mode. If the purpose is genuinely unclear from the draft, say so - an email whose purpose you cannot name is usually an email the customer will not act on, and that is the most useful thing you can tell the user. **Get the source.** A draft cannot be judged against itself. Where the material exists, read