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.
84
77%
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
75%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' clause and is well-scoped to a specific tool and platform (Slack via OpenClaw), making it complete and distinctive. However, it could be more specific about the full range of concrete actions supported and include more natural trigger terms users might use. The use of second person ('you need to') is noted but the primary concern is moderate specificity and trigger term coverage.
Suggestions
List more specific concrete actions beyond reacting and pinning, e.g., 'add emoji reactions, pin messages, unpin messages, manage bookmarks' to improve specificity.
Add more natural trigger term variations users might say, such as 'emoji reaction', 'pin a message', 'react to a slack message', 'add a thumbs up', or 'star a 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. The phrase 'control Slack from OpenClaw via the slack tool' is somewhat vague about the full range of actions. | 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...' with explicit trigger conditions about Slack channels or DMs). | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Slack', 'reacting to messages', 'pinning', 'unpinning', 'channels', 'DMs', but misses common variations users might say like 'emoji reaction', 'pin message', 'slack message', 'add reaction', or 'bookmark'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Slack-specific actions (reactions, pinning/unpinning) via a specific tool ('slack tool' from 'OpenClaw'), making it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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, actionable skill that provides concrete JSON payloads for every Slack action. Its main weakness is the lack of validation/error handling guidance, particularly for destructive operations like message deletion. The content is concise and assumes Claude's competence appropriately.
Suggestions
Add validation or confirmation guidance for destructive actions (deleteMessage, unpinMessage) — e.g., 'Before deleting, confirm the messageId by reading the message first.'
Consider adding a brief error handling note (e.g., what happens if channelId is invalid or bot lacks permissions) to improve workflow robustness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what Slack is or how APIs work. Every section serves a clear purpose, and the JSON examples are minimal but complete. | 3 / 3 |
Actionability | Every action has a concrete, copy-paste-ready JSON payload with realistic field values. The inputs section clearly specifies what needs to be collected and where to find the values (e.g., message context lines). | 3 / 3 |
Workflow Clarity | Individual actions are clear, 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 presents actions as isolated calls without sequencing or feedback loops. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and a summary table, but all actions are inline rather than being split into a reference file. For a skill of this length (~100 lines), it's borderline acceptable, but the action reference catalog could be separated to keep the main skill leaner. | 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
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.