Communication skills
Communication/email-draft [to] [purpose]Communication
What it is. Drafts a new outbound email in Misha's voice: direct opener, ordered key points, a clear ask, plus subject-line options.
What it does. Before drafting it reads reference/misha-voice.md, context/people.md, and context/business-info.md for voice and relationship context, then applies the always-on Voss layer (.claude/rules/voss.md) for calibrated questions and labeling. It returns the draft inline with 2-3 subject lines and a pre-send flag. It never auto-sends: outbound send is human-gated, and sending goes through scripts/send-email.py only after you approve.
How to use it. Use for a fresh outbound email to a named recipient. To reply to an email you received use /email-respond; for peer CEO correspondence use /ceo-to-ceo; for a branded letter use /corporate-letter.
/email-draft Jane Doe intro to our platform
"draft email to Jane Doe about the pilot timeline"Customize. Voice lives in reference/misha-voice.md; relationship context in context/people.md. The NEVER list (banned openers, passive voice, buried asks) is edited in the SKILL.md body.
/email-respond [notes]Communication
What it is. Drafts a reply to an existing email thread in Misha's voice: reads the incoming message, reads the sender's real intent, and answers concisely.
What it does. You paste the incoming email below the divider. It reads reference/misha-voice.md, context/people.md, and context/pipeline.md, then runs a Voss tactical-empathy read (.claude/rules/voss.md): surface the emotion, label tension before substance, redirect demands with calibrated questions. It returns the draft, a subject line if re-titling, and one pre-send flag. It never sends and never fabricates commitments not in the thread; outbound send stays human-gated.
How to use it. Use to reply to a received email. For a new outbound email use /email-draft; to triage the whole inbox use /email-intel.
/email-respond keep it short, decline politely
"reply to this email from Jane Doe"Customize. Voice in reference/misha-voice.md, relationship context in context/people.md, deal context in context/pipeline.md. Optional notes steer the reply per run.
/email-intel [--hours N] [--inbox-only] [--sent-only]Communication
What it is. Daily inbox intelligence processor. Scans incoming and outgoing 31C Exchange email, groups by conversation thread, and proposes CRM logs, tasks, pipeline updates, knowledge notes, and new contacts.
What it does. Runs five phases: state check, fetch and process via scripts/email-intelligence.py (Exchange EWS via exchangelib), present a priority-tagged (P1/P2/P3) digest plus one flat numbered action list, mandatory approval, then execute only the numbers you approve. Actions carry tier tags; the numbered list persists in sweep-actions-YYYY-MM-DD.json (via scripts/email-sweep.py) so an interrupted run resumes. Local writes land in crm/contacts/; pipeline changes route as a reversible notify card; [send-gated] replies and forwards send through scripts/send-email.py only after their number is approved (a procedural human gate). It never uses Gmail: Exchange only.
How to use it. Use to triage the inbox. For a single ad-hoc reply use /email-respond; for a multi-channel "what's new" sweep use the Morning Comms pattern.
/email-intel --hours 48
"process my inbox"Customize. Priority signals and enrichment thresholds (14-day WARNING, 30-day CRITICAL) live in the SKILL.md; digest and execution formats in references/digest-format.md and references/execution-templates.md. Exchange credentials load from .env. State lives under outputs/operations/email-intelligence/.
/follow-up [who] [context]Communication
What it is. Drafts a single personalized follow-up email after a specific meeting or conversation: under 150 words, one ask, referencing a concrete detail from the exchange.
What it does. Reads reference/misha-voice.md, context/people.md, context/pipeline.md, and context/business-info.md, then builds an opener-thread-value-nextstep-close structure with Voss-style labeling (reference/voss-negotiation.md). It returns the draft and a suggested subject line, and auto-logs the interaction to the contact's crm/contacts/ file (updating last_touch). It never sends: outbound send is human-gated, and it will not fabricate what was discussed.
How to use it. Use for a one-off post-meeting follow-up. For sweeping many overdue contacts use /cold-sweep; for mass event follow-ups the orchestrator runs the post-event pattern.
/follow-up Jane Doe met at the Acme Corp booth, discussed pilot
"send a follow-up to Jane Doe after our call"Customize. Voice in reference/misha-voice.md; the 150-word cap, one-ask rule, and sign-off are set in the SKILL.md body. Relationship and deal context from context/people.md and context/pipeline.md.
/ceo-to-ceo [name] [subject]Communication
What it is. Drafts peer-level CEO-to-CEO correspondence in Misha's voice: executive register, relationship-aware, 150-300 words.
What it does. Reads reference/misha-voice.md, context/people.md, context/business-info.md, context/pipeline.md, and validates facts against datastore/INDEX.md. It writes peer-to-peer (not vendor-to-client), proposes a concrete next step, and applies a Voss layer (accusation audit, normative leverage, calibrated next steps). It returns the draft with two subject-line options and one relationship flag. It never auto-sends and never invents shared history; outbound send stays human-gated.
How to use it. Use when writing to another company's CEO or founder as a peer. For a non-CEO recipient use /email-draft; for a formal branded letter on letterhead use /corporate-letter.
/ceo-to-ceo Jane Doe partnership expansion
"write to the Acme Corp CEO about strategic alignment"Customize. Voice and CEO-to-CEO notes in reference/misha-voice.md; relationship depth in context/people.md. The 150-300 word bound and Voss hooks are set in the SKILL.md.
/corporate-letter [recipient] [subject]Communication
What it is. Produces a branded 31C external letter (PDF + DOCX) from the locked corporate template, with letterhead, signature block, confidentiality footer, and a 31C-LET reference number applied automatically.
What it does. Five phases: load reference/corporate-style-guide.md plus the corporate-docs, terminology, voice, and Voss rules; announce the template selection; draft the body (under 350 words, Voss precision, no round-number pricing); present for approval as a hard stop; then render via scripts/render-doctype.py to HTML, PDF, and DOCX under outputs/documents/{sender-slug}/letter/. Reference IDs increment from outputs/documents/_letter-sequence.txt. It never renders or sends without explicit approval and runs a hidden-character scan before reporting.
How to use it. Use for formal correspondence to customers, partners, regulators, or investors. For peer CEO correspondence use /ceo-to-ceo; for a commercial offer with pricing use /proposal; for an MOU or LOI use /partnership-doc.
/corporate-letter Jane Doe letter of introduction
"write a formal letter to Acme Corp"Customize. Locked template, colors, typography, and signature live in reference/corporate-style-guide.md and the renderer registry (scripts/utils/doctype_renderer.py); the HTML template under datastore/brand/templates/doctypes/letter.html. Template changes require CEO approval.
/telegram [send|read|search] [contact] [message]Communication
What it is. A live Telegram client operating as Misha's personal account over MTProto: send and read messages, check unread, search history, forward, reply, send and download files and media, and list chats and contacts.
What it does. Drives .claude/skills/telegram/scripts/telegram_client.py (Telethon) with 15 commands, run from the workspace root. Sent and downloaded files resolve under the data overlay via get_outputs_dir(), not the engine tree. It always confirms with Misha before sending to other people; sending to Saved Messages (me) is safe without confirmation. It never logs the session file, API hash, or auth tokens.
How to use it. Use to interact with Telegram as a user. For the VIRAID capture channel use /viraid; not for other messaging platforms or for building Telegram bots.
/telegram read "@janedoe" --limit 10
"send a telegram to Jane Doe"Customize. Credentials (TELEGRAM_API_ID, TELEGRAM_API_HASH, TELEGRAM_PHONE) load from .env; the session lives gitignored at .sessions/telegram/telegram.session. Full command reference in references/commands.md.
/tribe-message [topic]Communication
What it is. Drafts a 100-250 word internal message to the 31C Tribe in the captain's voice, any day of the week: heading-setting, Navigation-Principle framing, with maritime register where natural.
What it does. Reads reference/misha-voice.md, outputs/operations/workspace/31c-operational-state-model.md (operational vocabulary and Five Core Principles), and context/current-data.md, then drafts using sea-state and heading framing plus a Voss layer that labels the Tribe's state before the ask. It handles updates, policy, milestones, and Crunch Mode declarations, and returns a draft only.
How to use it. Use for any internal all-hands or Tribe-wide message. For the recurring Monday cadence message use /tribe-monday; for external content use /linkedin-post or /corporate-letter.
/tribe-message quarter close and next heading
"write to the tribe about the pilot milestone"Customize. Voice and Tribe-communications guidance in reference/misha-voice.md; operational vocabulary in the state model. The NEVER list (no "team", no cheerleading, hyphens only) is in the SKILL.md.
/tribe-monday [week_theme]Communication
What it is. Drafts the recurring 150-250 word Monday message to the 31C Tribe: reads the sea state, sets the week's heading, and connects to a Core Principle in the captain's voice.
What it does. Reads reference/misha-voice.md, outputs/operations/workspace/31c-operational-state-model.md, and context/current-data.md, then opens with an honest read of external conditions, states the heading, acknowledges difficulty without drama, and can declare Crunch Mode when flagged. It returns a draft only for review.
How to use it. Use specifically for the weekly Monday cadence. For an off-cadence or one-off Tribe message use /tribe-message.
/tribe-monday focus week on the Acme Corp pilot
"draft the monday tribe message"Customize. Voice in reference/misha-voice.md; the sea-state/heading structure, 150-250 word bound, and NEVER list are set in the SKILL.md.
/translate [language] [text]Communication
What it is. Translates text between Russian and English (or other languages on request), preserving register, tone, and meaning rather than a literal word-for-word rendering.
What it does. Reads reference/misha-voice.md (especially the Russian Language Notes), auto-detects direction and register (personal, business, formal, or tribe), returns the translation, and flags phrases that needed cultural adaptation. It leaves ODUN.ONE, 31C, DPI+, and proper nouns untranslated, and lets warmth come through more fully in Russian.
How to use it. Use to render a passage in the other language in Misha's voice. To draft new content use the relevant content or comms skill instead.
/translate ru
"translate this to English"Customize. Voice and Russian-language guidance live in reference/misha-voice.md. The direction and register variables override auto-detection per run.