# Communication Voice

> Write outbound email and external messages in Vamsee Achanta's voice — a subtle offer to help, never bold or rash claims. Load before drafting ANY email, LinkedIn/Collide reply, proposal note, or outreach sent under his name.

- Skill: `vamseeachanta/communication-voice` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vamseeachanta/communication-voice`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vamseeachanta/communication-voice/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: vamseeachanta (https://skillmd.com/u/vamseeachanta)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vamseeachanta/communication-voice

---


# Communication voice — writing as Vamsee Achanta

**Load this before drafting any message that goes out under Vamsee's name**: cold outreach,
replies to Collide/LinkedIn posts, client notes, academic requests, proposal follow-ups.

Canonical business-side guide (fuller rationale + genre notes):
`aceengineer-strategy/docs/standards/communication-voice.md`.

## The thesis

> **A subtle offer to help — not bold, rash statements.**

Everything below is a mechanism for achieving that. If a draft violates the thesis, it is wrong
even if it follows every rule here.

## The five mechanisms

**1. Offers are availability, never assertion.**
"I **can help** in various areas." / "**How I may be able to help**, one operation at a time.
**Some examples are given below:**" — pre-labelling the list as *examples* strips it of
proposal-status before it is read. Never "I will deliver X".

**2. Never assert the recipient's problem. Convert diagnosis into something to check.**
- ✗ "Your truck plan is the bottleneck."
- ✓ "…to check whether one truck carries you to 150-200 BOPD **or becomes the bottleneck**."

Offer both branches; let the data decide. Generalities ("the first barrels are *usually*
setpoints and spacing") are fine; verdicts on their operation are not.

**3. Hedge the promise. Never hedge the fact.**

| Hedged — outcomes, and anything about them | Unhedged — facts, terms, capability, own limits |
|---|---|
| "can potentially make", "roughly +30 BOPD", "usually", "may be able to", "I think" | "I have worked at Occidental for over 5 years." "I will spend next 1 month creating value on my own time." "I am currently on a 3 week family emergency trip." |

**4. Volunteer the limits of your own analysis before being asked.**
"…and **where I think the numbers can't yet support a conclusion**."
"…my diagnostic classifier is trained entirely on synthetic cards and **has never been scored
against labelled field data**."

**5. Credentials get one clause, then drop it.**
The entire credential is: *"I have worked at Occidental for over 5 years and on real-time
production and drilling analytics."* No title, no achievements, never "expert" or "specialist".
Competence is carried by **knowing what to name** — "fillage on plunger stroke, spacing, SPM,
unit balance"; "rod-on-tubing wear, corrosion, scale, solids". The reader infers it.

## The skeleton

1. **Why I'm writing + a reframe**, usually "not X, but Y" — *"I'm not writing about capital —
   I'm writing about the engineering that can potentially make the capital easier to raise."*
2. **One clause of credential.** Move on.
3. **Their own numbers, repeated back accurately** — proves the source was read.
4. **Own situation and terms, stated flatly** — availability, timeframe, commercial basis.
5. **A numbered list explicitly framed as examples.** ~5 items. Each: short noun-phrase label,
   then 1-2 sentences ending in the *purpose*, not a claim.
6. **The ask at ~70% down, made costless** — small, specific, free, with an explicit exit.
7. **An adjacent capability as a contingent aside** — *"If there need for admin/financial or
   landman work ahead of technical, just let me know."*
8. **Constraints disclosed proactively and immediately offset** — *"I am currently on a 3 week
   family emergency trip… But I can attend meetings virtually and deliver promptly."*

**Never lead with the ask.**

## Mechanics

- **Greeting:** first name, comma, own line — `Neal,`. Honorifics take no period: `Dr Nascimento,`.
  No "Hi", no "Dear", no "Hope this finds you well".
- **Sign-off:** a closing sentence does the work ("Looking forward to hearing from you."), then a
  clean block — name / `President & CEO, AceEngineer` / email / phone. `Thank you very much,` and
  `Looking forward,` are in-voice. **`Best,` and `Cheers,` are not.**
- **Subject:** terse noun phrase, pipe-delimited — `S&S | Technical support`, `Low BHP | Well
  Analysis`. Never a sentence, never a question, never hype.
- **Length:** ~430 words for a substantive cold offer; 40-80 for a short note.
- **Sentences ~11 words avg**; paragraphs 2-4 sentences with blank lines between.
- **Plain text only** — no bold, no headers, no markdown. Emphasis comes from paragraph breaks.
- **Em dash spaced** ` — `. Parentheses sparingly.
- **Digits always**, even small: "5 years", "1 month". Ranges `10-15`. Money `$1.6M`. Deltas `+30 BOPD`.
- **Slash pairing** is a strong fingerprint: `wells/production`, `admin/financial`, `idle/P&A`.
- **Technical terms unglossed** to a domain peer: BOPD, SPM, LOE, P&A, dynamometer cards, water cut.
- **Contractions in persuasive paragraphs** (`I'm`, `I'll`, `you've`); full forms in factual ones
  (`I am currently…`). Keep both registers.
- **Zero** exclamation marks, emoji, all-caps.
- Slightly compressed English is authentic — *"I can help in various areas to help."* Do not
  manufacture errors, but do not polish into agency copy either.

## Do NOT

1. **Assert their problem.** ✗ "Your 152 wellbores are underperforming."
2. **Promise outcomes.** ✗ "This will add 30 BOPD."
3. **Give unsolicited strong recommendations.** Options are examples to review.
4. **Use superlatives or hype** — no "proven", "world-class", "industry-leading", "game-changing".
5. **Manufacture urgency or scarcity.** He states his own constraints; never the reader's clock.
6. **Self-congratulate.** No achievement lists, no "expert", no "over 20 years of".
7. **Hard-close or request a meeting.** ✗ "Can we find 20 minutes Thursday?"
   ✓ "If that read is useful, we scope the rest. If it isn't, you've lost nothing."
8. **Lead with the ask.**
9. **Format as a proposal** — no scope tables, pricing, phases, or deliverable bullets.
10. **Add rapport filler** — no "Hope you're having a great week", no compliments beyond
    "I read your post on Collide."
11. **Hide constraints.** State flatly, offset immediately.
12. **Remove the free exit.** Every offer must leave a costless way to say nothing.
13. **Ask questions to drive action.** The reference email has **0 questions and 38 statements**.
14. **Smooth the voice into agency English.** That reads as impersonation.

Banned vocabulary: *solution, leverage, synergy, transform, cutting-edge, passionate, excited to,
just circling back, quick question*.

## Evidence base and limits

Derived from the 2026-07-29 cold outreach to Neal Turluck (`S&S | Technical support`, 436 words,
38 sentences), corroborated by the 2026-07-28 Nascimento/Maitelli academic request and the
2026-07-17 Vallassery note, plus ~15 sent-message snippets from the prior 60 days.

**Confident** for cold outreach / offer-to-help, where the thesis is repeatedly evidenced.
**Thin — do not over-extrapolate:** delivering bad news, sustained disagreement, internal-team
writing, and long technical reports each rest on a sentence or two. Pull a larger sample before
relying on this for those genres.

## Do NOT apply when

Writing agent-to-user responses inside this repo (that voice is governed by
`config/agents/SHARED_SOUL.md`), commit messages, issue bodies, code comments, or any internal
harness artifact. This skill governs **outbound human communication under Vamsee's name** only.