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

64%

Does it follow best practices?

Impact

97%

1.42x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/slack-automation/SKILL.md

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable MCP tool catalog with clear sequenced workflows, explicit pitfalls, and concrete parameters. Its weaknesses are material duplication between per-workflow pitfalls and the "Known Pitfalls"/"Common Patterns" sections, and the absence of any progressive disclosure — all API reference detail lives inline in SKILL.md.

Suggestions

Deduplicate: keep the per-workflow Pitfalls inline but reduce "Known Pitfalls" to items not already covered, or vice versa — several entries (channel resolution, rate limits, thread vs channel, persisting channel/ts) appear twice.

Move the Quick Reference table and detailed per-tool parameter/pitfall notes into a references/ file (e.g., references/tool-reference.md), leaving SKILL.md as an overview with workflow sequences.

Add post-operation verification steps (e.g., confirm the sent message's ts/channel was returned, check response ok=true and matches count) to close the feedback loop in each workflow.

Dimension	Reasoning	Score
Conciseness	The body is dense and tool-focused with no explanation of concepts Claude already knows, but the "Known Pitfalls" section repeats per-workflow pitfalls nearly verbatim (channel resolution, rate limits, thread-vs-channel, persisting channel/ts) and "Common Patterns"/"Quick Reference" overlap earlier sections, so it could be tightened considerably.	3 / 5
Actionability	Guidance is highly concrete — exact tool slugs, parameter names, literal error strings ("Invalid request data provided", error=invalid_blocks, max 50 blocks), and response paths (response_metadata.next_cursor) — but no literal example tool-call payloads are shown, leaving minor gaps versus fully copy-paste-ready guidance.	4 / 5
Workflow Clarity	Every workflow has a numbered tool sequence with [Prerequisite]/[Required]/[Optional] markers and a "When to use" clause, setup validates the connection is ACTIVE before proceeding, and error-recovery guidance (Retry-After, pagination) is given. It falls short of 5 because per-operation outcomes are not verified after execution (e.g., confirming a message actually posted).	4 / 5
Progressive Disclosure	There are no bundle files at all; the entire ~185-line body is a single-file tool API reference (per-tool params, pitfalls, and a quick-reference table) that could live in a references/ file. Section headers are clear and navigation is decent, but content that should be separate is inline, matching the anchor for some structure with inline separable content rather than well-split content.	3 / 5
	Total	14 / 20 Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete capabilities with a clear niche anchor (Slack via Rube MCP/Composio). Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness, plus a few missing natural synonyms (DM, emoji, scheduling).

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to send, search, schedule, or react to Slack messages, manage Slack channels or users, or work in Slack threads."

Mention the scheduling workflow and DMs to align description coverage with the body's five core workflows.

Include natural synonyms users say ("DM", "emoji", "post to a channel") to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Send messages, search conversations, manage channels/users, and react to messages" lists several concrete actions across the Slack domain, but scheduling and message editing workflows from the body are omitted, so coverage has minor gaps rather than being comprehensive.	4 / 5
Completeness	The "what" is clear (automating Slack messaging, search, channel/user management, reactions, threads via Rube MCP), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied by the Slack domain, which caps completeness at 3.	3 / 5
Trigger Term Quality	Natural user terms are present ("Slack messaging", "channel management", "reactions", "threads", "search conversations"), giving good keyword coverage, but common variations like "DM", "emoji", "post to a channel", and "schedule" are missing.	4 / 5
Distinctiveness Conflict Risk	The niche is clear and the "via Rube MCP (Composio)" qualifier disambiguates from other Slack tooling, but a generic request to send or search Slack messages could still overlap closely related Slack skills, leaving minor conflict risk.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/slack-automation/SKILL.md
Commit: c9856ea

Reviewed: 6 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.