twitter-automation
Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas.
73
65%
Does it follow best practices?
Impact
85%
1.32xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/twitter-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 reasonably specific about capabilities and clearly identifies its domain (Twitter/X via Rube MCP/Composio), making it distinctive. However, it lacks an explicit 'Use when...' clause and misses common natural trigger terms users would say (e.g., 'tweet', 'retweet', 'timeline'). Adding trigger guidance and more user-facing vocabulary would improve skill selection accuracy.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to tweet, post on Twitter/X, search tweets, manage bookmarks or lists, or interact with the Twitter/X API.'
Include more natural user trigger terms like 'tweet', 'retweet', 'like', 'follow', 'timeline', 'DM' to improve matching against common user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: posts, search, users, bookmarks, lists, media. Also includes a procedural instruction ('Always search tools first for current schemas'). | 3 / 3 |
Completeness | Clearly answers 'what' (automate Twitter/X tasks including posts, search, users, bookmarks, lists, media) but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Twitter/X', 'posts', 'search', 'bookmarks', 'lists', 'media', but misses common user phrasings like 'tweet', 'timeline', 'follow', 'retweet', 'like'. 'Rube MCP (Composio)' is technical jargon unlikely to be used by most users. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Twitter/X', 'Rube MCP (Composio)', and the specific task categories creates a clear niche that is 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 is a comprehensive and well-structured skill that clearly documents Twitter/X automation workflows with good sequencing and pitfall documentation. Its main weaknesses are verbosity (redundant pitfalls, large inline reference table) and lack of concrete executable examples showing actual MCP tool invocations with sample parameters. The content would benefit from trimming repeated information and adding at least one concrete end-to-end example.
Suggestions
Add at least one concrete, copy-paste-ready example showing an actual MCP tool invocation with real parameters (e.g., a complete RUBE_SEARCH_TOOLS call followed by TWITTER_CREATION_OF_A_POST with sample payload).
Remove duplicated pitfall information — consolidate character limits, rate limits, and idempotency warnings into the 'Known Pitfalls' section only, and reference it from individual workflows instead of repeating.
Consider moving the quick reference table and search query syntax into a separate reference file to reduce the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-organized but is quite long (~200+ lines) with some redundancy. The 'Known Pitfalls' section repeats information already stated in per-workflow pitfalls (e.g., character limits, idempotency). The quick reference table duplicates tool names already listed in each workflow section. Some trimming would improve token efficiency. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and clear sequences, which is good. However, there are no executable code examples or concrete MCP call examples with actual payloads. The media upload flow is described in pseudocode-like numbered steps rather than showing an actual tool invocation with parameters. The guidance is specific but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps, prerequisite/required/optional annotations, and explicit pitfalls for each workflow. The setup section includes a verification step (confirm ACTIVE status before proceeding). The tool sequences are well-ordered with clear dependencies. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's monolithic — all content is inline in a single file. The detailed per-workflow pitfalls, search query syntax reference, and the full quick reference table could be split into separate files. The external link to Composio docs is helpful but the skill itself could benefit from splitting. | 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- 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.