slack-message
Draft and send Slack messages in Tim's natural voice. Use when the user wants to (1) post an update to a channel, (2) draft a Slack message, (3) share something on Slack, (4) send a DM, (5) reply in a thread. Applies Tim's Slack writing style and prose principles automatically.
Best use case
slack-message is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Draft and send Slack messages in Tim's natural voice. Use when the user wants to (1) post an update to a channel, (2) draft a Slack message, (3) share something on Slack, (4) send a DM, (5) reply in a thread. Applies Tim's Slack writing style and prose principles automatically.
Teams using slack-message should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/slack-message/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How slack-message Compares
| Feature / Agent | slack-message | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Draft and send Slack messages in Tim's natural voice. Use when the user wants to (1) post an update to a channel, (2) draft a Slack message, (3) share something on Slack, (4) send a DM, (5) reply in a thread. Applies Tim's Slack writing style and prose principles automatically.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Slack Message Draft and send Slack messages that sound like Tim wrote them. ## Before writing 1. Read `~/.claude/PROSE.md` for foundational prose principles. 2. Identify the message type: announcement, thread reply, DM, or technical post. 3. If the user says "draft", use `slack_send_message_draft`. If they say "send" or "post", use `slack_send_message`. 4. Use `slack_search_channels` to find channel IDs when only a name is given. ## Voice and tone **Register:** Relaxed professional. Write like talking to a coworker, not writing documentation. **Capitalization:** - Lowercase "i" in threads, DMs, and casual channel messages. - Capitalize normally only in announcement-style posts that lead with an emoji tag. - Sentence case everywhere. Never title case. **Contractions always:** "i'm", "don't", "it's", "can't", "won't". Never "I am" or "do not." **Brevity:** Default to fewer words. If a message can be 5 words, don't make it 15. ## Message types ### Announcements (channel posts) Lead with an **emoji tag** to signal type: - `:pr:` for PRs and code changes - `:wave:` or `:wave::skin-tone-2:` for feature announcements - `:alert-blue:` for heads-ups and notable changes Then one summary line. Then bullets or a short paragraph if needed. Stats go in bullets with raw numbers and commas: ### Thread replies and DMs Terse. Many messages should be 3-10 words: - "i can take a look today" - "will do" - "no idea, but i can find out" - "fixed @person" ### Technical posts Short casual intro, then structured content: - Code blocks with triple backticks - Numbered lists for distinct issues - Still conversational framing: "here's what i found:" not "The following analysis reveals:" ### Asks and requests Tag the person directly: `@person do you have a minute to look at...` Don't soften: "would you mind when you get a chance" is too padded. ### Links Drop inline with minimal context. No ceremony. - Good: `here's a proposal for @person https://...` - Good: `thoughts on making the landing page https://...` - Bad: `Here is the link to the PR I created: https://...` ## What to avoid - "Hey team" / "Hi everyone" openers - "Let me know if you have any questions" closers - "I'm excited to share" / "I'm happy to announce" / "Just wanted to share" - Padding stats: "a total of", "approximately" - Exclamation marks (except in genuinely funny/excited contexts) - Summarizing what a link already shows - "In conclusion" / "Overall" / "To summarize" - Any phrase flagged in `~/.claude/PROSE.md` anti-AI heuristics ## Checklist before sending - [ ] Does it sound like something Tim would actually type? - [ ] Is the "i" lowercase in casual contexts? - [ ] No unnecessary opener or closer? - [ ] Stats are raw numbers, no padding words? - [ ] Links dropped inline, not ceremonially introduced? - [ ] Passes the PROSE.md spoken word test — would Tim say this out loud?
Related Skills
stop-slop
Use this skill when writing or editing prose to eliminate predictable AI writing patterns. Helps make writing more direct, authentic, and human.
sonos-control
Control Sonos speakers on Tim's home network. Use when the user wants to (1) play, pause, or stop music on Sonos speakers, (2) change volume on speakers, (3) skip tracks, (4) check what's playing, (5) see speaker status, (6) group or ungroup speakers, (7) any Sonos or music/audio playback task involving home speakers. Triggers on "sonos", "speakers", "play music", "what's playing", "volume", "turn up", "turn down", "pause music", "stop music".
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
sending-to-codex
Delegate tasks or ask questions to OpenAI's Codex CLI from within Claude Code. Use this skill when the user says "ask codex", "send to codex", "delegate to codex", "have codex do this", "get codex's opinion", "run this in codex", or wants to offload a coding task or question to the Codex agent. Supports both fire-and-forget coding tasks (fix bugs, add features, refactor) and research questions (analyze code, explain behavior, get a second opinion).
reviewing-writing
Review and critique writing using Michael Nielsen's principles on craft. Analyzes text for purpose focus, brevity, danger words, opening strength, originality, reader psychology, truthfulness, and title impact. Use when the user says "review my writing", "nielsen review", "writing review", "review this writing", "critique my writing", or asks for feedback on prose quality.
reviewing-code
Review pull requests, branch changes, or code diffs. Triggers on "review this PR", "review my changes", "code review", "review branch", or GitHub PR URLs. Focuses on bugs, tests, complexity, and performance - not linting.
resend-email
Send emails via Resend.com API. Use when the user wants to (1) send an email, (2) email someone, (3) send a message to an email address, (4) send email with attachments, (5) schedule an email for later. Requires RESEND_API_KEY environment variable.
refresh-dotfiles
Full sync of personal (yadm) and work (yadm-work) dotfiles. Pulls remote changes, commits and pushes local changes, and audits for untracked files that should be tracked. Use when the user says 'refresh yadm', 'sync dotfiles', 'dotfiles sync', or 'update dotfiles'.
omnifocus
Interact with OmniFocus task manager via the command-line interface (@stephendolan/omnifocus-cli). Use when the user wants to: (1) Add tasks or projects to OmniFocus, (2) List, view, or search tasks/projects, (3) Update or complete tasks, (4) Manage inbox items, (5) Work with tags and analyze tag usage, (6) Process or organize their OmniFocus database from the command line.
omnifocus-triage
Interactively process OmniFocus inbox items using AskUserQuestion. Use when the user wants to (1) triage their inbox, (2) process inbox items, (3) organize their OmniFocus inbox, (4) clear out their inbox, (5) do a GTD-style inbox review. Triggers on "triage inbox", "process inbox", "organize inbox", "clear inbox", "inbox zero".
Nightshift
Manage and interact with Nightshift, an AI-powered development automation tool that runs coding tasks during off-hours.
modal
Run code on Modal's cloud infrastructure via `uvx modal run`. Use whenever the user wants to (1) validate handbook tutorial shell commands on a fresh Debian container from scratch (uv, pip, build tooling, etc. with no cached state from Tim's laptop), (2) test GPU-specific Python code (torch, CUDA, cupy, transformers, CUDA wheels) on real hardware, or (3) reproduce a "does this actually work from zero?" check. Trigger on phrases like "run this on modal", "test on a fresh machine", "try this on a GPU", "validate from scratch", "does the tutorial work end-to-end", "test this without my venv state", or any mention of modal.com / cloud GPUs / ephemeral containers for verification. Also trigger when the user is writing a handbook tutorial that involves GPU installs (PyTorch, CUDA wheels) and they want to confirm the commands work.