메뉴
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.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/vamseeachanta/workspace-hub --skill communication-voice명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | communication-voice |
| description | 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. |
| type | guideline |
| version | 1.0.0 |
| category | guidelines |
| last_updated | "2026-07-30T00:00:00.000Z" |
| source | internal |
| tags | ["communication","email","outreach","voice","business-development","writing"] |
| freedom | low |
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.
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.
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.
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.
Never lead with the ask.
Neal,. Honorifics take no period: Dr Nascimento,.
No "Hi", no "Dear", no "Hope this finds you well".President & CEO, AceEngineer / email / phone. Thank you very much, and
Looking forward, are in-voice. Best, and Cheers, are not.S&S | Technical support, Low BHP | Well Analysis. Never a sentence, never a question, never hype.—. Parentheses sparingly.10-15. Money $1.6M. Deltas +30 BOPD.wells/production, admin/financial, idle/P&A.I'm, I'll, you've); full forms in factual ones
(I am currently…). Keep both registers.Banned vocabulary: solution, leverage, synergy, transform, cutting-edge, passionate, excited to, just circling back, quick question.
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.
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.
Save/publish analysis or computation results from ANY ecosystem repo to Hugging Face as a queryable, viewer-renderable dataset. Use when the user wants to "save results to hugging face", "publish dataset to HF", "hugging face data saving", "save analysis results", "hf dataset", "make results queryable", or "render via datasets-server API". Reshapes nested results into flat parquet tables, writes a dataset card with a viewer `configs:` block and provenance, applies license/public-vs-private routing, enforces a domain data-quality gate (faithful-to-source != correct), publishes to `aceengineer/<repo>-<projection>`, and verifies via the datasets-server API.
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
Diagnose and fix a machine whose equivalence-state fingerprint publish is absent, stale, or gate-length slow (the wh#3500 pre-push RUN_ALL deadlock signature). Use when the equality matrix shows PUBLISH-GATED / PUBLISH-STALE / MISSING-EVIDENCE on the publish-health row, or the sentinel reports absent-fingerprint / publish-slow divergences.