slack
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
Quality
68%
Does it follow best practices?
Impact
100%
3.84xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/slack/SKILL.mdQuality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description provides a basic understanding of Slack interaction capabilities but lacks specificity in what actions are available. It has a 'Use when' structure which is positive, but the trigger terms could be more comprehensive and the capabilities more explicitly enumerated.
Suggestions
Replace 'control Slack' with specific action verbs like 'Add emoji reactions to messages, pin and unpin messages in channels'
Add more natural trigger terms users would say: 'emoji', 'react', 'pin message', 'unpin message', ':thumbsup:'
Separate the 'what' and 'when' more clearly - first list capabilities, then specify trigger conditions
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Slack) and some actions ('reacting to messages', 'pinning/unpinning items'), but the phrase 'control Slack' is vague and doesn't comprehensively list specific capabilities. | 2 / 3 |
Completeness | Has a 'Use when' clause which is good, but the 'what' portion is weak - it says 'control Slack' without clearly explaining what specific capabilities exist. The when and what are somewhat merged rather than distinctly answered. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Slack', 'messages', 'channels', 'DMs', 'pinning', but missing common variations users might say like 'emoji', 'reaction', 'pin message', 'unpin', or 'slack tool'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentions 'slack tool' and 'OpenClaw' which adds some distinctiveness, but 'control Slack' is broad enough it could overlap with other Slack-related skills (posting messages, reading channels, etc.). | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill that efficiently documents Slack tool actions with concrete JSON examples. The main weakness is the lack of validation guidance for destructive operations (delete, edit) and no error handling patterns. The content appropriately assumes Claude's competence while providing all necessary specifics.
Suggestions
Add a brief validation/confirmation note for destructive actions (deleteMessage, editMessage) such as 'Verify messageId before deletion' or suggest reading the message first
Include example error responses or common failure modes (e.g., invalid channelId, missing permissions) with recovery guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information without explaining what Slack is or how APIs work. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | All actions include complete, copy-paste ready JSON examples with concrete field values. The inputs section clearly specifies required parameters and their formats. | 3 / 3 |
Workflow Clarity | Actions are clearly listed but there's no validation or error handling guidance. For destructive operations like deleteMessage, there are no checkpoints or confirmation steps mentioned. | 2 / 3 |
Progressive Disclosure | For a skill of this scope, the content is well-organized with clear sections (Overview, Inputs, Actions, Ideas). The action groups table provides quick reference, and individual actions are easy to navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- trpc-group/trpc-agent-go
- Commit
8763418
- Reviewed
Table of Contents
Is this your skill?
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.