slack-message-check
Skill114 starsChanged 10 months agoMITView on GitHub
Check Slack for important messages and activity. Use during daily planning or when user asks about Slack updates.
In this repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assumption-mappingSkill
- assumption-prioritizationSkill
- atlassian-jira-syncSkill
- backend-designSkill
- brainstormingSkill
- challenging-stakeholder-questionsSkill
- competitor-analysisSkill
- crux-diagnosisSkill
- davciSkill
- decision-journalSkill
- decision-reversibilitySkill
- difficult-conversationsSkill
- executive-update-reviewSkill
- experiment-designSkill
- frontend-designSkill
- google-calendar-schedule-checkSkill
- granola-meeting-syncSkill
- hidden-agendasSkill
- hypothesis-designSkill
- ideas-summarySkill
- influence-strategiesSkill
- interview-cleanupSkill
- jtbd-clusteringSkill
- jtbd-extractionSkill
- limit-based-strategySkill
- linear-issue-syncSkill
- llm-coding-guardrailsSkill
- mece-analysisSkill
- meeting-power-dynamicsSkill
- message-framing-commsSkill
- opportunity-solution-treeSkill
- ost-intakeSkill
- ost-target-selectionSkill
- power-mapSkill
- prd-writingSkill
- problem-structuringSkill
- root-cause-analysisSkill
- signal-identificationSkill
- spec-writingSkill
- stakeholder-risk-reviewSkill
- structured-product-strategySkill
- systematic-debuggingSkill
- tddSkill
- value-chain-mappingSkill
- verificationSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Check Slack channels for important messages and summarize activity.
- Very specific: line 14
Call slack_list_channels to see available channels.
- Very specific: line 19
Call slack_get_channel_history with limit of 20 messages
- Distinctive: line 50
After Slack check, continue with normal planning workflow.
- Distinctive: line 71
Use this skill when the task directly matches the workflow described above.
- Distinctive: line 75
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Slack Message Check
Check Slack channels for important messages and summarize activity.
Instructions
Step 1: List Relevant Channels
Call slack_list_channels to see available channels.
Step 2: Check Priority Channels
For each important channel (determined by user preferences or channel activity):
- Call
slack_get_channel_historywith limit of 20 messages - Filter for messages since last check
Step 3: Summarize Activity
Present findings to user:
Slack activity since yesterday:
**#general** (3 new messages)
- @alice mentioned the deployment schedule
**#engineering** (12 new messages)
- Discussion about API changes
- @bob asked for review on PR #234
**DMs** (2 unread)
- @carol: Question about meeting timeStep 4: Offer Actions
| Option | Description |
| Create task | Turn a message into a task |
| Reply | Draft a response |
| Mark read | Continue without action |
Step 5: Continue Daily Flow
After Slack check, continue with normal planning workflow.
Example Flow
User: "What should I work on today?"
Agent:
- Checks Slack for new activity
- "You have 5 new messages across 2 channels..."
- Summarizes key items
- Offers to create tasks from actionable messages
- Continues with task planning
Notes
- Focus on actionable messages, not all activity
- Prioritize DMs and mentions over general channel noise
- Respect user's channel preferences if configured
When to Use
Use this skill when the task directly matches the workflow described above.
When Not to Use
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
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.

