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.
81
73%
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 ./skills/slack/SKILL.mdQuality
Discovery
67%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 clear 'Use when' trigger clause and names specific actions (reacting, pinning/unpinning), which is good. However, the opening phrase 'control Slack from OpenClaw' is vague and could overlap with other Slack skills. The description would benefit from listing more specific capabilities and including more natural trigger terms users would use.
Suggestions
List all specific actions more comprehensively (e.g., 'add emoji reactions, pin messages, unpin messages') rather than using the vague 'control Slack' umbrella phrase.
Add more natural trigger term variations users might say, such as 'emoji reaction', 'add reaction', 'pin a message', 'bookmark message'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Slack) and some actions (reacting to messages, pinning/unpinning items), but doesn't comprehensively list all capabilities. It mentions 'control Slack' which is vague, though the specific examples help. | 2 / 3 |
Completeness | Explicitly answers both 'what' (control Slack including reacting to messages, pinning/unpinning items) and 'when' (starts with 'Use when you need to control Slack via the slack tool'). The 'Use when' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'Slack', 'reacting to messages', 'pinning', 'unpinning', 'channels', 'DMs', but misses common variations users might say like 'emoji reaction', 'add reaction', 'pin message', 'unpin message', or 'slack tool'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'OpenClaw' and 'slack tool' adds some distinctiveness, but 'control Slack' is broad enough that it could overlap with other Slack-related skills (e.g., sending messages, reading channels). The specific actions of reacting and pinning help narrow it somewhat but the opening phrase is quite general. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
79%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 API reference skill with excellent actionability—every action has a concrete, copy-paste-ready JSON example. The content is concise and respects Claude's intelligence. The main weakness is the lack of validation/error handling guidance, particularly for destructive operations like message deletion, and the content could benefit from slight reorganization for progressive disclosure.
Suggestions
Add a brief error handling or validation note for destructive actions (deleteMessage, unpinMessage), e.g., 'Verify the messageId exists before deleting' or mention expected error responses.
Consider adding a brief note on what a successful response looks like for at least one action, so Claude can verify operations completed correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Slack is or how APIs work. Every section serves a purpose—inputs, action groups table, and concrete JSON examples. The 'Ideas to try' section is minimal and borderline unnecessary but only two lines. | 3 / 3 |
Actionability | Every action has a complete, copy-paste-ready JSON payload with realistic field values. The inputs section clearly specifies what to collect and where to find them (message context lines). This is fully executable guidance. | 3 / 3 |
Workflow Clarity | Each action is clearly documented individually, but there are no validation steps or error handling guidance. For destructive operations like deleteMessage, there's no confirmation or verification step mentioned. The skill is mostly a reference catalog rather than a workflow, but the absence of any feedback loops for destructive actions caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and a summary table, but all actions are inline in a single file. For 12 distinct actions, some could be grouped or referenced separately. However, the total length is manageable and no bundle files exist, so the inline approach is reasonable though not optimal. | 2 / 3 |
Total | 10 / 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.