Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 3.84xAgent success when using this skill
Validation for skill structure
Read messages, react, and pin workflow
readMessages action name
0%
100%
limit parameter present
100%
100%
react action name
0%
100%
Emoji as Unicode or :name:
0%
100%
Checkmark emoji for completion
50%
100%
pinMessage action name
0%
100%
messageId as timestamp
100%
100%
channelId in all actions
100%
100%
Slack tool structure used
0%
100%
Without context: $0.1853 · 45s · 11 turns · 13 in / 2,902 out tokens
With context: $0.5134 · 1m 53s · 27 turns · 276 in / 6,439 out tokens
Send, edit, and delete messages with correct parameter formats
sendMessage action name
0%
100%
`to` uses channel: prefix
0%
100%
`to` uses user: prefix for DMs
0%
100%
editMessage action name
0%
100%
deleteMessage action name
100%
100%
editMessage has channelId, messageId, content
0%
100%
deleteMessage has channelId and messageId
0%
100%
messageId as timestamp format
72%
100%
Slack tool structure used
100%
100%
Without context: $0.3498 · 1m 16s · 21 turns · 26 in / 4,818 out tokens
With context: $0.3597 · 1m 10s · 21 turns · 26 in / 4,047 out tokens
Member info, emoji list, and list reactions
memberInfo action name
0%
100%
userId parameter name
0%
100%
emojiList action name
0%
100%
emojiList has no extra parameters
50%
100%
reactions action name
0%
100%
reactions has channelId and messageId
0%
100%
messageId sourced from context
20%
100%
channelId sourced from context
100%
100%
Slack tool structure used
0%
100%
Without context: $0.2514 · 1m 3s · 17 turns · 62 in / 3,940 out tokens
With context: $0.3879 · 1m 23s · 22 turns · 183 in / 4,820 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.