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 provides a clear 'when to use' clause and identifies a distinct niche (Slack control via OpenClaw), which are strengths. However, the specificity of capabilities could be improved by listing more concrete actions, and the trigger terms could better cover natural user language variations. The use of 'OpenClaw' as internal jargon may not match how users phrase requests.
Suggestions
List more specific concrete actions beyond reacting and pinning, such as 'add emoji reactions', 'pin/unpin messages', 'post messages', etc., to improve specificity.
Add more natural trigger terms users might say, such as 'emoji', 'react', 'pin message', 'bookmark', or 'slack reaction' to improve keyword coverage.
| 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' is somewhat vague. | 2 / 3 |
Completeness | Clearly answers both 'what' (reacting to messages, pinning/unpinning items in Slack channels or DMs) and 'when' (explicitly starts with 'Use when you need to control Slack from OpenClaw via the slack tool'). | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Slack', 'reacting to messages', 'pinning', 'unpinning', 'channels', 'DMs', but misses common user phrasings like 'add emoji', 'add reaction', 'pin message', or 'slack tool'. The term 'OpenClaw' is internal jargon that users may not naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Slack interactions specifically via the 'slack tool' from 'OpenClaw', with distinct actions (reacting, pinning/unpinning). This is 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 a brief error handling/validation note for destructive actions (deleteMessage, unpinMessage) — e.g., 'Verify the message exists with readMessages before deleting' — to improve workflow safety.
Consider adding a note about what the tool returns on success/failure so Claude knows how to verify actions 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 but arguably unnecessary filler; however, it's 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 the values (e.g., message context lines). This is fully executable guidance. | 3 / 3 |
Workflow Clarity | Each action is clearly documented individually, but there are no validation checkpoints or error handling guidance. For destructive operations like deleteMessage, there's no confirmation step or feedback loop mentioned. The skill presents actions as independent calls without sequencing or verification. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and a summary table, but all 11 action examples are inline in a single file. The action examples could be split into a reference file with SKILL.md providing just the overview, inputs, and most common actions. However, given no bundle files exist, the inline approach is reasonable for this scope. | 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
9f4b734
- 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.