CtrlK
BlogDocsLog inGet started
Tessl Logo

add-slack

Add Slack as a channel. Can replace WhatsApp entirely or run alongside it. Uses Socket Mode (no public URL needed).

62

Quality

73%

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.

The content is a strong, executable, well-sequenced operational runbook with explicit validation checkpoints and feedback loops for risky git/env/service operations. The main gap is progressive disclosure: SLACK_SETUP.md is referenced but not bundled, so the deep-dive target is missing from the skill.

Suggestions

Add the referenced SLACK_SETUP.md to a references/ (or sibling) directory so the one-level reference resolves to a real file, or inline only its essential steps and drop the pointer.

Trim the Phase 3 quick summary to avoid duplicating SLACK_SETUP.md content and tighten conciseness toward a lean 5.

Consider extracting the lengthy 'Known Limitations' and 'Troubleshooting' sections into a separate reference file to keep the main workflow scannable.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — concrete commands with no padding explaining what Slack or npm is — though the Phase 3 quick summary partly duplicates content said to live in SLACK_SETUP.md and could be trimmed slightly.

4 / 5

Actionability

Fully executable throughout: copy-paste git/npm/npx commands with exact flags, concrete .env values, sqlite and curl troubleshooting queries — specific examples cover the common main-channel and additional-channel registration cases.

5 / 5

Workflow Clarity

Five clearly sequenced phases (Pre-flight → Apply → Setup → Registration → Verify) with explicit validation ('All tests must pass ... build must be clean before proceeding'), merge-conflict and scope-change feedback loops, and a structured troubleshooting section for error recovery.

5 / 5

Progressive Disclosure

Well-organized into clear phases and sections with a clearly signaled one-level reference to SLACK_SETUP.md, but that referenced file is not present in any bundle directory, and some inline troubleshooting/limitations content is dense; minor organization gaps remain.

4 / 5

Total

18

/

20

Passed

Description

58%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 specific and distinct, naming concrete actions and a clear niche, but it lacks an explicit 'when to use' trigger clause and has only partial natural-keyword coverage. Adding a 'Use when adding Slack to NanoClaw...' trigger phrase would raise both completeness and trigger_term_quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding Slack as a NanoClaw channel or when the user mentions Slack, Socket Mode, or replacing WhatsApp.'

Include natural synonyms/file extensions users might say (e.g. 'Slack', 'Slack app', 'Slack bot') to broaden trigger-term coverage beyond the single keyword.

Replace or supplement the technical 'Socket Mode' phrasing in the lead with a user-facing benefit term so the description reads as a natural request.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Add Slack as a channel', 'Can replace WhatsApp entirely or run alongside it', 'Uses Socket Mode (no public URL needed)' — but coverage of capabilities is not comprehensive.

4 / 5

Completeness

It clearly states what the skill does ('Add Slack as a channel') but has no 'Use when...' clause or equivalent explicit trigger guidance, so 'when' is only weakly implied — capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

'Slack' and 'channel' are natural keywords a user would say, but 'Socket Mode' is technical jargon and common synonyms/variations are missing, so keyword coverage is partial rather than good.

3 / 5

Distinctiveness Conflict Risk

'Add Slack as a channel' is a clear niche with a distinct trigger and low conflict risk, though 'channel' overlaps conceptually with WhatsApp, leaving minor overlap risk rather than a fully distinct niche.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
jbaruch/nanoclaw-telegram
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.