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:Lingjie-chen/MT5 --skill discord-automation71
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/skillValidation 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 automation capabilities and is highly distinctive due to platform and tool specificity. 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 a 'Use when...' clause with explicit triggers like 'Use when the user asks about Discord bots, sending Discord messages, managing server roles, or automating Discord workflows'
Include more natural user language variations such as 'Discord bot', 'server management', 'send DM', 'post to channel', or 'Discord automation'
| 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 with specific capabilities) but lacks an explicit 'Use when...' clause. The 'when' is only implied by mentioning Discord and the tool names. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Discord', 'messages', 'channels', 'roles', 'webhooks', but missing common user variations like 'bot', 'server', 'DM', 'send message', or action verbs users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Discord', 'Rube MCP', and 'Composio' as unique identifiers. Unlikely to conflict with other skills due to the specific platform and tooling mentioned. | 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 concrete executable examples (actual MCP tool call payloads) and contains some redundancy between the workflows and quick reference table. The content would benefit from showing actual tool invocation examples rather than just listing parameters.
Suggestions
Add at least one complete executable example per workflow showing the actual MCP tool call with real parameter values (e.g., `RUBE_SEARCH_TOOLS` call followed by `DISCORDBOT_CREATE_MESSAGE` with full payload)
Remove or consolidate the Quick Reference table with the Core Workflows section to reduce redundancy
Remove explanations of concepts Claude knows (snowflake IDs, bitwise permissions) or move to a separate reference file if needed for user context
| 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 concrete payloads. Key parameters are listed but no complete request/response examples are provided. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional). Each workflow includes pitfalls section that serves as validation guidance. The setup section has explicit verification steps before proceeding. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file. The skill could benefit from splitting detailed workflows or the quick reference into separate files. External link to Composio docs is good, but no internal file references for deeper content. | 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.