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

63%

Does it follow best practices?

Impact

85%

1.32x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/twitter-automation/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

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 reference with concrete tool sequences and genuinely useful pitfalls, but it suffers from duplicated pitfall content, no validation steps around destructive/non-idempotent operations, and a monolithic single-file layout that would benefit from splitting the quick reference and workflow details into reference files.

Suggestions

Add verification steps before destructive/non-idempotent calls (e.g., confirm the post ID via TWITTER_POST_LOOKUP_BY_POST_ID before deleting; check for a recent duplicate post before creating).

Deduplicate the Known Pitfalls section against per-workflow Pitfalls, and move the Quick Reference table to a references/ file with a clearly signaled link.

Include one or two concrete example search queries showing operator combination (e.g., "from:user -is:retweet has:media").

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (tool sequences, parameters, pitfalls; no padding explaining Twitter itself), but "280 weighted characters" and "posting is NOT idempotent" each appear twice, and the 25-row Quick Reference table repeats tool slugs already listed in workflows. Anchor 3: mostly efficient but could be tightened.	3 / 5
Actionability	Concrete tool slugs with ordered sequences marked [Prerequisite]/[Required]/[Optional], named parameters with semantics, and specific pitfalls (e.g., "Media IDs must be numeric strings, not integers") give mostly executable guidance. Not a 5: no example query strings or sample request/response payloads to make it copy-paste ready.	4 / 5
Workflow Clarity	Setup has an explicit checkpoint ("Confirm connection status shows ACTIVE before running any workflows") and each workflow lists a sequence, but destructive operations (post delete, unlike) and non-idempotent post creation have no verification or feedback steps. The rubric caps workflow clarity at 3 for destructive/batch workflows lacking validation.	3 / 5
Progressive Disclosure	The single ~230-line file is well-sectioned but entirely inline: the 25-row Quick Reference table and per-workflow details could live in one-level-deep reference files. Anchor 3: content that should be separate is inline; not a 4 because no reference split exists despite the length.	3 / 5
	Total	13 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 concise, specific description that names the platform, the integration mechanism, and six capability areas with strong distinctiveness. Its main weakness is the missing "Use when..." trigger clause and the absence of the "tweet" synonym, which cap completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to post, search, tweet, or manage Twitter/X content."

Include the synonym "tweets" alongside "posts" and mention likes/retweets to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("posts, search, users, bookmarks, lists, media") with only minor gaps such as likes/retweets. Not a 5 because these are category nouns rather than comprehensive concrete actions (e.g., "create posts, search tweets, upload media").	4 / 5
Completeness	The "what" is clear (automate Twitter/X operations across posts, search, users, bookmarks, lists, media) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"Twitter/X", "posts", "search", "bookmarks" are terms users naturally say, giving good keyword coverage. Not a 5 because the most common synonym "tweet" is missing, along with "like", "follow", and "retweet".	4 / 5
Distinctiveness Conflict Risk	"Automate Twitter/X tasks via Rube MCP (Composio)" carves out a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 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
Path: plugins/all-skills/skills/twitter-automation/SKILL.md
Commit: c9856ea

Reviewed: 6 days 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.