What is the purpose of this skill?

To automate Starton operations through Composio's Rube MCP toolkit, using up-to-date tool schemas.

Do I need to search for schemas every time?

Yes—always call RUBE_SEARCH_TOOLS first to fetch current tool schemas before execution.

What if the connection is not ACTIVE?

Follow the auth link from RUBE_MANAGE_CONNECTIONS to complete setup, then re-run the workflow.

starton-automation

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

Files (1)

SKILL.md

2.9 KB

Starton Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/starton

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Starton connection via RUBE_MANAGE_CONNECTIONS with toolkit starton
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 starton
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: "Starton 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 Starton task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["starton"]
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 Starton-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `starton`
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/starton-automation/SKILL.mdView on GitHub

Overview

This skill automates Starton operations through Composio’s Rube MCP toolkit. It emphasizes discovering current tool schemas before execution and ensuring an ACTIVE Starton connection to run workflows reliably.

How This Skill Works

It first queries available Starton tools via RUBE_SEARCH_TOOLS to fetch current schemas. It then verifies an ACTIVE connection with RUBE_MANAGE_CONNECTIONS and executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and session_id. The approach relies on using exact field names and staying up-to-date with schemas instead of hardcoding slugs.

When to Use It

When you need to perform a Starton operation using the latest tool schemas
When establishing an ACTIVE Starton connection via the toolkit
Before executing a discovered tool, verify schemas and connection
For bulk or multi-tool Starton workflows via Composio
During troubleshooting, re-verify schemas, connection, and memory usage

Quick Start

Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS is responsive
Step 2: Discover tools with RUBE_SEARCH_TOOLS and pick a tool_slug from the results
Step 3: Execute the tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id

Best Practices

Always search for current tool schemas with RUBE_SEARCH_TOOLS before execution
Verify the connection shows ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools
Use exact field names and types from the search results
Include memory in every RUBE_MULTI_EXECUTE_TOOL call (even if empty {})
Reuse session IDs within a workflow and avoid hardcoding slugs or arguments

Example Use Cases

Discover tools for a Starton task via RUBE_SEARCH_TOOLS and execute a disclosed TOOL_SLUG with required arguments
Connect to the Starton toolkit using RUBE_MANAGE_CONNECTIONS and run a single-tool workflow after activation
Run multiple tools in sequence by using RUBE_MULTI_EXECUTE_TOOL with a shared session_id
Bulk operations: use RUBE_REMOTE_WORKBENCH and run_composio_tool() to batch-starton tasks
When tool schemas update, re-run RUBE_SEARCH_TOOLS to refresh tool_slugs and schemas before execution

Frequently Asked Questions

Add this skill to your agents