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
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
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 has a proper 'Use when' structure and identifies the Slack domain, but lacks specificity in describing concrete capabilities. The phrase 'control Slack' is too vague, and the specific actions mentioned (reacting, pinning/unpinning) feel incomplete. The description would benefit from listing all supported operations explicitly.
Suggestions
Replace 'control Slack' with a specific list of supported actions (e.g., 'Add emoji reactions to messages, pin and unpin messages in channels')
Add more natural trigger terms users might say, such as 'add reaction', 'emoji', 'pin message', 'bookmark'
Clarify the scope by listing all operations the skill supports, not just examples
| 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 operations are supported beyond reacting and pinning. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Slack', 'messages', 'channels', 'DMs', 'pinning', but misses common variations users might say like 'emoji', 'reaction', 'pin message', or 'unpin'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentions 'slack tool' and specific Slack operations which helps distinguish it, but 'control Slack' is broad enough that it could conflict with other Slack-related skills that handle different operations. | 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 tool reference skill that excels at conciseness and actionability with complete JSON examples for every action. The main weakness is the lack of validation guidance for destructive operations (delete, edit) and no error handling patterns, which is important for operations that could fail or have unintended consequences.
Suggestions
Add a brief validation/confirmation note for destructive actions like deleteMessage (e.g., 'Verify messageId before deletion—this cannot be undone')
Include a short section on common error responses and how to handle them (e.g., message_not_found, channel_not_found)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information. No unnecessary explanations of what Slack is or how APIs work—it assumes Claude's competence and every section serves a clear purpose. | 3 / 3 |
Actionability | Every action includes a complete, copy-paste ready JSON example with realistic field values. The inputs section clearly specifies what data to collect and where to find it in message context. | 3 / 3 |
Workflow Clarity | Actions are clearly listed but there's no validation or error handling guidance. For destructive operations like deleteMessage, there's no confirmation step or feedback loop mentioned. | 2 / 3 |
Progressive Disclosure | For a tool reference skill of this scope (~80 lines), the structure is appropriate. Clear sections with a table overview of action groups, followed by individual action examples. No need for external file references. | 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 | |
- 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.