CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

twitter-automation

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/twitter-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The body is a well-structured, information-dense reference for the Rube MCP Twitter toolkit with concrete tool slugs, parameters, and pitfalls, and it largely respects Claude's competence. Its main weaknesses are the missing validation/verification checkpoints around destructive operations (delete post) and the non-idempotent posting flow, plus minor duplication between the workflow sections and the Quick Reference table.

Suggestions

Add explicit verification before destructive actions, e.g. look up the post by ID and confirm content with the user before TWITTER_POST_DELETE_BY_POST_ID.

Add a verify-and-deduplicate feedback loop for the non-idempotent posting workflow (check for an existing identical post before retrying a timed-out creation).

Move the Quick Reference tool catalog to a references file (e.g. references/tool-catalog.md) to cut duplication, and delete the boilerplate 'When to Use' closing sentence.

DimensionReasoningScore

Conciseness

The body is dense with API-specific facts Claude cannot know (exact Composio tool slugs, "280 weighted characters", "numeric strings, not integers", pagination token names) with essentially no explanation of known concepts. Minor trimmable padding exists: the Quick Reference table largely duplicates the workflow sections, and the closing 'When to Use' line ("This skill is applicable to execute the workflow or actions described in the overview") is filler. This matches 'Efficient; minor instances of over-explanation that could be trimmed' rather than the padded lower anchors.

4 / 5

Actionability

Highly actionable for an instruction-only skill: exact tool sequences ("TWITTER_USER_LOOKUP_ME - Get authenticated user info [Prerequisite]"), concrete parameter names and constraints ("media__media_ids": Array of media ID strings", "max_results": 10-100), and specific pitfalls. Per the scoring notes, absent code is not penalized if guidance is actionable; minor gaps (no example tool-call payloads or argument values) keep it at 4 rather than 5.

4 / 5

Workflow Clarity

Sequences are clearly numbered with [Prerequisite]/[Required]/[Optional] annotations and the Setup section has validation ("Confirm connection status shows ACTIVE before running any workflows"), but the destructive delete workflow ("TWITTER_POST_DELETE_BY_POST_ID") lacks an explicit verify-before-delete checkpoint, and no workflow has post-action verification or fix-retry feedback loops. Per the judging guidelines, missing validation in destructive operations caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Well-organized single-file skill: clear sections (Prerequisites, Setup, six Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) with no nonexistent references and no nested reference chains. It does not reach 5 because at ~230 lines the full tool catalog (Quick Reference table) is inline where a one-level-deep reference file could carry it, matching 'Good structure; most content is appropriately placed; minor organization gaps'.

4 / 5

Total

15

/

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.

The description is specific, distinct, and well-keyed to natural trigger terms for Twitter/X automation, but it omits any explicit 'when to use this skill' trigger clause, which both caps completeness and weakens its usefulness for skill selection. Adding a 'Use when...' sentence with common synonyms (tweet, like) would lift it to the top tier.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to post, search, bookmark, or manage tweets/X content.'

Include common synonyms such as 'tweet' and 'like' in the capability list so natural phrasings match.

Use action verbs (create, delete, search, bookmark) instead of bare nouns to sharpen the 'what'.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas — "posts, search, users, bookmarks, lists, media" — under the named domain "Automate Twitter/X tasks via Rube MCP (Composio)", comparable to the anchor 'Lists several specific actions; minor gaps in coverage'. It falls short of a 5 because the capabilities are bare nouns (no action verbs like create/delete/like) and coverage has gaps (likes, retweets, timeline not mentioned).

4 / 5

Completeness

The 'what' is clear ("Automate Twitter/X tasks... posts, search, users, bookmarks, lists, media"), but there is no 'Use when...' clause or equivalent explicit trigger guidance — "Always search tools first for current schemas" is procedural instruction, not a when-to-use trigger. Per the judging guidelines, a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "Twitter/X", "posts", "search", "bookmarks", "lists", "media" are terms users would naturally say. Not a 5 because common synonyms like "tweet" and "like/follow" are missing, matching 'Good keyword coverage; a few natural terms missing' rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers: Twitter/X automation tied to a specific stack ("Rube MCP (Composio)") and specific objects (posts, bookmarks, lists). Minimal conflict risk with other skills, matching the 'Clear niche with distinct triggers; minimal conflict risk' anchor; it is not generic like the lower-anchor examples ('Helps with document files').

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/twitter-automation/SKILL.md

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.