testat1
v1.0.0Use 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· 1.3k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill's name/description and SKILL.md consistently describe Slack actions (react, pin, send/edit/delete messages, list emoji/member info). Requiring no new binaries or credentials is coherent because the instructions say it uses the bot token already configured for Clawdbot.
Instruction Scope
SKILL.md only describes using a 'slack' tool to perform Slack operations and collecting Slack-related inputs (channelId, messageId, emoji, content). It does not instruct reading arbitrary files, accessing unrelated environment variables, or contacting external endpoints other than the Slack actions implied by the slack tool.
Install Mechanism
There is no install spec and no code files (instruction-only), so nothing is written to disk or downloaded. This minimizes installation risk.
Credentials
The SKILL.md states it uses 'the bot token configured for Clawdbot' but the skill does not declare any required env vars or primary credential. This is likely intentional (it expects the host agent already has Slack configured), but you should be aware that the skill will act with whatever Slack bot token/scopes are present for Clawdbot and can perform write actions (send/edit/delete/pin).
Persistence & Privilege
always is false and the skill is user-invocable with normal autonomous invocation allowed. The skill does not request persistent installation or modification of other skills/config; privileges are typical for an integration that operates via the agent's existing Slack token.
Assessment
This skill itself is just instructions for using your agent's existing Slack tool. Before installing, confirm: (1) your Clawdbot Slack bot token is present and you understand its scopes (it can send, edit, delete, pin, and read messages); (2) you are comfortable granting those abilities to the agent (these are powerful write actions in Slack); and (3) the package metadata discrepancy (_meta.json owner/slug differs from the registry metadata) is acceptable or explainable in your environment. If you want tighter control, restrict the bot token's scopes or use a token tied to a limited-purpose bot or workspace.Like a lobster shell, security has layers — review code before you run it.
latestvk97135d1f5hyyefpv52qd3d3z180jfpp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.