discord-automation
Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.
70
58%
Does it follow best practices?
Impact
89%
1.85xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/discord-automation/SKILL.mdQuality
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 is concise and specific about its domain (Discord automation) and lists concrete capability areas. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Trigger terms cover the basics but miss common user phrasings.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Discord automation, sending Discord messages, managing servers, creating channels, or working with Discord bots.'
Include more natural user-facing trigger terms like 'Discord bot', 'Discord server', 'send message on Discord', 'DM', 'manage Discord server' to improve matching against common user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: messages, channels, roles, webhooks, reactions. Also specifies the tool (Rube MCP/Composio) and includes a concrete procedural instruction ('Always search tools first for current schemas'). | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Discord tasks via Rube MCP), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the mention of Discord tasks. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes 'Discord', 'messages', 'channels', 'roles', 'webhooks', 'reactions' which are relevant keywords, but misses common user variations like 'send message', 'create channel', 'bot', 'server', 'DM', or 'Discord bot'. Also 'Rube MCP (Composio)' is technical jargon that users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to Discord automation via a specific tool (Rube MCP/Composio). The combination of Discord + specific MCP tool creates a distinct niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent reference skill that clearly documents Discord automation workflows with specific tool names, parameters, and pitfalls. Its main weaknesses are the lack of executable examples (no actual MCP call demonstrations), missing validation/error-recovery steps in workflows, 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 concrete end-to-end example.
Suggestions
Add at least one concrete, executable end-to-end example showing the actual MCP call syntax (e.g., a complete 'send a message to a channel' flow with real tool invocation format and expected responses).
Add explicit validation checkpoints to workflows — e.g., after sending a message, verify it was delivered; after role assignment, confirm the member's roles; handle 429 rate limit responses with a retry loop.
Remove or consolidate the quick reference table with the workflow sections to reduce redundancy, or move it to a separate REFERENCE.md file.
Trim the 'Common Patterns' section — Claude already understands snowflake IDs and bitwise operations; just list the specific permission values needed without explaining the concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some information Claude already knows (e.g., explaining what snowflake IDs are, basic permission bitfield concepts). The quick reference table at the end largely duplicates information already presented in the workflow sections. Some sections like 'Common Patterns' could be trimmed. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and clear tool sequences, which is good. However, it lacks executable examples — no actual MCP call syntax or concrete input/output examples are shown. The guidance is specific but not copy-paste ready; a user would need to figure out the exact call format by searching tools first. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps (Required/Optional/Prerequisite), and pitfalls are documented per workflow. However, there are no explicit validation checkpoints or error recovery loops — for example, no guidance on what to do if a message send fails, no 'verify the message was sent' step, and no handling of rate limit 429 responses beyond 'respect Retry-After headers.' | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table. However, at ~170 lines with no bundle files, some content (like the full quick reference table or the detailed webhook/reaction workflows) could be split into separate reference files. The single external link to Composio docs is appropriate but the skill is somewhat monolithic for its length. | 2 / 3 |
Total | 8 / 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.