Skill Tracer
Skills › Knowledge Work Plugins › inbox-manager › reply_drafting.md

reply_drafting.md

116 lines · small-business/skills/inbox-manager/reference/reply_drafting.md at 2574e29

Open on GitHub
1# Reply drafting
2
3Read [the shared voice profile](../../../shared/voice-profile.md) first. Every draft here goes out under the owner's name, and voice drift between skills is the thing owners notice fastest.
4
5If no profile exists, write plainly in a neutral register and say the profile is missing. Do not guess a personality — a guessed voice produces exactly the generic copy the owner is trying to escape.
6
7---
8

Reply drafting

Read the shared voice profile first. Every draft here goes out under the owner's name, and voice drift between skills is the thing owners notice fastest.

If no profile exists, write plainly in a neutral register and say the profile is missing. Do not guess a personality — a guessed voice produces exactly the generic copy the owner is trying to escape.


Raw lines 1 to 8
9## The rules that apply to every draft
11**Answer the question first.** Owners' customers ask specific things. A reply that opens with pleasantries and gets to the answer in paragraph three is a reply the owner rewrites.
13**Match the length of the incoming email.** A one-line question gets a one-line answer. Padding a short reply to look thorough wastes everyone's time and reads as a template.
15**Never write a number the owner has not already given.** Prices, dates, quantities, lead times. If the thread does not contain it, either leave it for the owner or write direction instead of a figure.
17**Never invent context.** No "great to hear from you again" if there is no prior thread. No "hope the install went well" if nothing says it did.
19**Do not apologize for the delay unless the owner is genuinely late.** Reflexive apology in every reply trains customers to expect slowness.
21---

The rules that apply to every draft

Answer the question first. Owners' customers ask specific things. A reply that opens with pleasantries and gets to the answer in paragraph three is a reply the owner rewrites.

Match the length of the incoming email. A one-line question gets a one-line answer. Padding a short reply to look thorough wastes everyone's time and reads as a template.

Never write a number the owner has not already given. Prices, dates, quantities, lead times. If the thread does not contain it, either leave it for the owner or write direction instead of a figure.

Never invent context. No "great to hear from you again" if there is no prior thread. No "hope the install went well" if nothing says it did.

Do not apologize for the delay unless the owner is genuinely late. Reflexive apology in every reply trains customers to expect slowness.


Raw lines 9 to 22
23## Patterns by email type

Patterns by email type

Raw lines 23 to 24
25### Routine question
27Answer, then close. No preamble.
29```
30Hi Marisol,
31Yes — the filter size for that unit is 20x25x1. Any hardware store carries it.
32Swap it every three months and you'll be fine.
33Thanks, Ray
34```

Routine question

Answer, then close. No preamble.

Hi Marisol,
Yes — the filter size for that unit is 20x25x1. Any hardware store carries it.
Swap it every three months and you'll be fine.
Thanks, Ray
Raw lines 25 to 35
36### Scheduling
38Propose real times from the live calendar. If no calendar is connected, ask for their availability instead of inventing slots — a slot that turns out to be taken costs a second exchange and an apology.
40```
41Hi Dana,
42Thursday morning or Friday after 1 both work on my end. Which is easier?
43Thanks, Ray
44```

Scheduling

Propose real times from the live calendar. If no calendar is connected, ask for their availability instead of inventing slots — a slot that turns out to be taken costs a second exchange and an apology.

Hi Dana,
Thursday morning or Friday after 1 both work on my end. Which is easier?
Thanks, Ray
Raw lines 36 to 45
46### A promise coming due
48Acknowledge the promise by name. Do not pretend it is a fresh conversation.
50```
51Hi Tom,
52Said Wednesday and here it is. Numbers attached.
53Thanks, Ray
54```

A promise coming due

Acknowledge the promise by name. Do not pretend it is a fresh conversation.

Hi Tom,
Said Wednesday and here it is. Numbers attached.
Thanks, Ray
Raw lines 46 to 55
56### An unhappy customer
58Do not draft the fix, and do not draft an offer. Draft the acknowledgement and get it to the owner fast. Compensation and blame are owner decisions.
60```
61Hi Marisol,
62Sorry — that shouldn't still be cycling after we were out. I'm looking at it
63now and I'll call you today.
64Thanks, Ray
65```
67Then flag it in "needs you" so Ray actually calls.

An unhappy customer

Do not draft the fix, and do not draft an offer. Draft the acknowledgement and get it to the owner fast. Compensation and blame are owner decisions.

Hi Marisol,
Sorry — that shouldn't still be cycling after we were out. I'm looking at it
now and I'll call you today.
Thanks, Ray

Then flag it in "needs you" so Ray actually calls.

Raw lines 56 to 68
69### Something you can't answer
71Say so. A holding reply that is honest beats a confident wrong one.
73```
74Hi Ellen,
75Need to check the unit specs before I answer that properly. Back to you
76tomorrow.
77Thanks, Ray
78```

Something you can't answer

Say so. A holding reply that is honest beats a confident wrong one.

Hi Ellen,
Need to check the unit specs before I answer that properly. Back to you
tomorrow.
Thanks, Ray
Raw lines 69 to 79
80### Declining
82Short, honest, and refer on when you can. Small markets remember both the no and the referral.
84```
85Hi Pete,
86Commercial refrigeration isn't something we're certified for. Basin Cooling
87handles it — ask for Teri.
88Thanks, Ray
89```
91---

Declining

Short, honest, and refer on when you can. Small markets remember both the no and the referral.

Hi Pete,
Commercial refrigeration isn't something we're certified for. Basin Cooling
handles it — ask for Teri.
Thanks, Ray

Raw lines 80 to 92
93## Lines to never write
95These are tells that someone other than the owner wrote the message:
97- "I hope this email finds you well"
98- "Just circling back" / "Just following up" / "Touching base"
99- "Per my last email"
100- "I wanted to reach out"
101- "Please don't hesitate to reach out"
102- "At your earliest convenience"
103- "As per our discussion"
105If the owner's profile lists their own never-dos, those take priority over this list.
107---

Lines to never write

These are tells that someone other than the owner wrote the message:

  • "I hope this email finds you well"
  • "Just circling back" / "Just following up" / "Touching base"
  • "Per my last email"
  • "I wanted to reach out"
  • "Please don't hesitate to reach out"
  • "At your earliest convenience"
  • "As per our discussion"

If the owner's profile lists their own never-dos, those take priority over this list.


Raw lines 93 to 108
109## When the owner edits a draft
111Every edit is data. Ask what the change was about if it is not obvious, and append it to the shared voice profile. The whole point of a shared profile is that a correction made once is never needed twice — and this skill produces more owner edits than any other in the plugin.
113```
114Updated: 2026-08-02 — cut "Sorry for the slow reply" from routine answers.
115 Ray: "I wasn't slow, don't say I was."
116```

When the owner edits a draft

Every edit is data. Ask what the change was about if it is not obvious, and append it to the shared voice profile. The whole point of a shared profile is that a correction made once is never needed twice — and this skill produces more owner edits than any other in the plugin.

Updated: 2026-08-02 — cut "Sorry for the slow reply" from routine answers.
         Ray: "I wasn't slow, don't say I was."
Raw lines 109 to 116