CtrlK
BlogDocsLog inGet started
Tessl Logo

slack

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

71

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A tight, highly actionable action catalog with excellent copy-paste examples and clear single-action workflows; its only weakness is progressive disclosure, where the inline example catalog could be split into a reference file to keep SKILL.md a leaner overview.

Suggestions

Move the per-action JSON examples into a references file (e.g. references/actions.md) and keep SKILL.md as a concise overview plus the action-group table and inputs, linking out for full payload details.

Add a brief validation/confirmation note for destructive actions (deleteMessage, unpinMessage) so the workflow explicitly addresses irreversible operations.

DimensionReasoningScore

Conciseness

The body is lean: a one-line overview, a compact inputs list, an action-group table, and minimal JSON snippets per action, with no padding or explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

Each action ships a complete, copy-paste-ready JSON example with concrete field values (e.g. {"action":"react","channelId":"C123","messageId":"1712023032.1234","emoji":"✅"}), leaving no ambiguity about how to call the tool.

3 / 3

Workflow Clarity

This is a simple single-tool skill where each action is independent and unambiguous; the simple-skill exception applies, so the lack of a multi-step workflow with validation checkpoints does not lower the score.

3 / 3

Progressive Disclosure

Sections are well-organized with clear headers and easy navigation, but at ~140 lines the body inlines 11 action examples that could reasonably live in a reference file; with no external references and over 50 lines, the simple-skill 'well-organized sections' exception does not apply, so content that could be separate remains inline.

2 / 3

Total

11

/

12

Passed

Description

80%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-triggered description with clear 'when' guidance and a distinct niche, but it undersells the skill's full action set and uses second-person voice ("you need") which the rubric penalizes on specificity.

Suggestions

Broaden the action list beyond reacting and pinning/unpinning to include send/edit/delete messages and member info, so the description reflects the skill's full capabilities.

Rephrase to third person to avoid the voice penalty — e.g., "Use when controlling Slack from Clawdbot via the slack tool, including reacting to messages, pinning/unpinning items, or sending/editing/deleting messages in channels or DMs."

DimensionReasoningScore

Specificity

The description names the Slack domain and a couple of concrete actions ("reacting to messages or pinning/unpinning items"), but omits core capabilities like send/edit/delete messages and member info, so it is not comprehensive; the second-person phrasing "Use when you need to control Slack" triggers the rubric's voice penalty, reducing specificity by one.

1 / 3

Completeness

It answers both 'what' (control Slack via the slack tool, reacting/pinning) and 'when' with an explicit "Use when you need to control Slack from Clawdbot via the slack tool" trigger clause.

3 / 3

Trigger Term Quality

It includes natural terms a user would actually say — "control Slack", "reacting to messages", "pinning/unpinning", "Slack channels or DMs" — giving good coverage of trigger vocabulary.

3 / 3

Distinctiveness Conflict Risk

The niche is distinct — controlling Slack specifically through Clawdbot's slack tool — so it is unlikely to trigger for or conflict with other skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
huangruiteng/CS-Notes
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.