slack-message
Skill82 starsChanged 42 days agoMITView on GitHub
Draft an internal Slack message grounded in current project context and recent workflow. Use when sharing a status update, result, finding, or request with a teammate or internal stakeholder at your org.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- addisonk/skillstheir own version, first seen Nov 8, 2026
- talgacapri/pm-ostheir own version, first seen May 23, 2026
- nbirkner/digital-braintheir own version, first seen Apr 12, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- addisonk/skills★ 1same name
- nbirkner/digital-brain★ 0same name
- talgacapri/pm-os★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-reviewSkill
- brieflySkill
- commit-batchingSkill
- commit-batchSkill
- create-alertSkill
- disclose-projectSkill
- discloseSkill
- evolve-claude-mdSkill
- figure-reviewSkill
- grillingSkill
- grill-meSkill
- handoffSkill
- lit-reviewSkill
- overbakedSkill
- pathfinderSkill
- pickupSkill
- recover-sessionsSkill
- repo-initSkill
- retroSkill
- reviewer-2Skill
- spot-aiSkill
- tab-setupSkill
- unstaleSkill
- worklogSkill
- write-new-skillSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Check the user's request against this list.
- Distinctive: line 37
Write in the user's voice: direct, no corporate hedging.
- Very specific: line 38
Use Slack-native formatting: *bold*, _italic_, bullet lists with -,
codeblocks for technical snippets. - Distinctive: line 41
Always generate a Title — a short (≤10 word) subject line that captures the message purpose.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are drafting a first-draft Slack message for the user to review and edit before sending. Synthesize live project context with their direction.
Live context
echo "=== Recent commits ===" && git log --oneline -5 2>/dev/null || echo "(not a git repo)"
echo "=== Working state ===" && git status --short 2>/dev/null | head -20 || echo ""
echo "=== Directory ===" && basename "$(pwd)"Interview
Check the user's request against this list. If any anchor is missing, ask all missing questions in one message — never one at a time.
| # | Question |
| 1 | Who is this for? Name/role; DM, team channel, or leadership post? |
| 2 | What's the purpose? (status update / share a finding / request review / ask for action / FYI) |
| 3 | What's the one key thing they need to know? |
| 4 | Tone: casual or professional? Technical or plain language? |
| 5 | Length: one-liner, short paragraph, or structured with sections? |
| 6 | Call to action or deadline? What, if anything, do you need from them — and by when? |
Drafting rules
- Ground the message in the live context above — reference actual recent work, commits, or open changes where relevant (don't invent).
- Write in the user's voice: direct, no corporate hedging.
- Use Slack-native formatting:
*bold*,_italic_, bullet lists with-,```code```blocks for technical snippets. - Scale technical depth to the audience: peer-level can go deep; leadership stays outcome-focused.
- One message, one point. If the user has multiple asks, flag that and suggest splitting.
- Always generate a Title — a short (≤10 word) subject line that captures the message purpose. Always end the title with 🔽.
Output
Present the draft with a title line followed by the message body inside a fenced block:
Title: <title ending with 🔽>
<!-- Slack draft -->Then call the Skill tool with disclose (the /disclose core) on the draft, so the
user can rate Claude's involvement before sending.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.