twitter-automation
Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill twitter-automation73
Quality
65%
Does it follow best practices?
Impact
85%
1.32xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/twitter-automation/SKILL.mdDiscovery
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.
This description effectively communicates specific Twitter/X automation capabilities and is highly distinctive due to platform naming. However, it lacks explicit trigger guidance ('Use when...') and misses common user vocabulary like 'tweet', 'retweet', or 'follow' that would improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to tweet, post to Twitter/X, search tweets, or manage their Twitter account'
Include common user vocabulary: 'tweet', 'retweet', 'follow', 'timeline', 'DM', '@mention' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'posts, search, users, bookmarks, lists, media' - these are distinct, actionable capabilities within the Twitter/X domain. | 3 / 3 |
Completeness | Clearly answers 'what' (automate Twitter tasks via Rube MCP) but lacks an explicit 'Use when...' clause. The instruction to 'search tools first' is operational guidance, not trigger guidance for when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes 'Twitter/X' and action terms like 'posts, search, bookmarks' which users might say, but missing common variations like 'tweet', 'retweet', 'follow', 'timeline', or '@mentions' that users naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche with 'Twitter/X' and 'Rube MCP (Composio)' making it highly distinct. Unlikely to conflict with other skills due to platform-specific naming. | 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 Twitter/X automation with well-structured workflows and clear sequencing. However, it lacks executable code examples (relying on tool names and parameter descriptions instead), and the document is lengthy enough that some content could be split into separate reference files. The pitfalls sections are valuable but contribute to overall verbosity.
Suggestions
Add concrete executable examples showing actual tool invocations with sample parameters, not just parameter lists (e.g., show a complete RUBE_SEARCH_TOOLS call followed by TWITTER_CREATION_OF_A_POST with real parameter values)
Consider moving the detailed workflow sections to a separate WORKFLOWS.md file, keeping only the Quick Reference table and setup in the main SKILL.md
Consolidate repeated pitfalls (e.g., 'User IDs are numeric strings' appears multiple times) into a single 'Common Pitfalls' section to reduce redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the Quick Reference table duplicates information already covered in the workflows, and some pitfalls are repeated across sections. The setup section could be tighter. | 2 / 3 |
Actionability | Provides tool names and parameter lists which is helpful, but lacks executable code examples. The Media Upload Flow shows a numbered process but no actual code. Tool sequences are listed but without concrete invocation examples showing exact parameter formats. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with explicit prerequisites marked, optional vs required steps labeled, and pitfalls documented for each workflow. The setup section includes a verification step before proceeding. Tool sequences provide clear ordering. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a quick reference table, but the document is quite long (200+ lines) and could benefit from splitting detailed workflows into separate files. All content is inline rather than appropriately distributed. | 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.