CtrlK
BlogDocsLog inGet started
Tessl Logo

discord-bot-architect

Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding.

51

Quality

56%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/discord-bot-architect/SKILL.md

The canonical home for this skill is discord-bot-architect in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

43%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 skill supplies genuinely useful concrete code for Discord.js and Pycord setups, but its quality is undermined by duplicated fences, truncated code blocks, a broken Sharp Edges table, and no real workflow or external reference structure.

Suggestions

Complete the truncated code blocks (interactionCreate.js, the Pycord cog, and the interactive-components handler) so every example is copy-paste executable.

Fix the duplicated opening code fences and rebuild the Sharp Edges table with real issues, severities, and concrete solutions rather than placeholder 'Issue' rows.

Replace the generic 'When to Use' boilerplate with an explicit sequenced workflow (setup intents -> register commands -> wire events -> deploy) and split framework details into reference files (e.g. references/discordjs.md, references/pycord.md).

DimensionReasoningScore

Conciseness

The body largely assumes Claude's competence without over-explaining concepts, but wasted tokens appear in duplicated code fences, three truncated code blocks, a broken Sharp Edges table, and a generic 'When to Use' boilerplate line that could be tightened.

3 / 5

Actionability

Several blocks are complete and executable (index.js, ping.js, main.py), but three code examples are truncated mid-statement ('name: Event', '@commands.Cog.', 'else if (i.custo'), leaving incomplete rather than copy-paste-ready guidance.

3 / 5

Workflow Clarity

The body is organized as patterns/anti-patterns with no sequenced bot-building workflow, the Sharp Edges table is broken (every row literally 'Issue' with no real solutions), and there are no validation checkpoints or feedback loops.

2 / 5

Progressive Disclosure

Section headers provide some structure, but as a single ~280-line file with no bundle files, content that clearly belongs in separate references (two full framework setups plus interactive components) is inlined rather than split.

3 / 5

Total

11

/

20

Passed

Description

70%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 clearly states what the skill does and is highly distinctive within the Discord-bot niche, but it omits any explicit 'Use when...' trigger guidance, which caps completeness and limits its activation clarity.

Suggestions

Append an explicit trigger clause, e.g. 'Use when building or debugging Discord bots, adding slash commands or interactive components, or working with Discord.js/Pycord.'

Add natural synonyms and file extensions (e.g. 'Discord.py', '.py', 'bot token', 'gateway') to broaden trigger-term coverage.

Reframe the coverage list as concrete actions ('Build, deploy, and shard Discord bots...') to lift specificity from topic-listing to action-oriented.

DimensionReasoningScore

Specificity

Names the domain plus several concrete technical areas ('gateway intents, slash commands, interactive components, rate limiting, and sharding') and two frameworks, but frames them as 'Covers...' topics rather than action verbs, leaving minor gaps versus the comprehensive-action anchor.

4 / 5

Completeness

The 'what' is clearly stated ('building production-ready Discord bots' plus coverage areas), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Discord bots', 'slash commands') plus framework names ('Discord.js', 'Pycord'), but lacks synonyms and file extensions, stopping short of comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche ('production-ready Discord bots' with named frameworks Discord.js and Pycord) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.