Twitter/X Automation via Rube MCP

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/twitter-automation

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Twitter/X Automation via Rube MCP Automate Twitter/X operations through Composio's Twitter toolkit via Rube MCP.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, Common Patterns, Known Pitfalls, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• This skill is applicable to execute the workflow or actions described in the overview.
• Use when the request clearly matches the imported source intent: Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
2. Call RUBEMANAGECONNECTIONS with toolkit twitter
3. If connection is not ACTIVE, follow the returned auth link to complete Twitter OAuth
4. Confirm connection status shows ACTIVE before running any workflows
5. TWITTERUSERLOOKUP_ME - Get authenticated user info [Prerequisite]
6. TWITTERUPLOADMEDIA / TWITTERUPLOADLARGE_MEDIA - Upload media [Optional]
7. TWITTERCREATIONOFAPOST - Create a new post [Required]

Imported Workflow Notes

Imported: Setup

Get Rube MCP: Add

https://rube.app/mcp

1. Verify Rube MCP is available by confirming

   RUBE_SEARCH_TOOLS

   responds
2. Call

   RUBE_MANAGE_CONNECTIONS

   with toolkit

   twitter

3. If connection is not ACTIVE, follow the returned auth link to complete Twitter OAuth
4. Confirm connection status shows ACTIVE before running any workflows

Imported: Core Workflows

1. Create and Manage Posts

When to use: User wants to create, delete, or look up tweets/posts

Tool sequence:

1. TWITTER_USER_LOOKUP_ME

   - Get authenticated user info [Prerequisite]

2. TWITTER_UPLOAD_MEDIA

   /

   TWITTER_UPLOAD_LARGE_MEDIA

   - Upload media [Optional]

3. TWITTER_CREATION_OF_A_POST

   - Create a new post [Required]

4. TWITTER_POST_LOOKUP_BY_POST_ID

   - Look up a specific post [Optional]

5. TWITTER_POST_DELETE_BY_POST_ID

   - Delete a post [Optional]

Key parameters:

• text

  : Post text content (max 280 weighted characters)

• media__media_ids

  : Array of media ID strings for attachments

• reply__in_reply_to_tweet_id

  : Tweet ID to reply to

• quote_tweet_id

  : Tweet ID to quote

• id

  : Post ID for lookup/delete

Pitfalls:

• Post text is limited to 280 weighted characters; some characters count as more than one
• Posting is NOT idempotent; retrying on timeout will create duplicate posts
• Media IDs must be numeric strings, not integers
• UPLOAD_LARGE_MEDIA is for videos/GIFs; UPLOAD_MEDIA for images
• Always call USER_LOOKUP_ME first to get the authenticated user's ID

2. Search Posts

When to use: User wants to find tweets matching specific criteria

Tool sequence:

1. TWITTER_RECENT_SEARCH

   - Search recent tweets (last 7 days) [Required]

2. TWITTER_FULL_ARCHIVE_SEARCH

   - Search full archive (Academic access) [Optional]

3. TWITTER_RECENT_SEARCH_COUNTS

   - Get tweet count matching query [Optional]

Key parameters:

• query

  : Search query using Twitter search operators

• max_results

  : Results per page (10-100)

• next_token

  : Pagination token

• start_time

  /

  end_time

  : ISO 8601 time range

• tweet__fields

  : Comma-separated fields to include

• expansions

  : Related objects to expand

Pitfalls:

• RECENT_SEARCH covers only the last 7 days; use FULL_ARCHIVE_SEARCH for older tweets
• FULL_ARCHIVE_SEARCH requires Academic Research or Enterprise access
• Query operators:

  from:username

  ,

  to:username

  ,

  is:retweet

  ,

  has:media

  ,

  -is:retweet

• Empty results return

  meta.result_count: 0

  with no

  data

  field
• Rate limits vary by endpoint and access level; check response headers

3. Look Up Users

When to use: User wants to find or inspect Twitter user profiles

Tool sequence:

1. TWITTER_USER_LOOKUP_ME

   - Get authenticated user [Optional]

2. TWITTER_USER_LOOKUP_BY_USERNAME

   - Look up by username [Optional]

3. TWITTER_USER_LOOKUP_BY_ID

   - Look up by user ID [Optional]

4. TWITTER_USER_LOOKUP_BY_IDS

   - Batch look up multiple users [Optional]

Key parameters:

• username

  : Twitter handle without @ prefix

• id

  : Numeric user ID string

• ids

  : Comma-separated user IDs for batch lookup

• user__fields

  : Fields to return (description, public_metrics, etc.)

Pitfalls:

