CtrlK
BlogDocsLog inGet started
Tessl Logo

add-discord

Add Discord bot channel integration via Chat SDK.

61

Quality

71%

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-discord/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a tight, highly actionable operational workflow with strong validation and error-recovery guidance, scoring at the top of conciseness, actionability, and workflow clarity. Its only weakness is progressive disclosure: everything is inline with no file-level split for reference material.

DimensionReasoningScore

Conciseness

The body is directive-driven and dense with skill-specific rationale (idempotent fences, why build precedes test) rather than generic concepts Claude already knows; every section earns its tokens with little padding.

3 / 3

Actionability

It provides fully executable, copy-paste-ready guidance: exact curl calls against real Discord endpoints, pinned "@chat-adapter/discord@4.29.0", and concrete pnpm/vitest/restart commands inside nc: directives.

3 / 3

Workflow Clarity

A numbered Apply sequence (copy → register → install → build → test) is backed by explicit validation checkpoints (build guards the typed call, the registration test goes red on drift, 401 fails before restart) plus a troubleshooting section with feedback loops.

3 / 3

Progressive Disclosure

Sections are clearly organized, but the skill is monolithic with no bundle files or one-level-deep references, and reference-style material (Channel Info, Troubleshooting) lives inline where a split reference file could aid discovery.

2 / 3

Total

11

/

12

Passed

Description

50%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 concrete and on-domain but stops at a single action with no "Use when" trigger guidance, leaving every dimension at the midpoint. Adding explicit trigger terms and a use-when clause would lift specificity, completeness, and distinctiveness together.

Suggestions

Add a "Use when ..." clause naming natural triggers, e.g. "Use when adding a Discord bot channel, wiring up Discord DMs, or integrating Discord via the Chat SDK bridge."

Replace or supplement the internal "Chat SDK" jargon with user-facing terms (Discord bot, Discord server, DM channel, bot token) to improve trigger-term coverage.

List the concrete actions performed (copy/register the adapter, install the pinned package, store bot credentials, restart) so specificity reaches the multi-action anchor.

DimensionReasoningScore

Specificity

"Add Discord bot channel integration via Chat SDK" names the domain and a single concrete action ("Add ... integration") but does not list multiple specific actions, matching the anchor that names a domain and some actions without being comprehensive.

2 / 3

Completeness

It clearly states what the skill does ("Add Discord bot channel integration via Chat SDK") but provides no "Use when ..." clause or equivalent trigger guidance, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

"Discord bot channel" are natural terms a user would say, but coverage is thin (no "Discord server", "DM", "bot token") and "Chat SDK" is internal jargon rather than a user trigger, so it has some relevant keywords but misses common variations.

2 / 3

Distinctiveness Conflict Risk

The Discord-specific niche is fairly distinct, but the generic "channel integration via Chat SDK" framing could overlap sibling channel skills and there is no explicit trigger to differentiate them, so it is somewhat specific but could still overlap.

2 / 3

Total

8

/

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.