agentleFS
Sign inStart free
DanaResearchGroupDanaResearchGroup/agent-skills/slack-notify/SKILL.md

slack-notify

Skill1 starsChanged 3 months agoMITView on GitHub

Send the user a one-way notification over Slack (no reply expected). Use to report progress, completion, or that a long/automated procedure finished or hit an error, when the user may be away from the terminal.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this to ping the user when something happens and you do not need an answer back.

    line 8
  2. Very specific:

    Run hostname so the message says which machine it came from.

    line 29
  3. Distinctive:

    Use ✅ for success, ⚠️ for needs-attention, ❌ for failure.

    line 36
  4. Very specific:

    Do not wait for a reply. If the helper prints ERR …, report it (token missing or bot not in channel).

    line 38

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

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

slack-notify — one-way notification over Slack

Use this to ping the user when something happens and you do not need an answer back. For questions that need a reply, use slack-ask instead.

Posts as the bot via the send helper, not via the connector: the claude.ai connector posts as the user, which Slack never notifies the user about. The bot identity is what actually triggers a notification.

Config

  • Channel: the id in $CC_SLACK_CHANNEL (e.g. C0123456789; find yours in Slack via channel name → About → Copy channel ID). The helper requires it and exits with ERR when unset — wiring in SETUP.md.
  • Send helper: $HOME/.claude/bin/cc-slack-post.py "<message>" — posts as the bot (token from ~/.claude/.slack-bot-token), allowlisted so it runs without a prompt. The command may use $HOME, but the ~/.claude/settings.json allow-rule must use the literal absolute helper path. To DM instead of the channel, set CC_SLACK_CHANNEL to your Slack member id (e.g. U0123456789 — profile → Copy member ID) for the call.

Procedure

  1. Run hostname so the message says which machine it came from.
  2. Send via Bash:
    $HOME/.claude/bin/cc-slack-post.py "<emoji> *<machine>* — \`<task>\`
<one-line status>
<optional detail or link>"
    Use ✅ for success, ⚠️ for needs-attention, ❌ for failure.

Do not wait for a reply. If the helper prints ERR …, report it (token missing or bot not in channel).

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.

Check your setup, free