twitter-automation

Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas.

1.32x

Quality

—

Does it follow best practices?

Impact

85%

1.32x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable MCP skill body with clear sequenced workflows and validation checkpoints. It loses points for redundant content (Quick Reference + Known Pitfalls repeating workflow detail) and for keeping everything inline with no progressive disclosure.

Suggestions

Remove the duplicated pitfalls from the "Known Pitfalls" section or the per-workflow Pitfalls blocks so each fact appears once, trimming the token budget.

Consider moving the per-workflow parameter detail or the Quick Reference into a reference file referenced one level deep, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and avoids explaining Twitter/API basics, but the Quick Reference table and the Known Pitfalls section duplicate tool slugs and pitfalls already stated in the per-workflow sections, so not every token earns its place.	2 / 3
Actionability	Provides concrete tool slugs (e.g., TWITTER_CREATION_OF_A_POST), typed key parameters (e.g., "text: max 280 weighted characters"), and a 3-step media upload flow — specific, copy-paste-ready MCP guidance.	3 / 3
Workflow Clarity	Each workflow has a numbered tool sequence with [Prerequisite]/[Required]/[Optional] markers, and Setup includes explicit validation checkpoints (confirm RUBE_SEARCH_TOOLS responds, confirm connection is ACTIVE before proceeding).	3 / 3
Progressive Disclosure	Content is well-sectioned but lives entirely in one ~228-line file with no bundle references and no split into deeper files; the detailed per-tool parameter tables and pitfalls could be separated for a multi-workflow skill of this size.	2 / 3
	Total	10 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that names concrete capabilities and natural trigger terms. Its main weakness is the missing explicit "when to use" guidance, which caps completeness.

Suggestions

Add an explicit "Use when..." clause naming user intents (e.g., posting tweets, searching, managing bookmarks or lists) so Claude knows when to invoke the skill.

Consider including "tweets" alongside "posts" as an alternate natural term users frequently say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "posts, search, users, bookmarks, lists, media" — matching the top anchor of named, specific capabilities rather than vague abstraction.	3 / 3
Completeness	Clearly states what the skill does but lacks an explicit "Use when..." trigger clause; the closing "Always search tools first" is an instruction, not a usage trigger, so completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	Covers natural terms users would say ("Twitter/X", "posts", "search", "users", "bookmarks", "lists", "media") with good breadth of common phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to Twitter/X via Rube MCP (Composio), a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Commit: 366e45b

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.