slack

Use when you need to control Slack from Bitterbot via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/slack/SKILL.md

Quality

Content

83%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 concise and highly actionable with complete JSON examples for every action, but it lacks validation/verification guidance for its destructive (delete) and batch-capable operations.

Suggestions

Add a verification step before destructive actions, e.g. confirm the messageId/channelId and note that deleteMessage is irreversible.

For readMessages or batch scenarios, add a checkpoint to verify fetched results before acting on them.

Optionally surface a short 'before you delete' note in the deleteMessage example to satisfy the validation-checkpoint requirement.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: a one-sentence overview, a tight inputs list, and compact per-action JSON examples with no padding or explanations of concepts Claude already knows; nearly every token earns its place.	5 / 5
Actionability	Every action ships a copy-paste-ready JSON payload (react, reactions, sendMessage, editMessage, deleteMessage, readMessages, pin/unpin/listPins, memberInfo, emojiList) covering the common cases concretely.	5 / 5
Workflow Clarity	Per-action recipes are unambiguous, but the skill includes destructive operations (deleteMessage) with no validation/verification checkpoint, which the rubric caps at 3 regardless of simplicity.	3 / 5
Progressive Disclosure	Single self-contained file with clean sectioning (Overview, Inputs, Actions, Ideas) and no nested references; well-organized, though no one-level-deep references exist to push it to the top anchor.	4 / 5
	Total	17 / 20 Passed

Description

73%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 clear, distinct, and uses a proper 'Use when' trigger with concrete action terms, but it under-represents the tool's capabilities relative to what the body documents.

Suggestions

Expand the 'what' to mention send/edit/delete messages, reading messages, and member/emoji info so the description matches the body's action set.

Add a synonym-style trigger such as 'react to, pin, or send Slack messages' to broaden natural keyword coverage.

Keep the existing 'Use when' clause intact while folding the additional actions into a single concise phrase.

Dimension	Reasoning	Score
Specificity	Names the Slack-control domain and a few concrete actions ("reacting to messages", "pinning/unpinning items"), but omits several capabilities the body supports (send/edit/delete messages, member info, emoji list), so coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers "when" ("Use when you need to control Slack from Bitterbot via the slack tool") and gives a "what" with concrete actions, but the "what" under-states the tool's full action set, keeping it just below the top anchor.	4 / 5
Trigger Term Quality	Includes natural terms users would say ("Slack", "reacting to messages", "pinning/unpinning", "channels", "DMs") with good coverage; a few natural phrasings are missing but the core triggers are present.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific named tool ("control Slack from Bitterbot via the slack tool"), carving a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: Bitterbot-AI/bitterbot-desktop
Path: skills/slack/SKILL.md
Commit: 017761f

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