CtrlK
BlogDocsLog inGet started
Tessl Logo

twitter-automation

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

56

Quality

65%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/twitter-automation/SKILL.md

The canonical home for this skill is twitter-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 content is a well-structured, actionable reference for Twitter/X automation via Rube MCP, but it carries redundant pitfalls/table duplication and a filler closing line, and its destructive operations lack explicit verification checkpoints that would lift workflow clarity.

Suggestions

Remove the redundant "Known Pitfalls" section (or the per-workflow pitfalls) and the filler "When to Use" line to tighten token use.

Add explicit verify-before-act checkpoints for destructive ops, e.g. "Confirm the post ID via TWITTER_POST_LOOKUP_BY_POST_ID before calling DELETE."

Move the Quick Reference table and search-query syntax into a separate references file and link to it from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference material but includes redundancy: the "Known Pitfalls" section re-states the 280-character and non-idempotency pitfalls already given per workflow, the Quick Reference table repeats tool slugs, and the trailing "When to Use" line ("This skill is applicable to execute the workflow or actions described in the overview.") is pure filler.

3 / 5

Actionability

Concrete, executable guidance throughout: exact tool slugs (e.g. TWITTER_CREATION_OF_A_POST, TWITTER_RECENT_SEARCH), specific key parameters, search query operators, and a numbered media upload flow, but it lacks copy-paste example tool-call payloads so it stops short of fully ready-to-run.

4 / 5

Workflow Clarity

Workflows are clearly sequenced with numbered "Tool sequence" lists and [Prerequisite]/[Required]/[Optional] markers, and setup has an ACTIVE-status checkpoint, but destructive operations (TWITTER_POST_DELETE_BY_POST_ID, TWITTER_UNLIKE_POST, remove bookmark) and the non-idempotent post-creation flow lack explicit verify-before-act checkpoints, so the destructive-ops cap of 3 applies.

3 / 5

Progressive Disclosure

No bundle files exist and no external references are signaled; the skill is a single well-organized ~236-line document with clear section headers, but the large Quick Reference table and query-syntax block are the kind of bulk reference content that could be split into a separate file, so it is good but not exemplary.

4 / 5

Total

14

/

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 and distinct, naming a clear Twitter/X automation niche with good keyword coverage, but it lacks an explicit "Use when..." trigger clause, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to post, search, or manage Twitter/X content via Rube MCP."

Include natural synonyms such as "tweet", "retweet", and "timeline" to broaden trigger-term coverage.

Consider stating the destructive operations (delete post, unlike) up front so the capability surface is fully described.

DimensionReasoningScore

Specificity

Names the Twitter/X domain plus six concrete capability areas ("posts, search, users, bookmarks, lists, media"), listing several specific actions with only minor coverage gaps, but they are categories rather than granular actions so not a 5.

4 / 5

Completeness

The "what" is clear ("Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media"), but there is no explicit "Use when..." trigger clause; "Always search tools first" is operational guidance, not trigger guidance, so completeness caps at 3 per the rubric.

3 / 5

Trigger Term Quality

"Twitter/X", "posts", "search", "users", "bookmarks", "lists", "media" give good natural keyword coverage, but common synonyms like "tweet", "retweet", and "timeline" are missing, so below comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Automate Twitter/X tasks via Rube MCP (Composio)" carves a clear, narrow niche with a specific integration, so trigger conflict risk with other skills is minimal.

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