• Usernames are case-insensitive but must not include the @ prefix
• User IDs are numeric strings, not integers
• Suspended or deleted accounts return errors, not empty results
• LOOKUP_BY_IDS accepts max 100 IDs per request

4. Manage Bookmarks

When to use: User wants to save, view, or remove bookmarked tweets

Tool sequence:

1. TWITTER_USER_LOOKUP_ME

   - Get authenticated user ID [Prerequisite]

2. TWITTER_BOOKMARKS_BY_USER

   - List bookmarked posts [Required]

3. TWITTER_ADD_POST_TO_BOOKMARKS

   - Bookmark a post [Optional]

4. TWITTER_REMOVE_A_BOOKMARKED_POST

   - Remove bookmark [Optional]

Key parameters:

• id

  : User ID (from USER_LOOKUP_ME) for listing bookmarks

• tweet_id

  : Tweet ID to bookmark or unbookmark

• max_results

  : Results per page

• pagination_token

  : Token for next page

Pitfalls:

• Bookmarks require the authenticated user's ID, not username
• Bookmarks are private; only the authenticated user can see their own
• Pagination uses

  pagination_token

  , not

  next_token

5. Manage Lists

When to use: User wants to view or manage Twitter lists

Tool sequence:

1. TWITTER_USER_LOOKUP_ME

   - Get authenticated user ID [Prerequisite]

2. TWITTER_GET_A_USER_S_OWNED_LISTS

   - List owned lists [Optional]

3. TWITTER_GET_A_USER_S_LIST_MEMBERSHIPS

   - List memberships [Optional]

4. TWITTER_GET_A_USER_S_PINNED_LISTS

   - Get pinned lists [Optional]

5. TWITTER_GET_USER_S_FOLLOWED_LISTS

   - Get followed lists [Optional]

6. TWITTER_LIST_LOOKUP_BY_LIST_ID

   - Get list details [Optional]

Key parameters:

• id

  : User ID for listing owned/member/followed lists

• list_id

  : List ID for specific list lookup

• max_results

  : Results per page (1-100)

Pitfalls:

• List IDs and User IDs are numeric strings
• Lists endpoints require the user's numeric ID, not username

6. Interact with Posts

When to use: User wants to like, unlike, or view liked posts

Tool sequence:

1. TWITTER_USER_LOOKUP_ME

   - Get authenticated user ID [Prerequisite]

2. TWITTER_RETURNS_POST_OBJECTS_LIKED_BY_THE_PROVIDED_USER_ID

   - Get liked posts [Optional]

3. TWITTER_UNLIKE_POST

   - Unlike a post [Optional]

Key parameters:

• id

  : User ID for listing liked posts

• tweet_id

  : Tweet ID to unlike

Pitfalls:

• Like/unlike endpoints require user ID from USER_LOOKUP_ME
• Liked posts pagination may be slow for users with many likes

Imported: Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
• Active Twitter connection via

  RUBE_MANAGE_CONNECTIONS

  with toolkit

  twitter

• Always call

  RUBE_SEARCH_TOOLS

  first to get current tool schemas

Examples

Example 1: Ask for the upstream workflow directly

Use @twitter-automation to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @twitter-automation against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @twitter-automation for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @twitter-automation using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/twitter-automation

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @trpc-fullstack

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @trust-calibrator

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @turborepo-caching

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @tutorial-engineer

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Quick Reference

Imported: Common Patterns

Search Query Syntax

Operators:

• from:username

  - Posts by user

• to:username

  - Replies to user

• @username

  - Mentions user

• #hashtag

  - Contains hashtag

• "exact phrase"

  - Exact match

• has:media

  - Contains media

• has:links

  - Contains links

• is:retweet

  /

  -is:retweet

  - Include/exclude retweets

• is:reply

  /

  -is:reply

  - Include/exclude replies

• lang:en

  - Language filter

Combinators:

• Space for AND

• OR

  for either condition

• -

  prefix for NOT
• Parentheses for grouping

Media Upload Flow

1. Upload media with TWITTER_UPLOAD_MEDIA (images) or TWITTER_UPLOAD_LARGE_MEDIA (video/GIF)
2. Get media_id from response
3. Pass media_id as string in media__media_ids array to TWITTER_CREATION_OF_A_POST

Imported: Known Pitfalls

Character Limits:

• Standard posts: 280 weighted characters
• Some Unicode characters count as more than 1
• URLs are shortened and count as fixed length (23 characters)

Rate Limits:

• Vary significantly by access tier (Free, Basic, Pro, Enterprise)
• Free tier: very limited (e.g., 1,500 posts/month)
• Check

  x-rate-limit-remaining

  header in responses

Idempotency:

• Post creation is NOT idempotent; duplicate posts will be created on retry
• Implement deduplication logic for automated posting

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.