CtrlK
BlogDocsLog inGet started
Tessl Logo

add-slack

Add Slack channel integration via Chat SDK.

59

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-slack/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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 a well-validated, clearly sequenced workflow, but it is a long monolithic document with no progressive-disclosure structure and some duplicated content. Splitting peripheral detail into reference files would improve token efficiency and navigation.

Suggestions

Extract the duplicated Slack app creation steps (shared OAuth scopes, App Home setup) into a single referenced block to remove the socket/webhook duplication.

Move the detailed operator-setup walkthroughs and/or Troubleshooting into one-level-deep reference files (e.g. SLACK-SETUP.md) signaled from the main body.

Tighten the Credentials tradeoff prose so only decision-relevant detail remains inline.

DimensionReasoningScore

Conciseness

The prose is mostly tight and purposeful with no irrelevant concept explanations, but the ~200-line body duplicates the full OAuth scope list across the socket and webhook operator blocks and could be tightened.

2 / 3

Actionability

Every step ships executable, copy-paste-ready guidance: exact nc: directives, a pinned dependency version, real pnpm/curl commands, and concrete Slack API scopes.

3 / 3

Workflow Clarity

A clearly numbered sequence (Apply, Credentials, Resolve DM, Restart) with explicit validation checkpoints (build guard, registration test, auth.test fast-fail) and idempotent re-run feedback loops for recovery.

3 / 3

Progressive Disclosure

Sections are well organized, but the skill is a single monolithic file with no bundle references; lengthy operator-setup and troubleshooting blocks sit inline rather than being split into one-level-deep reference files.

2 / 3

Total

10

/

12

Passed

Description

57%Weight 40%Scale 1-3

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 clearly niche-targeted, but it omits any explicit usage trigger and only names a single action. Adding a 'Use when...' clause with natural trigger terms would lift its weakest dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when adding Slack as a chat channel, connecting a Slack app, or wiring Slack message delivery.'

Broaden natural trigger terms to include 'Slack app', 'connect Slack', and 'Slack messages' rather than relying on the jargony 'Chat SDK'.

Name a second concrete action (e.g. 'registers the adapter and stores Slack credentials') to push specificity toward multiple specific actions.

DimensionReasoningScore

Specificity

Names a concrete action and domain ("Add Slack channel integration") plus the mechanism ("via Chat SDK"), but lists only a single action rather than multiple specific concrete actions.

2 / 3

Completeness

It clearly states what the skill does but provides no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

"Slack", "channel", and "integration" are natural terms a user would say, but "Chat SDK" is technical jargon and common variations like "Slack app" or "connect Slack" are absent.

2 / 3

Distinctiveness Conflict Risk

The Slack-specific niche ("Add Slack channel integration") is clearly distinguishable and unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

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
nanocoai/nanoclaw
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.