slack-automation

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.

1.42x

Quality

72%

Does it follow best practices?

Impact

97%

1.42x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/slack-automation/SKILL.md

Quality

Discovery

82%

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 is strong in specificity and trigger terms, listing concrete Slack operations with natural keywords users would use. It also clearly identifies its niche via the Slack + Rube MCP/Composio scope. The main weakness is the absence of an explicit 'Use when...' clause, which caps completeness at 2 per the rubric guidelines.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to send Slack messages, manage Slack channels, search Slack conversations, or automate Slack workflows.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: messaging, channel management, search, reactions, threads, sending messages, searching conversations, managing channels/users, and reacting to messages programmatically.	3 / 3
Completeness	Clearly answers 'what does this do' with specific Slack actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the actions described.	2 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Slack', 'messaging', 'channel management', 'search', 'reactions', 'threads', 'send messages', 'conversations'. These cover common variations of how users would describe Slack-related tasks.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Slack via Rube MCP (Composio), which is a very distinct niche. The mention of the specific platform (Slack) and integration method (Rube MCP/Composio) makes it unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

62%

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, comprehensive Slack automation skill with excellent workflow clarity—each workflow has clear tool sequences, labeled step types, and detailed pitfall documentation. The main weaknesses are moderate verbosity with repeated information across sections, lack of concrete executable examples (no actual MCP call payloads or response snippets), and all content being inline rather than using progressive disclosure to separate reference material from core workflows.

Suggestions

Add at least one concrete example per core workflow showing an actual MCP tool invocation with parameters and a sample response snippet, rather than only listing parameter names.

Deduplicate pitfalls—remove per-workflow pitfall items that are repeated verbatim in the 'Known Pitfalls' section, or consolidate all pitfalls into one section with workflow cross-references.

Extract the Quick Reference table and detailed per-workflow pitfalls into a separate REFERENCE.md file, keeping SKILL.md focused on the setup and core workflow sequences.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some redundancy—pitfalls are repeated across individual workflows and then again in the 'Known Pitfalls' section. Some information (like pagination patterns) is stated multiple times. However, it avoids explaining basic concepts Claude already knows and stays focused on tool-specific details.	2 / 3
Actionability	The skill provides specific tool names, parameter names, and response field paths, which is quite actionable. However, there are no executable code examples or copy-paste ready MCP call examples—everything is described in prose/lists rather than shown with concrete invocation syntax. The tool sequences are clear but lack example payloads or responses.	2 / 3
Workflow Clarity	Each workflow has a clearly numbered tool sequence with labeled steps (Prerequisite, Required, Optional, Fallback), explicit parameter documentation, and detailed pitfalls sections that serve as validation guidance. The setup section includes a clear verification sequence. Error recovery patterns (e.g., fallback from FIND_CHANNELS to LIST_ALL_CHANNELS, pagination with de-duplication) are well-documented.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and a quick reference table, but it's quite long (~200+ lines) with all content inline. The detailed per-workflow pitfalls, common patterns, and known pitfalls sections could be split into separate reference files. The only external reference is the Composio toolkit docs link.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: davepoon/buildwithclaude
Commit: 7cc63f3

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.