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

—

Does it follow best practices?

Impact

97%

1.42x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The body is highly actionable with clearly sequenced, validated workflows and concrete tool/parameter detail. Its weaker spots are redundancy between the workflow sections and the consolidated pitfall/reference sections, and the absence of any progressive-disclosure structure for a fairly large skill.

Suggestions

De-duplicate pitfalls: keep each pitfall in its workflow section or consolidate solely in 'Known Pitfalls', not both, to cut repeated tokens.

Consider moving the per-workflow detailed parameter/pitfall lists into a reference file (e.g. WORKFLOWS.md) and keeping SKILL.md as a concise overview with the Quick Reference table linking out, to add progressive disclosure.

Trim the Quick Reference table to tools/params not already enumerated inline, or drop it in favor of the inline sequences, to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is dense and free of concept-explanation filler, but the 'Known Pitfalls' section and 'Quick Reference' table restate pitfalls and tool params already covered in the per-workflow sections, so it could be tightened; not the fully lean level-3 where every token earns its place.	2 / 3
Actionability	Concrete tool slugs, exact parameter names (markdown_text, thread_ts, query modifiers like in:#channel/before:YYYY-MM-DD), named errors, and response field paths make the guidance copy-paste ready for an MCP-tool skill, matching the level-3 executable-guidance anchor.	3 / 3
Workflow Clarity	Each workflow is a numbered tool sequence with [Prerequisite]/[Required]/[Optional]/[Fallback] tags plus explicit checkpoints ('Confirm connection status shows ACTIVE before running') and error-recovery guidance (honor Retry-After, paginate via next_cursor), meeting the level-3 clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	It is well-organized with a navigation table, but as a >50-line multi-workflow skill it keeps all detail inline in a single file with no reference files to offload it, fitting the level-2 'could be better organized / content that should be separate is inline' anchor rather than the level-3 one-level-deep-reference structure.	2 / 3
	Total	10 / 12 Passed

Description

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 specific, action-oriented, and clearly niche-scoped to Slack automation, with natural trigger terms. Its main weakness is the missing explicit 'Use when…' guidance, which leaves the 'when to use' half implicit.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to send or schedule Slack messages, search conversations, manage channels/users, or add reactions to messages.'

Add a few common natural phrasings users say ('post to a channel', 'reply in a thread', 'react with an emoji') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Send messages, search conversations, manage channels/users, and react to messages' — matching the level-3 anchor of several specific capabilities rather than the level-2 single-domain example.	3 / 3
Completeness	It clearly states what the skill does but lacks any 'Use when…' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	Natural terms a user would say are well covered ('Slack messaging', 'channels', 'search', 'reactions', 'threads', 'send messages'), not technical jargon, so it clears the level-3 bar over the level-2 'some relevant keywords' anchor.	3 / 3
Distinctiveness Conflict Risk	'Automate Slack … via Rube MCP (Composio)' carves a clear niche with distinct triggers unlikely to fire for unrelated skills, matching the level-3 distinct-niche anchor.	3 / 3
	Total	11 / 12 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
Commit: 366e45b

Reviewed: about 22 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.