agentleFS
ArgentAIOSArgentAIOS/agent-skills/slack-signal-monitor/SKILL.md

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.

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
  1. Very specific:

    Use slack_signal_monitor to detect high-signal Slack activity and proactively alert Jason.

    line 12
  2. Very specific:

    Run slack_signal_monitor with action: "status".

    line 16
  3. Very specific:

    If setupRequired: true, configure Slack token/scopes and monitor scope.

    line 17
  4. Distinctive:

    Run an immediate scan:

    line 41
  5. Very specific:

    Add users:read scope for reliable user display-name resolution.

    line 92

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Slack Signal Monitor

Use slack_signal_monitor to detect high-signal Slack activity and proactively alert Jason.

First run

  1. Run slack_signal_monitor with action: "status".
  2. If setupRequired: true, configure Slack token/scopes and monitor scope.
  3. Set monitor config with action: "set_config".
  4. Enable cron with action: "ensure_cron_monitor".

Recommended first-run commands

  1. Configure all-channel monitoring:
{
  "action": "set_config",
  "monitorAllChannels": true,
  "mentionNames": ["jason"],
  "intervalSeconds": 300,
  "lookbackMinutes": 10
}
  1. Confirm setup:
{ "action": "status" }
  1. Run an immediate scan:
{ "action": "scan_now" }
  1. Turn on cron monitor:
{ "action": "ensure_cron_monitor" }

Core actions

  • status
  • set_config
  • scan_now
  • ensure_cron_monitor
  • disable_cron_monitor
  • clear_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: true scans all active Slack channels visible to the configured token.
  • To monitor specific channels only, set monitorAllChannels: false and provide watchedChannels.
  • watchedChannels also accepts "all" or "*" as shorthand for all-channel mode.
  • Add users:read scope for reliable user display-name resolution.
  • Known fallback sender names are used when user lookup fails.
  • Monitor is deduped by channelId:messageTs so repeated scans do not re-alert old messages.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.