CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-slack

Add Slack channel integration via Chat SDK.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

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

This is a strong, highly operational skill body: every apply step is executable, validation is built in at each phase, and error recovery is documented. The only weaknesses are minor — some repeated disclaimers, a short concepts explainer, and a monolithic structure that could offload detail to reference files.

DimensionReasoningScore

Conciseness

The body is overwhelmingly operational (file lists, pinned deps, curl+jq one-liners, exact scopes), but has minor trimmable spots: the Slack terminology explainer ("Slack has 'workspaces' containing 'channels.'") restates knowledge Claude already has, and the agents-feature disclaimer repeats across the intro, Next Steps, and Troubleshooting. Anchor 4 (efficient, minor over-explanation), not 5 due to those repetitions.

4 / 5

Actionability

Fully executable throughout: an exact 13-path copy payload, exact barrel imports, a pinned dependency (@chat-adapter/slack@4.41.1), runnable build/vitest commands naming specific test files, copy-paste curl commands with jq validation, and exact token regexes and env var names. Matches anchor 5 (copy-paste ready, covers common cases).

5 / 5

Workflow Clarity

A clear numbered sequence (copy → register → install → build/validate → credentials → DM resolution → restart → next steps) with explicit validation checkpoints: build and tests gate the apply phase, auth.test "fast-fails a bad credential" before the restart, and Troubleshooting gives feedback loops (red registration test → re-run Apply steps). Matches anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is self-contained with well-organized sections (Apply / Credentials / Restart / Channel Info / Troubleshooting) and clearly signaled one-level pointers to sibling skills. The long inline credential walkthroughs are parser-consumed directive fences that belong in the body, but at ~215 lines some material (app-creation walkthroughs, troubleshooting detail) could be split into reference files — anchor 4, not 5 since the under-50-line exception does not apply.

4 / 5

Total

18

/

20

Passed

Description

53%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 concise and states a clear, distinct capability, but it is minimal: one action, no trigger guidance, and thin keyword coverage. Adding a "Use when..." clause and natural trigger phrases would lift the two heaviest-weighted dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to add Slack, connect a Slack bot or workspace, or chat with the agent via Slack DMs or channels."

Include natural trigger terms users would actually say — "Slack bot", "connect Slack", "Slack workspace", "DM" — to improve trigger term quality.

Briefly enumerate the concrete capabilities (bot messaging in DMs and channels, Socket Mode or webhook event delivery, multi-instance support) so the "what" is comprehensive rather than a single action.

DimensionReasoningScore

Specificity

"Add Slack channel integration via Chat SDK" names a specific domain and one concrete action with its mechanism, but coverage is minimal — no mention of bot setup, messaging, or DMs. It sits at anchor 3 (domain plus 1-2 concrete actions, not comprehensive), below 4 which requires several listed actions.

3 / 5

Completeness

The "what" is clear (add Slack channel integration via the Chat SDK), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4, because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

The natural keyword "Slack" is present, but common user phrasings like "Slack bot", "connect Slack", "DM", "workspace", or "chat" are missing. This matches anchor 3 (some relevant keywords, missing common variations) rather than 4, since most variations are absent.

3 / 5

Distinctiveness Conflict Risk

"Slack channel integration" carves a clear niche with the distinct trigger "Slack" and a specific mechanism (Chat SDK). However, the body references sibling skills (/slack-a2a-rooms, /slack-agent-flow, /slack-multi-instance, /migrate-slack-agents) that a bare Slack trigger could also match, giving minor overlap risk — anchor 4 rather than 5.

4 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nanocoai/nanoclaw

Path

.claude/skills/add-slack/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.