Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatically.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill slack-automation74
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/skillValidation for skill structure
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.
This description excels at specificity and distinctiveness by clearly listing Slack-specific capabilities and mentioning the integration method (Rube MCP/Composio). However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know exactly when to select this skill, and could benefit from more natural trigger term variations that users commonly say.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to send Slack messages, search Slack history, manage Slack channels, or automate Slack workflows'
Include common user phrasings like 'DM', 'direct message', 'post to Slack', 'Slack notification', or 'message someone on Slack'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Send messages, search conversations, manage channels/users, and react to messages programmatically' along with 'Slack messaging, channel management, search, reactions, and threads'. | 3 / 3 |
Completeness | Clearly answers 'what' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the action descriptions. | 2 / 3 |
Trigger Term Quality | Includes good keywords like 'Slack', 'messages', 'channel', 'search', 'reactions', 'threads' but missing common variations users might say like 'DM', 'direct message', 'post to Slack', 'Slack bot', or 'notify channel'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Slack specifically with distinct triggers like 'Slack', 'Rube MCP', 'Composio'. Unlikely to conflict with other messaging or communication skills due to explicit Slack focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
70%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-organized skill with excellent workflow clarity and structure. The main weakness is the lack of executable code examples - while tool names and parameters are specific, there are no actual code snippets showing how to invoke these MCP tools. Some content redundancy between workflow-specific pitfalls and the consolidated 'Known Pitfalls' section could be eliminated.
Suggestions
Add at least one executable code example showing how to call an MCP tool (e.g., the RUBE_SEARCH_TOOLS or SLACK_SEND_MESSAGE invocation pattern)
Consolidate pitfalls - either keep them only in workflow sections or only in the Known Pitfalls section to reduce redundancy
Show a concrete example of the response structure for key operations like SEND_MESSAGE to clarify where to find channel/ts values for subsequent operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the 'Known Pitfalls' section repeats information already covered in workflow-specific pitfalls, and some explanations could be tighter. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Provides specific tool names, parameters, and sequences, but lacks executable code examples. The guidance is concrete (tool slugs, parameter names) but not copy-paste ready - no actual API call examples or code snippets showing how to invoke these tools. | 2 / 3 |
Workflow Clarity | Excellent workflow sequencing with clear numbered steps, explicit prerequisites/required/optional annotations, and detailed pitfalls for each workflow. Includes validation steps (verify connection is ACTIVE before proceeding) and error handling guidance (pagination, rate limits, fallbacks). | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections: Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference table. External reference to toolkit docs is one level deep. Content is appropriately organized for scanning and discovery. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.