CtrlK
BlogDocsLog inGet started
Tessl Logo

discord-automation

Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.

57

Quality

66%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/discord-automation/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured and actionable, laying out concrete tool sequences with parameters and pitfalls for each Discord workflow, but it lacks validation/confirmation feedback loops around its destructive operations and carries minor redundancy in the quick-reference table and a filler closing line.

Suggestions

Add explicit validation/confirmation steps before destructive calls (e.g., 'Confirm role_id and member count before DELETE_GUILD_ROLE, since it removes the role from all members') to lift workflow_clarity above the destructive-operations cap.

Remove or trim the redundant Quick Reference table and the generic 'When to Use' line to tighten conciseness toward 5.

For batch list operations, add an explicit pagination/verification checkpoint so Claude confirms it has retrieved all relevant items before mutating them.

DimensionReasoningScore

Conciseness

The body is mostly lean with no padded explanations of concepts Claude already knows, but the Quick Reference table duplicates tool slugs already in the workflow sections and the final 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview') is filler, so it sits just below the fully-lean 5 anchor.

4 / 5

Actionability

Concrete, named tool slugs (e.g., DISCORDBOT_CREATE_MESSAGE) with key parameters (channel_id, content, role_id) and per-workflow pitfalls give mostly executable guidance; it is not quite copy-paste ready code, but for an MCP tool-orchestration skill the specificity is strong, matching the 4 anchor.

4 / 5

Workflow Clarity

Workflows are clearly sequenced with [Prerequisite]/[Required]/[Optional] tags and an ACTIVE-connection checkpoint in Setup, but destructive and batch operations (DELETE_GUILD_ROLE, DELETE_ALL_MESSAGE_REACTIONS) have no explicit validate/confirm feedback loop, so the destructive-operations cap of 3 applies.

3 / 5

Progressive Disclosure

No bundle files exist, so all content is a single ~180-line SKILL.md with well-organized sections and headers; structure is good with only minor content (Quick Reference, Common Patterns) that could be split, matching the 4 rather than 5 anchor since it exceeds the under-50-line simple-skill exception.

4 / 5

Total

15

/

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 specific and clearly distinct, naming five Discord capability areas and the Rube MCP mechanism, but it omits any explicit "Use when..." trigger guidance and leans on a single generic verb, capping completeness and specificity.

Suggestions

Add a 'Use when...' clause stating concrete user triggers (e.g., 'Use when the user wants to send Discord messages, manage roles or webhooks, or handle reactions').

Replace the generic 'Automate Discord tasks' with concrete action verbs (send, create, assign, edit) to lift specificity toward 5.

Include common synonyms like 'servers' (for guilds) and 'DMs' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the Discord domain and five concrete capability areas ("messages, channels, roles, webhooks, reactions"), but the only action verb is the generic "Automate"; specific verbs like send, create, or manage are not stated, so it falls short of the multi-action 4 anchor.

3 / 5

Completeness

It clearly states what the skill does ("Automate Discord tasks via Rube MCP") but lacks any "Use when..." trigger clause; the trailing "Always search tools first" is procedural, not a usage trigger, so the missing-when cap of 3 applies.

3 / 5

Trigger Term Quality

Natural terms users would say are present ("Discord", "messages", "channels", "roles", "webhooks", "reactions"), but common synonyms such as "servers" or "DMs" are missing, placing it just below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The Discord automation niche via "Rube MCP (Composio)" is highly specific with distinct triggers and minimal realistic overlap with other skills, matching the clear-niche 5 anchor.

5 / 5

Total

15

/

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.