What is Ayrshare Automation via Rube MCP?

It is automating Ayrshare tasks through Composio's Ayrshare toolkit using the Rube MCP workflow engine.

Do I need API keys for Ayrshare to use this skill?

No API keys are needed for MCP. You connect via RUBE_MANAGE_CONNECTIONS with the Ayrshare toolkit, and rely on RUBE_SEARCH_TOOLS for current schemas.

How should I handle changing tool schemas?

Always call RUBE_SEARCH_TOOLS before running; do not hardcode tool slugs or arguments. Use the input schema provided by the search results and include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls.

ayrshare-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/ayrshare-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Ayrshare Automation via Rube MCP

Automate Ayrshare operations through Composio's Ayrshare toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/ayrshare

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Ayrshare connection via RUBE_MANAGE_CONNECTIONS with toolkit ayrshare
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit ayrshare
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Ayrshare operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Ayrshare task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ayrshare"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Ayrshare-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ayrshare`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/ayrshare-automation/SKILL.mdView on GitHub

Overview

Ayrshare Automation via Rube MCP lets you orchestrate Ayrshare operations through Composio's Ayrshare toolkit using the Rube MCP workflow engine. It relies on dynamic tool schemas discovered at runtime, so always call RUBE_SEARCH_TOOLS first. Set up a active Ayrshare connection and verify status before running any workflows.

How This Skill Works

Discover available Ayrshare tool slugs and input schemas with RUBE_SEARCH_TOOLS. Validate an ACTIVE connection using RUBE_MANAGE_CONNECTIONS. Execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL with memory and session_id, optionally fetching full schemas with RUBE_GET_TOOL_SCHEMAS. This pattern ensures you adapt to schema changes and maintain proper session management.

When to Use It

When you need to run an Ayrshare operation end-to-end from discovery to execution within a single session
When tool schemas may change and you must fetch current slugs and input fields before running
When you must ensure the Ayrshare connection remains ACTIVE prior to executing workflows
When performing bulk Ayrshare tasks, potentially via RUBE_REMOTE_WORKBENCH
When reusing a session across multiple Ayrshare tasks within one workflow

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'ayrshare' and complete auth if prompted; ensure ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then execute a tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id

Best Practices

Always search first: use RUBE_SEARCH_TOOLS to get current tool schemas
Check connection: verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Schema compliance: use exact field names and types from search results
Memory parameter: include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

Example 1: Discover an Ayrshare tool to schedule a post and execute it with a live session
Example 2: Retrieve engagement analytics via a discovered tool and export results to a report
Example 3: Perform bulk Ayrshare operations using RUBE_REMOTE_WORKBENCH and run multiple tools
Example 4: Validate ACTIVE Ayrshare connection and initiate a campaign workflow
Example 5: Chain multiple Ayrshare tasks by reusing a session across steps

Frequently Asked Questions

Add this skill to your agents