CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

discord-bot

Discordlancer's discord.js conventions - adding a command, the command gate (owner-only, project channel, client, stage), replies and deferring, user-facing errors, channel permissions, invites and join tracking, and testing in the real server. Use whenever work touches src/discord/, a slash command, a button, channel or invite handling, or the bot's wording, even if the user only says "add a command", "the bot says", "the channel" or "the invite".

Quality

97%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A dense, high-signal conventions document: every rule is project-specific and executable, workflows carry explicit validation and error-recovery paths, and the single-file structure is the right shape for its length. The only deduction is the unpinned-in-place 'discord.js 14.27' version reference, which is time-sensitive information outside a deprecation section.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no explanation of what Discord or discord.js is, every line carrying project-specific facts ("Discord expects an answer within 3 seconds", "Nothing is ever deleted", "Only one bot process may run at a time"). However, the time-sensitive version pin "discord.js 14.27" appears outside any 'old patterns'/'deprecated' section, which the guidelines say should penalize conciseness. Not 5: the version-number mention is the one token that doesn't durably earn its place; not 3: everything else is uniformly tight with zero padding.

4 / 5

Actionability

Guidance is concrete throughout: exact file paths ("src/discord/commands/<name>.ts", "src/discord/texts.ts"), exact Command fields ("access", "where", "stages", "definition", "execute(run)"), exact APIs and commands ("interaction.deferReply()", "flags: MessageFlags.Ephemeral", "npm run commands:register", "safeReply", "createGitHub(env, { fetch })"), and concrete naming conventions ("dl-test-*"). Per the rubric's code-vs-instruction note, this instruction-only skill's absence of full code is not penalized since the guidance is fully executable. Not 4: there are no gaps — a reader can add a command, handle a join, and test it without guessing anything.

5 / 5

Workflow Clarity

"Adding a command" is a clear 3-step sequence with explicit validation ("Add tests for any pure logic it has, and check helpText lists it at the right stages"), and "Testing in the real server" gives a sequenced checklist (unit-test pure parts → try each command → note second-account items in TODO.md). Error-recovery feedback loops are present: joins that match "none or several" route to Boran via owner-desk and /link-client, and unmatched cases are handled rather than ignored. Not 4: checkpoints are explicit in both workflows, including cleanup ("list what was created so Boran can clean up").

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the ~55-line body is appropriately self-contained with clean section headers (Adding a command, The gate, Replies and errors, Channels and permissions, Invites and joins, Testing in the real server) — matching the rubric's simple-skill allowance of 5 for short, well-organized content with no need for external references. The only external pointers ("Read typescript-node and surreal-data first", the Context7 guidance) are one level deep and clearly signaled. Not 4: nothing that belongs in a separate file is inlined, and no references are buried.

5 / 5

Total

19

/

20

Passed

Description

100%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.

An exemplary description: third-person voice, a concrete enumeration of the skill's capability areas, and an explicit 'Use whenever...' clause that includes both direct triggers (slash command, button, invite handling) and the indirect phrasings a user would actually say. It is project-specific enough to carry no conflict risk.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capability areas with sub-detail: "adding a command, the command gate (owner-only, project channel, client, stage), replies and deferring, user-facing errors, channel permissions, invites and join tracking, and testing in the real server" — comprehensive coverage of the skill's scope, matching the anchor 'Lists multiple specific concrete actions; comprehensive coverage'. Not 4: the enumeration is exhaustive for this skill, with parenthetical elaboration, leaving no minor gaps.

5 / 5

Completeness

Both what and when are explicit: the 'what' is the enumerated conventions list, and the 'when' is a concrete "Use whenever work touches src/discord/, a slash command, a button, channel or invite handling, or the bot's wording" clause with concrete trigger phrases. This mirrors the anchor-5 example structure. Not 4: the 'when' clause is fully explicit with indirect-speech triggers, not merely present.

5 / 5

Trigger Term Quality

Natural user phrasings are explicitly covered: "a slash command, a button, channel or invite handling, or the bot's wording, even if the user only says 'add a command', 'the bot says', 'the channel' or 'the invite'" — it anticipates both direct and indirect trigger phrasings, matching the comprehensive-synonyms anchor. Not 4: it goes beyond good keyword coverage by enumerating the exact abbreviated phrases a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

The skill is niched to "Discordlancer's discord.js conventions" with project-specific paths ("src/discord/") and bot-specific triggers ("the bot's wording", "the invite"), giving it a clear niche with minimal conflict risk against generic skills. Not 4: the project name plus file-path triggers make overlap with any other skill essentially impossible.

5 / 5

Total

20

/

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

boranfurkan/discordlancer

Path

.claude/skills/discord-bot/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.