CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

85

1.42x
Quality

80%

Does it follow best practices?

Impact

97%

1.42x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Content

77%

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-crafted, highly actionable skill that provides clear tool sequences, specific parameters, and valuable pitfall documentation for Slack automation via Rube MCP. Its main weakness is some redundancy between per-workflow pitfalls and the consolidated pitfalls section, and the overall length could benefit from splitting detailed content into supporting files. The workflow clarity is excellent with labeled step types and concrete response path references.

Suggestions

Extract the detailed per-workflow pitfalls and the 'Known Pitfalls' section into a separate PITFALLS.md to reduce the main file length and eliminate redundancy between inline and consolidated pitfall lists.

Remove minor redundancies like explaining what markdown_text supports (headers, bold, italic, code blocks) since Claude already knows Slack markdown formatting.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some redundancy—pitfalls are repeated across sections and in the 'Known Pitfalls' summary, and some explanations (like what markdown_text does) are unnecessary for Claude. The quick reference table duplicates information already covered in workflows. However, most content is genuinely useful operational detail.

2 / 3

Actionability

The skill provides specific tool names, exact parameter names, concrete tool sequences with clear ordering (prerequisite/required/optional/fallback labels), specific response paths (e.g., `response.data.messages.matches`), and precise pitfalls with error messages. This is highly actionable guidance that Claude can directly execute.

3 / 3

Workflow Clarity

Each workflow has a clearly numbered tool sequence with explicit labels (Prerequisite, Required, Optional, Fallback), key parameters, and detailed pitfalls. The setup section includes a verification step before proceeding. The search workflow includes pagination guidance for when `has_more=true`. Workflows are well-sequenced with validation considerations.

3 / 3

Progressive Disclosure

The content is well-structured with clear sections and a useful quick reference table, but it's a long monolithic file (~180 lines of dense content) with no bundle files to offload detailed workflow descriptions or the pitfalls catalog. The per-workflow pitfalls plus the consolidated 'Known Pitfalls' section could be split out. However, for a skill with no bundle, the internal organization is reasonable.

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 strong in specificity and trigger terms, listing concrete Slack operations with natural keywords users would use. It clearly identifies its niche via the Slack + Rube MCP/Composio combination. However, it lacks an explicit 'Use when...' clause, which limits its completeness score and could make it slightly harder for Claude to know exactly when to select this skill.

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 interact with Slack via Composio.'

DimensionReasoningScore

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 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 specific niche. The mention of both the platform (Slack) and the integration mechanism (Rube MCP/Composio) makes it highly distinctive and unlikely to conflict with other skills.

3 / 3

Total

11

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
Reviewed

Table of Contents

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.