How do I install Cold Email Checker?

Install Cold Email Checker with a single command: npx mdskills install proskillpacks/cold-email-checker. This downloads the skill files into your project and your AI agent picks them up automatically.

What platforms support Cold Email Checker?

Cold Email Checker works with Claude Code, Claude Desktop, Cursor, Vscode Copilot, Windsurf, Continue Dev, Codex, Gemini Cli, Amp, Roo Code, Goose, Opencode, Trae, Qodo, Command Code, Chatgpt. Skills use the open SKILL.md format which is compatible with any AI coding agent that reads markdown instructions.

Cold Email Checker

Name: Cold Email Checker: AI Agent Skill
Brand: proskillpacks
Availability: InStock
Author: proskillpacks

ProductivityIntermediate

Checks a drafted cold email before it is sent. It tests every claim about the prospect against text you supply, flags claims about you that need proof, checks length, subject line and the single ask, checks the legal basics of commercial email (sender identity, postal address, opt-out), and returns a tightened version with unsupported claims removed.

by kaiventura.founder

npx mdskills install proskillpacks/cold-email-checker

Skill Portability Check

Checks Agent Skills (SKILL.md folders) for portability and common mistakes with a standard-library Python script, then explains each finding and the fix. It catches frontmatter that strict YAML parsers reject (such as an unquoted colon in the description, which makes tools like npx skills skip the skill), keys other than name and description, bad name format, a description that does not say when to use the skill, vendor tool names and paths, missing fallbacks when a tool or the network is...

Fact Claim Checker

Reads a draft article, post, newsletter, report or script and lists every claim that needs a source before it is published, sorted by risk, with what kind of source would settle each one. It marks which claims the draft itself already supports, which are plain opinion, and which are risky (numbers, studies, quotes, dates, "first/only/best", cause and effect, claims about people or companies). It does not rule claims true or false from memory.

CSV Profile And Sanity Check

Reads a CSV or spreadsheet export without changing it and reports what is in it, including row and column counts, each column's type, blanks, distinct values, numeric ranges, duplicates, mixed formats, odd outliers and case or spacing variants, then lists what to ask the data's owner before anyone uses it.

Readme First Run Check

Reads a project's README the way a new user would and checks, against the repository itself, every step they are told to take - the prerequisites and versions, the install and setup commands, the files, scripts, environment variables and ports the README mentions, and the run and test commands. It reports each step as OK, BROKEN, MISSING or UNVERIFIED with file evidence, then gives the first-run path a newcomer would actually experience and the README edits that fix it.

SKILL.md

1---
2name: cold-email-checker
3description: Checks a drafted cold email before it is sent. It tests every claim about the prospect against text you supply, flags claims about you that need proof, checks length, subject line and the single ask, checks the legal basics of commercial email (sender identity, postal address, opt-out), and returns a tightened version with unsupported claims removed. Use when someone has a cold or outreach email draft and says "check this email", "is this OK to send", "review my outreach", or pastes a draft with the prospect's website text.
4---
5 
6# Cold email checker
7 
8You review a draft the way a careful colleague would before it goes out. You test claims against evidence. You do not write a new campaign.
9 
10## What you need
111. The **draft** (subject and body).
122. **Evidence about the prospect**: the text of their page or pages the draft refers to. If you have a web tool, you may fetch the page the draft names, with whatever tool you have. If you cannot fetch, ask the user to paste the text. If neither is possible, still run every other check and mark every claim about the prospect "not checked against the site".
133. **What the sender can prove**: any result, client or credential the draft states. Ask once if the draft states one and the user has not said it is true.
144. Optional: the sender's country and the recipient's country, if the user says.
15 
16**Stop condition.** If there is no prospect text after you asked once, mark every claim about the prospect "not checked" and go no further on those claims.
17 
18## Checks
191. **Claims about the prospect.** List each factual statement about them (what they do, a product, a recent post, a number, a place). For each, quote the evidence from the supplied text, or mark it Unsupported (the text says nothing or says otherwise) or Not checked (no evidence supplied). A line like "I noticed you are growing fast" is a claim.
202. **Claims about the sender.** Results, years, clients, awards, comparisons. Mark each Backed (the user said it is true) or Needs proof.
213. **Invented familiarity.** Flag phrases that imply the sender used the product, read the newsletter, met the person or saw an event, unless the user said so.
224. **Subject line.** Under about 6 words, and it must accurately reflect the content. Flag "Re:" or "Fwd:" on a first message, fake urgency, and subjects unrelated to the body.
235. **One ask.** Count the asks. Flag more than one, and asks that cannot be answered in a short reply.
246. **Length and clarity.** Count the words. Flag over 120 words for a first message, jargon, flattery, and filler openers.
257. **Commercial email basics.** The US Federal Trade Commission's CAN-SPAM guide (https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business) lists these for commercial email: accurate From, To and Reply-To information, a subject line that accurately reflects the content, a clear disclosure that the message is an ad, the sender's valid physical postal address, and a clear way to opt out. It says opt-out requests must be honoured within 10 business days and that the law makes no exception for business-to-business email. Check the draft for each of these and say which are present or missing. Do not state that the law applies or does not apply to this sender. Rules in other countries differ, so say that and tell the user to check the rules where the recipient is. You are not giving legal advice.
26 
27## Output
28**Verdict:** one line: Send as is, Send after fixes, or Do not send, with the main reason.
29 
30**Claims table:** claim | evidence or status.
31 
32**Issues:** numbered, most serious first, each quoting the exact words from the draft and saying why it matters and the fix.
33 
34**Tightened version:** the draft with unsupported claims removed or marked `[CONFIRM: ...]`, one ask, plain words. Keep the user's voice. Do not add new facts.
35 
36**Before you send:** what the user must confirm or add (postal address, opt-out line, proof for claims).
37 
38## Rules
39- Never add a fact about the prospect or the sender that is not in the supplied text or the user's words.
40- Do not guess the recipient's name or email address.
41- Do not send anything.
42- Plain, short sentences. No em dashes.
43

Full transparency — inspect the skill content before installing.