slack-signal-monitor
Skill4 starsChanged 8 months agoMITView on GitHub
Configure and run Slack signal monitoring (mentions + keyword watchlist) with dedupe, audio alerts, task creation, and cron automation.
In this repository50 other files it gives its agents.
- model-usage/CLAUDE.mdCLAUDE.md
- peekaboo/CLAUDE.mdCLAUDE.md
- apple-notesSkill
- apple-remindersSkill
- autonomous-unblockSkill
- bear-notesSkill
- birdSkill
- blogwatcherSkill
- blucliSkill
- camsnapSkill
- coolifySkill
- easydmarcSkill
- eightctlSkill
- email-deliverySkill
- food-orderSkill
- geminiSkill
- gifgrepSkill
- githubSkill
- gogSkill
- goplacesSkill
- himalayaSkill
- imsgSkill
- local-placesSkill
- mcporterSkill
- model-usageSkill
- namecheapSkill
- nano-pdfSkill
- notebooklm-researchSkill
- notionSkill
- obsidianSkill
- openai-image-genSkill
- openai-whisperSkill
- openhueSkill
- oracleSkill
- ordercliSkill
- peekabooSkill
- pieces-mcpSkill
- railwaySkill
- sagSkill
- send-payloadSkill
- skill-creatorSkill
- songseeSkill
- sonoscliSkill
- spotify-playerSkill
- summarizeSkill
- twilioSkill
- vercelSkill
- video-framesSkill
- vip-emailSkill
- weatherSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use slack_signal_monitor to detect high-signal Slack activity and proactively alert Jason.
- Very specific: line 16
Run slack_signal_monitor with action: "status".
- Very specific: line 17
If setupRequired: true, configure Slack token/scopes and monitor scope.
- Distinctive: line 41
Run an immediate scan:
- Very specific: line 92
Add users:read scope for reliable user display-name resolution.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Signal Monitor
Use slack_signal_monitor to detect high-signal Slack activity and proactively alert Jason.
First run
- Run
slack_signal_monitorwithaction: "status". - If
setupRequired: true, configure Slack token/scopes and monitor scope. - Set monitor config with
action: "set_config". - Enable cron with
action: "ensure_cron_monitor".
Recommended first-run commands
- Configure all-channel monitoring:
{
"action": "set_config",
"monitorAllChannels": true,
"mentionNames": ["jason"],
"intervalSeconds": 300,
"lookbackMinutes": 10
}- Confirm setup:
{ "action": "status" }- Run an immediate scan:
{ "action": "scan_now" }- Turn on cron monitor:
{ "action": "ensure_cron_monitor" }Core actions
statusset_configscan_nowensure_cron_monitordisable_cron_monitorclear_seen
Example setup
{
"action": "set_config",
"monitorAllChannels": true,
"mentionNames": ["jason"],
"keywordWatchlist": [
"DNS",
"DMARC",
"domain transfer",
"website",
"Barrett",
"urgent",
"ASAP",
"blocked"
],
"intervalSeconds": 300,
"lookbackMinutes": 10,
"taskCreationEnabled": true,
"audioAlertEnabled": true,
"mainSessionAudioAlert": true
}Notes
monitorAllChannels: truescans all active Slack channels visible to the configured token.- To monitor specific channels only, set
monitorAllChannels: falseand providewatchedChannels. watchedChannelsalso accepts"all"or"*"as shorthand for all-channel mode.- Add
users:readscope for reliable user display-name resolution. - Known fallback sender names are used when user lookup fails.
- Monitor is deduped by
channelId:messageTsso repeated scans do not re-alert old messages.
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.

