SkillWrite in your voice
Learn your writing voice
Builds a reusable voice guide from 10 to 20 of your own sent messages, then drafts in it and flags any line that breaks it.
write-in-my-voice/SKILL.mdDownload- name
write-in-my-voice- description
- Use this skill when a seller wants drafts that sound like them. It reads 10 to 20 of their own sent emails or messages, writes a reusable voice guide (length, sentence rhythm, openers, sign-offs, words they never use, how formal they get by audience), then applies it to any draft and flags the lines that break it.
- license
- CC-BY-4.0
Learn your writing voice
This skill builds a short voice guide from messages a seller actually wrote, then uses it to draft and to check drafts. The guide describes how the person writes, measured from their own text, so a buyer reading an AI draft hears the same person they would hear on a call. Run it once per seller and language, then reuse the guide in every writing skill.
Inputs
- 10 to 20 messages the seller wrote themselves. A mix works best: first messages to prospects, follow-ups, replies to clients and at least one polite no. Leave out templates, sequence steps, anything written by marketing or by an AI, and anything confidential.
- Email access (optional). With it, the agent proposes candidates from the Sent folder of the last 90 days. Without it, ask the seller to paste the messages.
- Language. One guide per language; people write differently in English and in Portuguese.
- Audiences: who they write to (prospects, clients, partners), so the guide can note shifts in formality.
- Drafts they rewrote (optional): before and after versions are the best negative examples.
Steps
- Collect. With email access, list 20 candidates with date, recipient's company and subject, and ask the seller to confirm or drop each. Skip forwards, calendar replies, one-word answers and any text sent to several people unchanged. Fewer than 10 samples: build the guide anyway and mark it low confidence.
- Clean. Remove quoted replies, signatures, legal footers and anything someone else wrote. Replace client and person names with [client] and [name].
- Count before you describe. Median words per message, median words per sentence, paragraphs per message, questions per message, contractions, exclamation marks, emoji, and how dates and times are written. Report numbers, not adjectives.
- Find the patterns. The greetings and the first five words of each message, the sign-offs with how often each appears, phrases the seller repeats, and how they ask (a direct question, an offer, a suggested time).
- Build the never list. Check the samples for phrases drafts often use: "I hope this finds you well", "just checking in", "touch base", "circle back", "reach out", "excited to", "per my last email". Every phrase with zero occurrences goes on the list, plus anything the seller adds.
- Write the guide in the format below. Include three reference lines in the seller's own words, with names removed.
- Test once. Draft a reply to a situation from one of the samples, show it beside the original, and ask what sounds off. Update the guide. Stop after two rounds.
- Apply. For every new draft, write it from the guide, then check it: length in range, an opener and a sign-off from the seller's set, nothing from the never list, one ask. List each line that breaks the guide and why.
- Save, with permission. Offer the guide as a file named voice-guide-[name]-[language].md, or as text to paste into the assistant's project instructions.
Output
Voice guide: [Name] · English · 14 sent emails, 2026-08-02 to 2026-11-18
Confidence: medium (12 to prospects, 2 to clients)
Shape
Length: 45 to 90 words, median 62. Two short paragraphs.
Sentences: median 11 words. Rarely over 20.
Questions: one per message, always at the end.
Openers (use one)
"Hi [first name]," then straight to the point (11 of 14)
"[First name], quick one:" (3 of 14, only with people they know)
Sign-offs
"Thanks," (9) · "Best," (4) · first name only (1)
How they ask
A specific question with a day: "Does Thursday at 10 work?"
Never asks for "a few minutes of your time".
Habits
Contractions always (I'm, it's, we've). No exclamation marks. No emoji.
Dates as "Thursday the 12th". Numbers as digits.
Never use
"I hope this finds you well" · "just checking in" · "touch base" ·
"circle back" · "excited to" · "synergy"
With clients vs prospects
Clients: first name only, no greeting line, shorter (median 38 words).
Reference lines (seller's own words)
"Saw the news about the new plant. Who is planning the move?"
"No pressure either way, a no is useful too."
"I'll send the numbers by Friday."
Draft check
Pass: length 58 words, opener, sign-off, one ask.
Fix: line 3 uses "reach out" (never list).Guardrails
- Reads: only the messages the seller pastes or approves from their Sent folder.
- Writes: the voice guide, and only where the seller says. Drafts stay in the chat.
- Asks before: opening the mailbox, using any message as a sample, saving the guide.
- MUST measure from the samples and show the counts behind each rule.
- MUST remove client names, prices and anything confidential from the guide.
- MUST build a separate guide for each language.
- NEVER send a draft or put it in the mailbox without a yes.
- NEVER build a guide from someone's messages without that person's consent, and never use one person's voice for messages another person sends.
- NEVER copy whole sentences from a sample into a message to someone else. The guide describes the voice; it does not recycle text.
Sources
- How can a founder sell without a sales team?, ALTARA Insights: why a message in the sender's own words carries weight.
- How do I run outbound without hiring an SDR?, ALTARA Insights: "write like yourself" in an outbound routine.
Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/toolkit
Use it with
-
Runs in ALTARAPlaybook Run the cadenceFounder-led outbound in 30 minutes a day, with ALTARAThirty minutes a day with ALTARA: a weekly list with dated reasons, contacts and sequences you approve, replies logged in the CRM. 30 minutes a dayRun it →
-
Connection Run the cadenceGmail, Google Calendar and DriveALTARA sends the sequences your team approved from a separate, warmed inbox. Your own AI reads your Gmail, Calendar and Drive to prepare the calls. Sending inbox for sequencesSee how →
-
Connection Run the cadenceOutlook, Teams and SharePointYour team texts ALTARA in Microsoft Teams, and it sends approved sequences from a warmed inbox. Your own AI reads your Outlook, Teams and files. Sending inbox for sequencesSee how →