discord-automation
Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill discord-automation74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 89%
↑ 1.85xAgent success when using this skill
Validation for skill structure
Discovery
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 effectively communicates specific Discord capabilities and has a clear, distinct niche through the Rube MCP integration. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users would actually say when requesting Discord automation help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to automate Discord, send messages, manage servers, or work with Discord bots.'
Include more natural user-facing trigger terms like 'Discord bot', 'server management', 'send DM', 'create server' that users would naturally say when requesting these capabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'messages, channels, roles, webhooks, reactions' - these are distinct, actionable Discord capabilities rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers 'what' (automate Discord tasks via Rube MCP with specific capabilities) but lacks an explicit 'Use when...' clause. The 'when' is only implied by mentioning Discord. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Discord', 'messages', 'channels', 'roles', 'webhooks', 'reactions' but missing common user variations like 'bot', 'server', 'DM', 'direct message', or action verbs users might say like 'send message', 'create channel'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets Discord automation via Rube MCP (Composio). The combination of platform (Discord) and integration method (Rube MCP) makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of Discord automation workflows with clear sequencing and good pitfall documentation. However, it lacks executable examples showing actual tool invocations, and the content is somewhat verbose with redundant information between the workflows and quick reference sections. The structure is solid but could benefit from concrete code/call examples.
Suggestions
Add executable MCP tool call examples showing complete parameter structures (e.g., actual RUBE_SEARCH_TOOLS and DISCORDBOT_CREATE_MESSAGE invocations with JSON parameters)
Remove the Quick Reference table or consolidate it with Core Workflows to eliminate redundancy
Remove explanations of Discord concepts Claude already knows (snowflake IDs, permission bitfields) or move to a separate reference file
Add a concrete end-to-end example showing a complete workflow from connection verification through message sending
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the Quick Reference table duplicates information from the Core Workflows section, and some explanations (like snowflake IDs, permission bitfields) are concepts Claude likely knows. Could be tightened. | 2 / 3 |
Actionability | Provides tool names and parameter lists but lacks executable code examples. The workflows describe sequences but don't show actual MCP tool calls with complete parameter structures. Key parameters are listed but not demonstrated in context. | 2 / 3 |
Workflow Clarity | Clear multi-step sequences with labeled steps (Required/Optional/Prerequisite). Each workflow has explicit tool ordering, pitfalls section warns of common errors, and the setup section includes verification steps before proceeding. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file. The Quick Reference table and detailed workflows could be split. External link to Composio docs is good, but no internal file references for advanced topics. | 2 / 3 |
Total | 9 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.