ClawHub

slack-1

v1.0.0

Use when you need to control Slack from Clawdbot via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.

⭐ 0· 450·2 current·2 all-time
by@rumengkai·duplicate of @chaunceyliu/testat1
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
The SKILL.md describes controlling Slack (reacting, messaging, pins, member info) and all instructions map directly to those actions. It does not declare or install extra capabilities. Note: the doc says the tool uses a bot token configured for Clawdbot — the skill itself does not request or declare that token, so it relies on the host agent/platform to provide the Slack CLI and token.
✓
Instruction Scope
Instructions are narrowly scoped to Slack actions (react, send/edit/delete messages, pins, member info, emoji list). The instructions do not tell the agent to read local files, arbitrary env vars, or to transmit data to unrelated external endpoints.
✓
Install Mechanism
No install spec and no code files — lowest-risk, instruction-only skill. It assumes a preinstalled 'slack' tool but does not attempt to download or write code.
ℹ
Credentials
The skill does not request environment variables or credentials in its metadata. However, the SKILL.md explicitly references a Slack bot token (managed by Clawdbot) used by the 'slack' tool; this implicit dependency is proportionate to the purpose but relies on platform-managed credentials rather than declaring them.
✓
Persistence & Privilege
always is false and the skill is user-invocable with normal autonomous invocation allowed. It does not request persistent presence or attempt to modify other skills or system settings.
Assessment
This skill is coherent and appears to do what it claims: control Slack via a preexisting 'slack' tool using the bot token that Clawdbot/platform should manage. Before enabling: confirm your agent environment actually provides the 'slack' CLI and that the Slack bot token has only the permissions you intend (sending/editing/deleting messages and pin management are powerful). If you want tighter control, restrict the bot token's scopes or run the skill in a test workspace first. Because the skill can edit and delete messages, make sure you trust the agent and have audit/logging enabled for Slack activity.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cx330qhs70y847hq232zn2981x20f

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments