CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

slack-automation

Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-automation-builder/skills/slack-automation/SKILL.md

The canonical home for this skill is slack-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

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 delivers dense, concrete, well-organized operational guidance — tool sequences with roles, exact parameters, error signatures, and pagination/validation pitfalls — that assumes Claude's competence and wastes few tokens. Its main weaknesses are moderate duplication between the workflow pitfalls and the 'Known Pitfalls' section, a circular filler 'When to Use' section, and the absence of example call payloads.

Suggestions

Consolidate the 'Known Pitfalls' section with the per-workflow 'Pitfalls' entries (thread-vs-channel, 429 rate limits, edit persistence each appear twice) to remove duplication.

Delete or replace the circular 'When to Use' section ("applicable to execute the workflow or actions described in the overview") with concrete applicability conditions.

Add one example tool invocation and response payload (e.g., a SLACK_SEND_MESSAGE call and its response.data fields) to make the guidance copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational detail (exact tool sequences, params, error strings, response paths) and explains nothing Claude already knows. Minor trimming targets exist: the "Known Pitfalls" section repeats several workflow-level pitfalls (thread-vs-channel, 429 rate limits, edit persistence), the closing "When to Use" section is circular filler, and the intro line duplicates the description — minor instances rather than the broader padding of the level-3 anchor.

4 / 5

Actionability

Concrete guidance throughout: named tool slugs, sequenced steps with roles ([Prerequisite], [Required], [Fallback]), exact parameter names, formats ('1234567890.123456', 'wave::skin-tone-3'), error strings, and response paths (response.data.messages.matches). It falls short of fully executable because no example invocation or response payload is shown, and the link between RUBE_SEARCH_TOOLS discovery and the SLACK_* tool calls is not demonstrated — minor gaps rather than missing key details.

4 / 5

Workflow Clarity

Each of the five workflows has a clearly sequenced tool list with explicit roles and a 'When to use' condition, and the Setup section embeds real verification (confirm RUBE_SEARCH_TOOLS responds, confirm connection is ACTIVE before proceeding) with fallback paths (LIST_ALL_CHANNELS if FIND_CHANNELS fails). It is not 5 because validation knowledge largely lives in separate 'Pitfalls' sections rather than inline checkpoints within the sequences (e.g., no explicit 'verify response.ok and persist channel/ts' step after SEND_MESSAGE).

4 / 5

Progressive Disclosure

The single file is well structured — Prerequisites, Setup, five workflow sections, Common Patterns, Known Pitfalls, and a Quick Reference table make navigation easy, and there are no nested or buried references. It is not 5 because nothing is split out: with this much per-tool API detail, an overview-plus-references split (e.g., per-workflow detail files) would better match the ideal structure; it is not 3 because the existing organization is genuinely clear, not merely adequate.

4 / 5

Total

16

/

20

Passed

Description

70%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 states concretely what the skill does and sits in a well-delineated niche, but it omits any 'Use when...' trigger guidance, which caps completeness and leaves a few natural trigger terms (DM, emoji, schedule) uncovered. Adding an explicit trigger clause would resolve its main weakness.

Suggestions

Append an explicit trigger clause, e.g., "Use when the user wants to send, search, schedule, or react to Slack messages, or manage Slack channels, users, and DMs."

Include scheduling and user/DM management in the capability list so the description matches the workflows actually documented in the body.

Add natural synonyms users would say — "DM", "post a message", "emoji reaction", "thread reply" — to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

"messaging, search, channel management, and reaction workflows" lists several specific action areas in a concrete domain. Coverage has minor gaps — the body also covers message scheduling, DMs, and user listing, none of which appear in the description — so it matches 'lists several specific actions; minor gaps in coverage' rather than the comprehensive anchor.

4 / 5

Completeness

The 'what' is clear (automating Slack messaging, search, channel management, and reactions via Composio), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the rubric guideline. It is not 2 because the 'what' half is fully concrete, and not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"Slack", "messaging", "search", "channel management" are terms users would naturally say when needing this skill. Common variations like "DM", "post a message", "emoji reaction", or "schedule a message" are missing, fitting 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

"Automate Slack workspace operations ... through Composio's Slack toolkit" occupies a clear niche with a distinct trigger term (Slack) and a named integration path (Composio), so it is unlikely to fire for unrelated skills. It is not 4 because no closely overlapping domain is identifiable — any triggering request would necessarily involve Slack.

5 / 5

Total

16

/

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.

Validation — 15 / 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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/antigravity-bundle-automation-builder/skills/slack-automation/SKILL.md

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.