CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-discord

Add Discord bot channel integration via Chat SDK.

Quality

81%

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

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 body is an exemplary executable workflow: directive-based steps with pinned versions, concrete curl/jq commands, explicit validation checkpoints with failure-mode explanations, and actionable troubleshooting with retry loops. Its only real gaps are minor token inefficiency (Discord-basics explanations) and a monolithic single-file structure where the Channel Info and Troubleshooting sections could be split into references.

DimensionReasoningScore

Conciseness

Directive fences carry the mechanical steps compactly and the rationale prose is project-specific ("Build first: it guards the typed createChatSdkBridge(...) core call and proves the dependency is installed"), but minor over-explanation of Discord basics ("Discord has 'servers' (also called 'guilds') containing 'channels.' Text channels start with #.") could be trimmed.

4 / 5

Actionability

Every step is copy-paste executable: a file list to copy, an exact barrel import to append, a pinned dependency (@chat-adapter/discord@4.41.1), build and vitest commands, exact curl calls with jq pipelines, and a concrete env block. Nothing is pseudocode or left to inference.

5 / 5

Workflow Clarity

The Apply → Credentials → Restart → Invite → Resolve DM sequence is explicit with real validation checkpoints (build guard, registration test, "A bad token fails here, before the restart"), inline retry guidance ("if Discord refuses... invite it, then retry"), and troubleshooting feedback loops ("red means the barrel import or the @chat-adapter/discord install drifted, so re-run the Apply steps").

5 / 5

Progressive Disclosure

The single-file skill (no references/, scripts/, or assets/ exist) is well organized into clearly signaled sections (Apply, Credentials, Restart, Invite, Resolve DM, Channel Info, Troubleshooting). At ~163 lines it exceeds the under-50-line simple-skill exception, and Channel Info / Troubleshooting detail could live in reference files, so minor organization gaps keep it below 5.

4 / 5

Total

18

/

20

Passed

Description

65%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, specific, and names a distinct platform niche, so conflict risk is minimal. Its main weakness is the missing "Use when..." trigger clause, which caps completeness, and it covers only a single action rather than the full set of things the skill does. It is a solid but not exemplary description.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding a Discord bot, connecting a Discord server or DM channel, or when the user mentions Discord setup."

Enumerate the concrete actions the skill performs, e.g. "Copies and registers the Discord adapter, pins the @chat-adapter/discord dependency, stores bot credentials, and resolves the owner DM channel."

Include natural synonym terms users say, such as "server", "guild", "DM", or "invite the bot", to improve trigger matching.

DimensionReasoningScore

Specificity

"Add Discord bot channel integration via Chat SDK" names a precise domain and one concrete action with its mechanism, matching the anchor for 1-2 concrete actions without broader coverage; it is not anchor 4 because only a single action ("Add ... integration") is described.

3 / 5

Completeness

The "what" is clear ("Add Discord bot channel integration via Chat SDK"), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines; not 4 because the "when" is entirely missing rather than merely imprecise.

3 / 5

Trigger Term Quality

"Discord", "bot", "channel", and "integration" are natural terms a user would say when needing this skill, giving good keyword coverage; it falls short of anchor 5 because common variations like server, guild, DM, or message are absent.

4 / 5

Distinctiveness Conflict Risk

"Discord bot channel integration" names an explicit platform and niche, so sibling channel skills (e.g., Slack or Telegram adapters) would not be triggered by it — a clear niche with minimal conflict risk.

5 / 5

Total

15

/

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-discord/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.