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.

82

1.42x
Quality

75%

Does it follow best practices?

Impact

97%

1.42x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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.

The body is highly actionable with concrete tooling details and clearly sequenced workflows, but mild redundancy between the Quick Reference / Known Pitfalls sections and the per-workflow sections keeps conciseness from the top level.

Suggestions

Trim redundancy: the Quick Reference table repeats tool slugs and params already documented in each workflow; consider keeping only one as the canonical source.

Add an explicit validate->fix->retry feedback loop for destructive or batch operations (e.g., message editing or bulk channel listing) to push workflow clarity higher.

Consolidate the per-workflow 'Pitfalls' bullets with the 'Known Pitfalls' section to avoid repeating the same caveats (e.g., thread vs. channel history, rate limits) twice.

DimensionReasoningScore

Conciseness

Mostly efficient with compact tool sequences, params, and pitfalls, but the Quick Reference table and Known Pitfalls section duplicate content already present in the per-workflow sections, so it could be tightened.

3 / 5

Actionability

Provides concrete tool slugs, exact parameter names, specific error strings ('Invalid request data provided', 'invalid_blocks'), and precise response paths ('response.data.messages.matches', 'response_metadata.next_cursor'), giving fully executable guidance.

5 / 5

Workflow Clarity

Numbered tool sequences with [Prerequisite]/[Required]/[Optional]/[Fallback] tags and an explicit ACTIVE-connection checkpoint give a clear sequence, but explicit validate->fix->retry feedback loops for batch/destructive operations are absent.

4 / 5

Progressive Disclosure

Single self-contained file with well-organized sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) and clear headers; no nested references, though the file runs longer than the simple-skill threshold.

4 / 5

Total

16

/

20

Passed

Description

75%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.

The description is specific and well-scoped with strong trigger terms and low conflict risk, but it omits an explicit 'Use when...' trigger clause, which caps its completeness.

Suggestions

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

Include natural synonyms users say like 'DM', 'emoji', or 'post a message' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across five capability areas ('messaging, channel management, search, reactions, and threads') with a second sentence elaborating concrete operations, giving comprehensive coverage.

5 / 5

Completeness

A clear 'what' is present but there is no explicit 'Use when...' clause, and the judging guidelines cap completeness at 3 when explicit trigger guidance is missing.

3 / 5

Trigger Term Quality

Good natural-term coverage ('Slack messaging', 'search', 'channels', 'reactions', 'threads') but missing common synonyms a user might say such as 'DM', 'emoji', or 'post a message'.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to Slack automation via Rube MCP (Composio), a distinct niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.