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. However, it lacks 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 Slack automation skill with clear workflow sequences, good labeling of required vs optional steps, and valuable pitfall documentation. Its main weaknesses are the lack of concrete executable examples (actual MCP call payloads) and some redundancy between per-workflow pitfalls and the consolidated Known Pitfalls section. The content would benefit from being split across files given its length.

Suggestions

Add at least one concrete MCP call example per core workflow showing exact input parameters and expected response structure (e.g., a RUBE_SEARCH_TOOLS call followed by SLACK_SEND_MESSAGE with actual JSON payloads).

Deduplicate pitfalls—either keep them inline per workflow OR in the consolidated section, not both, to reduce token usage.

Consider extracting the detailed workflow sections (3-6) and the Known Pitfalls into a separate WORKFLOWS.md or REFERENCE.md file, keeping SKILL.md as a concise overview with the quick reference table and setup instructions.

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 parameter descriptions could be tightened. However, it largely avoids explaining 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 valuable. However, there are no executable code examples or concrete MCP call examples showing exact input/output JSON. The guidance is specific but not copy-paste ready—it describes what to call rather than showing exact invocations.	2 / 3
Workflow Clarity	Each workflow has a clearly numbered tool sequence with labeled steps (Prerequisite, Required, Optional, Fallback), explicit ordering, and detailed pitfalls that serve as validation checkpoints. The setup section includes a verification step before proceeding. The ID resolution pattern and pagination pattern provide clear feedback loops.	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 no bundle files to offload detailed workflow descriptions or pitfall catalogs. The pitfalls sections in particular could be split into a separate reference file. The single external link to Composio docs is appropriate but the skill itself is monolithic.	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: d065ead

Reviewed: 2 days 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.