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.

70

1.85x
Quality

58%

Does it follow best practices?

Impact

89%

1.85x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/discord-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a comprehensive reference for Discord automation via Rube MCP with clear tool sequences and parameter documentation. Its main weaknesses are the lack of concrete executable examples (actual tool call payloads), missing validation/verification steps for destructive operations, and some redundancy between the workflow sections and the quick reference table. The content would benefit from being more concise and including at least one complete worked example.

Suggestions

Add at least one concrete, complete example showing an actual RUBE_SEARCH_TOOLS call followed by a tool invocation with real parameter values and expected response structure.

Add explicit validation/verification steps to destructive workflows (role deletion, reaction clearing) — e.g., 'Confirm the role exists and list affected members before deleting'.

Remove or significantly condense the 'Common Patterns' section (snowflake IDs, permission bitfields, pagination) as these are standard Discord API concepts Claude already knows.

Consider removing the quick reference table since it largely duplicates information already in the workflow sections, or keep only the table and make the workflow sections more concise.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some information Claude already knows (e.g., explaining what snowflake IDs are, what bitwise OR is, basic pagination concepts). The quick reference table at the end largely duplicates the workflow sections above it. Some sections like 'Common Patterns' explain Discord API concepts that are general knowledge rather than skill-specific guidance.

2 / 3

Actionability

The skill provides specific tool names and parameter lists, which is helpful, but lacks executable examples showing actual tool invocations with concrete parameter values. The tool sequences are clear but remain at the level of 'call this tool with these params' without showing example payloads or expected responses. The instruction to 'always call RUBE_SEARCH_TOOLS first' is good but no example invocation is shown.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with numbered steps and labeled as Required/Optional, which is good. However, there are no validation checkpoints or error recovery steps. For destructive operations like DELETE_GUILD_ROLE or DELETE_ALL_MESSAGE_REACTIONS, there's no verification step before or after. The setup section has a basic verification flow but the core workflows lack feedback loops.

2 / 3

Progressive Disclosure

The content is well-structured with clear sections and headers, but it's quite long (~180 lines) with no bundle files to offload detail into. The quick reference table, common patterns, and detailed workflow sections could benefit from being split into separate reference files. The single external link to Composio docs is appropriate but the skill itself is monolithic.

2 / 3

Total

8

/

12

Passed

Description

67%

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 specific about its capabilities, clearly identifying the Discord domain and the integration mechanism (Rube MCP/Composio). Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms could also be expanded to include more natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to send Discord messages, manage Discord servers, create channels, assign roles, or set up webhooks.'

Include more natural user-facing trigger terms like 'Discord bot', 'Discord server', 'send a message on Discord', 'manage a Discord server' to improve matching with how users phrase requests.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: messages, channels, roles, webhooks, reactions. Also specifies the tooling context (Rube MCP, Composio) and includes a concrete procedural instruction ('Always search tools first for current schemas').

3 / 3

Completeness

Clearly answers 'what' (automate Discord tasks via Rube MCP with specific task types listed), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the mention of Discord tasks. Per rubric guidelines, missing 'Use when...' caps completeness at 2.

2 / 3

Trigger Term Quality

Includes 'Discord', 'messages', 'channels', 'roles', 'webhooks', 'reactions' which are relevant keywords, but misses common user phrasings like 'send a message on Discord', 'create a channel', 'bot', 'server', or 'Discord bot'. The terms are somewhat technical/feature-oriented rather than how users naturally phrase requests.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive: specifies Discord as the platform, Rube MCP (Composio) as the integration method, and lists specific Discord-domain actions. Unlikely to conflict with other skills unless there's another Discord skill.

3 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
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.