Email tone review criteria
Review the worker's email draft against these checks. Issue exactly
one verdict per iteration:
- APPROVE — passes all checks. Ready to send.
- REVISE — 1-2 specific tone or content issues that the worker
can fix.
- REJECT — fundamentally wrong shape (e.g. answers the wrong
question, cites the wrong recipient, addresses a non-issue).
Checks
Tone matches recipient + situation:
- Customer service emails: warm, brief, action-oriented
- B2B emails: clear, professional, no false urgency
- Apology emails: own the issue without grovelling
- Internal Slack-likes: casual, no formal sign-off
- Cold outreach: relevant first sentence, no walls of text
No AI tells:
- Avoid: "I'm reaching out", "I hope this email finds you well",
"delve into", "harness", "unlock", "robust", "synergy",
"leverage" (as a verb), "moving forward", "circle back"
- Avoid em dashes if the user's house style avoids them — check
the User Preferences block in context for tone constraints
- Avoid passive-aggressive phrases ("just following up", "as
mentioned previously", "per my last email")
Specific values used verbatim (CRITICAL):
- Customer name, amounts, order numbers, dates, codes from the
Task must appear as literal text — never
[CUSTOMER_NAME] or
[AMOUNT] placeholder leakage. This is always REVISE.
Action clear:
- The recipient should know what to do (reply, click, wait, etc)
after one read. If unclear, REVISE.
Sign-off matches sender role:
- Personal email: first name only
- Customer support: name + role + company
- Don't use multiple sign-offs in one email
Length appropriate:
- Quick acknowledgement: 1-2 short paragraphs
- Detailed response: ≤4 paragraphs unless explicitly asked for
more
- One-line replies are fine when the situation calls for them
Verdict format
Respond with ONE LINE in this exact shape:
VERDICT: APPROVE — warm tone matches the apology context cleanly
VERDICT: REVISE — replace "I hope this finds you well" with a direct first sentence
VERDICT: REJECT — drafted a refund denial when the task asked for an apology + refund confirmation
The em-dash (—) or hyphen (-) is the parser delimiter — use either.
1---2name: review-email-tone3description: Reviewer criteria for outbound email drafts via with_review. Checks tone-recipient match, professionalism, no AI tells, no placeholder leakage. Use as criteria.skill argument when reviewing email drafts before send.4---56# Email tone review criteria78Review the worker's email draft against these checks. Issue exactly9one verdict per iteration:1011- **APPROVE** — passes all checks. Ready to send.12- **REVISE** — 1-2 specific tone or content issues that the worker13 can fix.14- **REJECT** — fundamentally wrong shape (e.g. answers the wrong15 question, cites the wrong recipient, addresses a non-issue).1617## Checks18191. **Tone matches recipient + situation**:20 - Customer service emails: warm, brief, action-oriented21 - B2B emails: clear, professional, no false urgency22 - Apology emails: own the issue without grovelling23 - Internal Slack-likes: casual, no formal sign-off24 - Cold outreach: relevant first sentence, no walls of text25262. **No AI tells**:27 - Avoid: "I'm reaching out", "I hope this email finds you well",28 "delve into", "harness", "unlock", "robust", "synergy",29 "leverage" (as a verb), "moving forward", "circle back"30 - Avoid em dashes if the user's house style avoids them — check31 the User Preferences block in context for tone constraints32 - Avoid passive-aggressive phrases ("just following up", "as33 mentioned previously", "per my last email")34353. **Specific values used verbatim** (CRITICAL):36 - Customer name, amounts, order numbers, dates, codes from the37 Task must appear as literal text — never `[CUSTOMER_NAME]` or38 `[AMOUNT]` placeholder leakage. This is always REVISE.39404. **Action clear**:41 - The recipient should know what to do (reply, click, wait, etc)42 after one read. If unclear, REVISE.43445. **Sign-off matches sender role**:45 - Personal email: first name only46 - Customer support: name + role + company47 - Don't use multiple sign-offs in one email48496. **Length appropriate**:50 - Quick acknowledgement: 1-2 short paragraphs51 - Detailed response: ≤4 paragraphs unless explicitly asked for52 more53 - One-line replies are fine when the situation calls for them5455## Verdict format5657Respond with ONE LINE in this exact shape:5859```60VERDICT: APPROVE — warm tone matches the apology context cleanly61VERDICT: REVISE — replace "I hope this finds you well" with a direct first sentence62VERDICT: REJECT — drafted a refund denial when the task asked for an apology + refund confirmation63```6465The em-dash (—) or hyphen (-) is the parser delimiter — use either.
jezweb