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 ./openclaw/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' clause which provides good completeness, and it names specific actions like reacting and pinning/unpinning. However, the opening phrase 'control Slack from OpenClaw' is vague, and the description could benefit from listing more concrete actions and natural trigger terms to improve specificity and reduce potential overlap with other Slack skills.
Suggestions
List more specific concrete actions beyond reacting and pinning (e.g., 'add emoji reactions', 'pin messages to channels', 'unpin items') to improve specificity.
Add more natural trigger term variations users might say, such as 'emoji', 'react', 'pin message', 'unpin message', 'bookmark' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Slack control via OpenClaw) and some actions (reacting to messages, pinning/unpinning items), but the phrase 'control Slack' is vague and the list of concrete actions is limited. | 2 / 3 |
Completeness | Explicitly answers both 'what' (control Slack via the slack tool, including reacting and pinning/unpinning) and 'when' (starts with 'Use when you need to...' with explicit trigger conditions). | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'Slack', 'reacting to messages', 'pinning', 'unpinning', 'channels', 'DMs', but misses common variations 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, managing channels). The specific actions of reacting and pinning help narrow it somewhat. | 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, 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 inline listing of all actions is acceptable given the skill's scope but could benefit from progressive disclosure for the full reference.
Suggestions
Add validation/confirmation guidance for destructive actions (deleteMessage, unpinMessage) - e.g., 'Before deleting, confirm the messageId by reading the message first'
Consider moving the full action JSON examples to a separate REFERENCE.md and keeping only the most common 2-3 actions inline with a link to the full list
| 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 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 in isolation without sequencing or feedback loops. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a summary table, but all 11 action examples are inline rather than being split into a reference file. The action groups table provides a nice overview, but the body could benefit from separating the full action reference into a linked file. | 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
af8bd5f
- 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.