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

Low

Low-risk findings worth noting

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 strongly operational skill: every step is executable, validation and error-recovery loops are woven through the workflow, and the prose only explains repo-specific context Claude could not infer. The weaknesses are minor — some repetition of the shared-server note, a slightly long patch rationale, and no file split for the reference-style Channel Info and Troubleshooting sections.

Suggestions

State the shared-server DM requirement once (e.g., in the Credentials section) and reference it from the Invite and Resolve DM sections instead of repeating it three times.

If the skill grows, move the Channel Info reference table and Troubleshooting entries into a references/ file and link to them, keeping SKILL.md as the linear procedure.

Tighten the step-3 patch explanation by leading with the action (register the patch before install) and compressing the 4.41.1 bug narrative to one or two sentences.

DimensionReasoningScore

Conciseness

The body is dense and operational — repo-specific facts Claude could not know (the adapter 4.41.1 mention-serialization bug, pnpm patch reapplication behavior, ERR_PNPM_UNUSED_PATCH) justify their prose. Minor trims exist: "the bot can only DM you once you share a server" is repeated three times (operator block, Invite section, Resolve DM section), and the step-3 patch explanation runs long. This fits the level-4 anchor 'efficient; minor instances that could be trimmed' rather than the every-token-earns-its-place level 5.

4 / 5

Actionability

Every step is copy-paste ready: exact nc: directives with file lists, concrete pnpm/vitest/curl/jq commands with captures, a fully-formed invite URL with the permissions integer, named env vars with set-if-absent semantics, and a token-validation regex. This matches the level-5 anchor 'fully executable; copy-paste ready; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The sequence is explicit and numbered (copy → register → patch → install → build → test → credentials → restart → invite → resolve DM), with validation checkpoints throughout: the build guards the typed core call, two tests verify registration and the patch, the token is validated via applications/@me before the restart, and Troubleshooting provides feedback loops (re-run apply steps, vitest check, restart, inspect logs). Idempotency and fallback behavior are stated up front. This matches the level-5 anchor; no destructive/batch cap applies since steps are additive and idempotent.

5 / 5

Progressive Disclosure

No bundle files exist, and the single ~200-line document is organized into clear, well-ordered sections that suit a linear agent-executed procedure. However, the under-50-line exception for scoring 5 on sections alone does not apply, and the Channel Info and Troubleshooting sections are plausible candidates for a separate reference file. This fits the level-4 anchor 'good structure; most content appropriately placed; minor organization gaps'.

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, third-person, and unambiguous about what the skill does, with a highly distinctive domain trigger. Its main weakness is the absence of any 'when to use' trigger guidance and a single-action framing that undersells the skill's scope (adapter registration, patching, credentials, validation).

Suggestions

Add an explicit trigger clause, e.g.: "Use when adding Discord as a chat channel, wiring up a Discord bot, or when the user mentions Discord servers, guilds, or DMs."

Broaden the action coverage to reflect the skill's actual scope, e.g.: "Add Discord bot channel integration via the Chat SDK: copy and register the adapter, apply the pnpm patch, store bot credentials, and validate with registration and gateway tests."

Include one or two more natural synonyms users might say ("server", "guild", "DM") to strengthen trigger matching.

DimensionReasoningScore

Specificity

"Add Discord bot channel integration via Chat SDK" names a concrete domain (Discord bot, channel, Chat SDK) with one concrete action (add the integration). It is more informative than the level-2 anchor "Processes PDF files" but lists only a single action, matching the level-3 anchor 'names domain and 1-2 concrete actions, not comprehensive'.

3 / 5

Completeness

The 'what' is clear (adds Discord bot channel integration via the Chat SDK bridge) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It sits at the level-3 anchor: clear 'what', 'when' missing.

3 / 5

Trigger Term Quality

"Discord", "bot", and "channel" are exactly the natural terms a user would say when requesting this skill, giving good keyword coverage. A few natural variations are missing (e.g., "server", "guild", "DM", "messages"), which keeps it below the comprehensive level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

"Discord bot channel integration" carves out a clear niche with a distinct trigger term ("Discord") and minimal conflict risk — only sibling channel skills (e.g., Slack/Telegram) are even plausible competitors, and the platform name disambiguates. This matches the level-5 anchor.

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.