agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/email-copy-review/SKILL.md

email-copy-review

Skill13 starsChanged 24 days agoMITView on GitHub

Use this skill when you want an honest review of outreach copy before sending: \"roast my cold email\", \"review this sequence\", \"why is nobody replying\", \"score my email\". Scores the email on relevance, clarity, proof, ask, length and deliverability risk, quotes the exact lines that hurt, explains why from the reader's point of view, and returns a rewritten version. Works for cold emails, LinkedIn messages and whole sequences.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this before a campaign goes out, or when results are poor.

    line 16
  2. Distinctive:

    MUST quote the exact line for every criticism.

    line 75
  3. Distinctive:

    MUST keep the sender's facts, offer and proof in the rewrite.

    line 76
  4. Distinctive:

    NEVER add claims, numbers or customers the sender did not provide.

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this before a campaign goes out, or when results are poor. It produces a scorecard, exact line-level fixes and a rewrite, judged from the reader's side of the inbox.

Inputs

  • The email, message or full sequence.
  • Who it is for and what it should achieve.
  • Results so far, if any.

The play

1. Read it as the recipient

A busy person on a phone, between meetings, who has never heard of you. Note the moment you would stop reading.

2. Score six dimensions

Score each 1-5 using references/review-rubric.md:

DimensionQuestion
RelevanceIs it clearly about my situation?
ClarityDo I understand what they do and why it matters to me in one read?
ProofIs there a specific, believable reason to trust the claim?
AskIs the next step easy and low-commitment?
BrevityIs every sentence earning its place?
DeliverabilityDoes anything look like spam or marketing?

3. Quote and fix

For every issue, quote the exact line, say why it hurts from the reader's side, and give the replacement. Prioritise: fix the top three issues first; polishing a weak angle is wasted effort.

4. Rewrite

Return a rewritten version that keeps the sender's offer and proof. Show the word count before and after.

5. Diagnose results (if provided)

SymptomMost likely cause
High bounceList quality, not copy
Low replies, few opt-outsWeak relevance or targeting
Replies mostly negativeOffer or ask mismatch, or wrong persona
Positive replies but few meetingsSlow or weak reply handling
Spam complaintsVolume, targeting or misleading subject

Output format

Score: <total>/30  |  Verdict: send / fix first / rewrite
Top 3 issues: <quoted line - why - fix>
Other notes: <short>
Rewrite (<words before> → <words after>):
<email>

What good looks like

  • Feedback quotes the email; it never says "make it more personal" without showing how.
  • Honest but useful: "this reads like a brochure" is followed by the line that proves it and a better line.
  • The review separates copy problems from list and deliverability problems.
  • The common mistake is rewriting the whole thing in the reviewer's voice and losing the sender's facts and proof.

Rules

  • MUST quote the exact line for every criticism.
  • MUST keep the sender's facts, offer and proof in the rewrite.
  • NEVER add claims, numbers or customers the sender did not provide.

Example prompts

  • "Roast this cold email. Be brutal but useful."
  • "Review our 4-step sequence; replies dropped to 1%."
  • "Score these three variants and tell me which to send."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.