CtrlK
BlogDocsLog inGet started
Tessl Logo

add-discord

Add Discord bot channel integration to NanoClaw.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-discord/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 body is a well-sequenced, highly actionable workflow with strong validation checkpoints and feedback loops for risky operations. Its main weakness is monolithic inline content with no progressive disclosure to reference files, though the in-file structure is clean.

DimensionReasoningScore

Conciseness

The body is mostly lean — bash/code blocks and terse phase headings with little concept explanation — but a few prose passages (e.g., the "This merges in" bullet list) could be tightened further.

4 / 5

Actionability

Guidance is fully executable: concrete git, npm, vitest, sqlite3, and `npx tsx setup/index.ts` commands with explicit flags cover the common cases, and user-facing steps are given as copy-ready prompts.

5 / 5

Workflow Clarity

A clear five-phase sequence with explicit validation checkpoints ("Validate code changes", "All tests must pass... before proceeding", Phase 5 Verify) and feedback loops for the destructive git-merge and env-config operations.

5 / 5

Progressive Disclosure

Content is well-organized into labeled phases and troubleshooting with clear section structure, but everything lives inline in SKILL.md with no external references, so some self-contained blocks (bot-creation walkthrough, troubleshooting) could be split out.

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 names a specific, distinguishable niche, but it states only a single action and omits any "Use when" trigger guidance, capping completeness and trigger quality. Adding a trigger clause and one or two more concrete actions would lift it toward the top anchors.

Suggestions

Append a "Use when..." clause naming natural triggers (e.g., "Use when adding Discord bot support or when the user asks to connect Discord to NanoClaw").

Broaden the action list beyond "add" to surface concrete capabilities (e.g., registers the channel, configures the bot token, verifies connectivity).

Include common synonyms/extensions users might say (Discord, bot token, server, channel ID) to improve trigger term coverage.

DimensionReasoningScore

Specificity

"Add Discord bot channel integration to NanoClaw" names the domain (Discord bot channel) and a concrete action (add integration) targeting a specific system, but offers only one action and no breadth of capability.

3 / 5

Completeness

The "what" is clear (add Discord bot channel integration to NanoClaw), but there is no "when"/"Use when" clause; per the guideline a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say ("Discord", "bot", "channel") are present, but there are no synonyms or file extensions and no "Use when" phrasing to surface them as triggers.

3 / 5

Distinctiveness Conflict Risk

Naming both a specific channel type (Discord bot) and a specific target system (NanoClaw) carves a clear niche with minimal overlap risk, though the brevity leaves minor ambiguity versus other NanoClaw channel skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.