slack-messaging
Skill10 starsChanged 3 months agoMITView on GitHub
Use when you need to send messages to a Slack channel or read recent
- Pipes a download into a shell
- Reads credentials
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
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
- Very specific: line 31
No silent download-and-execute (curl … | sh).
“Common” is measured: kept by at least 6 in 10 of the 8 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
Slack Messaging
Purpose
Send and read Slack messages programmatically via the Slack Web API. Two deterministic shell scripts backed by a shared helper library:
send.sh— post a message to a channel viachat.postMessageread.sh— fetch recent messages from a channel viaconversations.historyand emit them as stable JSON
Credentials are read exclusively from the SLACK_BOT_TOKEN environment
variable. The token is never written to a file, never appears in script output
or logs, and is never committed to the repository.
Constraints
- Token only from env var
SLACK_BOT_TOKEN. Never from a file, never echoed. - TLS is never disabled — no
curl -k, no--insecure, noverify=false. - No silent download-and-execute (
curl … | sh). - Errors on network/security operations are always surfaced — no
2>/dev/nullon calls whose result matters, no emptycatch. set -euo pipefailin every script.- Exit-code contract: 0 success; 1 usage/argument error; 2 missing
tool (
curl/jq) or missingSLACK_BOT_TOKEN; 3 API failure (HTTP non-2xx, network error, or Slackok:false).
Setup — co a kam vložit
1. Vytvoř Slack App
- Přejdi na https://api.slack.com/apps a klikni Create New App → From scratch.
- Vyber workspace a pojmenuj appku (např.
messaging-bot). V sekci OAuth & Permissions → Bot Token Scopes přidej scopy:
Scope Použití chat:writeodesílání zpráv ( send.sh)channels:historyčtení zpráv z veřejných kanálů ( read.sh)channels:readpřístup k metadatům veřejných kanálů groups:historyčtení zpráv z privátních kanálů ( read.sh)- Klikni Install to Workspace a potvrď oprávnění.
- Zkopíruj Bot User OAuth Token (začíná
xoxb-…) z OAuth & Permissions.
2. Bezpečné nastavení tokenu
Nastav token jako env var — NIKDY ho necommituj do repa, NIKDY ho nevkládej
do .env souboru sledovaného Gitem:
# shell profil (mimo repo) — ~/.zshrc nebo ~/.bash_profile
export SLACK_BOT_TOKEN=xoxb-...
# CI secret (GitHub Actions):
# Settings → Secrets → New repository secret → Name: SLACK_BOT_TOKEN
# V workflow: env: SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}3. Pozvi bota do kanálu
V každém kanálu, do kterého chceš psát nebo číst, spusť příkaz ve Slacku:
/invite @jmeno-tveho-bota4. Zjisti Channel ID
V Slacku klikni na název kanálu → View channel details → posuň se dolů →
Channel ID (začíná C… nebo G… u privátních). To ID předávej skriptům.
Usage
send.sh — odeslat zprávu
# TEXT jako argument
send.sh C0123456789 "Zpráva z terminálu"
# TEXT ze stdin (přes -)
echo "Zpráva z pipeline" | send.sh C0123456789 -
# Výstup: ts odeslané zprávy na stdout, log na stderr
# 1718870400.123456
# action=sent channel=C0123456789 ts=1718870400.123456Chybové stavy:
send.sh # exit 1: usage (chybějící argumenty)
send.sh C0123 "" # exit 1: prázdný text
unset SLACK_BOT_TOKEN
send.sh C0123 "text" # exit 2: chybějící tokenread.sh — číst zprávy
# Posledních 20 zpráv (výchozí)
read.sh C0123456789
# Posledních 5 zpráv
read.sh C0123456789 5
# Výstup: stabilní JSON pole seřazené od nejstarší zprávy
# [
# { "user": "U0123456789", "text": "ahoj", "ts": "1718870400.123456" },
# { "user": "U0567890123", "text": "díky", "ts": "1718870461.234567" }
# ]Chybové stavy:
read.sh # exit 1: usage (chybějící channel ID)
read.sh C0123 0 # exit 1: neplatný limit (musí být 1..200)
read.sh C0123 abc # exit 1: neplatný limit (musí být celé číslo)
unset SLACK_BOT_TOKEN
read.sh C0123 # exit 2: chybějící tokenStabilní JSON tvar zpráv
[
{ "user": "U0123456789", "text": "zpráva", "ts": "1718870400.123456" },
{ "user": null, "text": "bot msg", "ts": "1718870461.234567" }
]userjenullpro zprávy od botů bezuserpoletextje""když Slack pole chybítsje Slack timestamp (řetězec, unikátní ID zprávy)- Pole je seřazeno od nejstarší po nejnovější (reverse oproti API)
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- anthropics/knowledge-work-plugins★ 34ksame name
- slackapi/slack-skills-plugin★ 163same name
- haojing8312/WorkClaw★ 141same name
- anton-abyzov/vskill★ 48same name
- NiazMorshed2007/jcr★ 19same name
- damacus/agent-skills★ 2same name
- edu6565/claude-skills★ 0same name
- tsbhatia/coding-skills-for-agents★ 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 repository62 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analyze-problemSkill
- api-reviewSkill
- article-writingSkill
- assignment-compliance-checkSkill
- automation-audit-opsSkill
- autonomous-loopsSkill
- benchmark-optimization-loopSkill
- benchmarkSkill
- blueprintSkill
- class-refactoringSkill
- cleanup-local-branchesSkill
- codebase-simplification-auditSkill
- code-review-bugsnagSkill
- code-review-githubSkill
- code-review-jiraSkill
- code-reviewSkill
- composer-updateSkill
- create-issues-from-textSkill
- create-issueSkill
- create-missing-tests-in-prSkill
- create-testSkill
- design-systemSkill
- docker-patternsSkill
- e2e-testingSkill
- frontend-a11ySkill
- frontend-design-directionSkill
- frontend-patternsSkill
- frontend-slidesSkill
- git-workflowSkill
- laravel-authorization-reviewSkill
- laravel-securitySkill
- laravel-telescopeSkill
- latency-critical-systemsSkill
- merge-github-prSkill
- mysql-patternsSkill
- mysql-problem-solverSkill
- penetration-testerSkill
- postgres-patternsSkill
- prepare-issue-contextSkill
- process-code-reviewSkill
- product-capabilitySkill
- production-auditSkill
- pr-staged-merge-planSkill
- pr-summarySkill
- record-project-memorySkill
- redis-patternsSkill
- refactor-entry-point-to-actionSkill
- refresh-claude-mdSkill
- resolve-issueSkill
- rewrite-tests-pestSkill
- security-bounty-hunterSkill
- security-reviewSkill
- security-threat-analysisSkill
- seoSkill
- skill-creatorSkill
- smartest-project-additionSkill
- test-driven-developmentSkill
- tester-cookbookSkill
- test-like-humanSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

