Ritekit Automation

What This Skill Does

• This skill automates Ritekit operations using Composio's Ritekit toolkit through Rube MCP.
• It's designed for users who want to streamline social media and SEO tasks within Ritekit.
• The skill requires an active Ritekit connection and utilizes Rube MCP for tool discovery and execution.

When to Use

• Enhance social media posts.
• Find relevant hashtags.
• Analyze hashtag performance.
• Improve SEO with keyword research.
• Get insights on social media trends.
• Schedule social media posts.

Key Features

• Automates Ritekit tasks via Rube MCP.
• Uses Composio's Ritekit toolkit.
• Discovers available tools using RUBE_SEARCH_TOOLS.
• Manages connections with RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.
• Provides setup instructions and known pitfalls.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedRitekit Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ritekit

Prerequisites

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

Setup

• Get Rube MCP: Add https://rube.
• 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 ritekit 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: "Ritekit 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 Ritekit task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["ritekit"] 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