PromptShop

Starton Automation

automates Starton operations using the Composio Starton toolkit via Rube MCP.

Install

npx promptshop add starton-automation

Details

What This Skill Does

This skill automates Starton operations using the Composio Starton toolkit via Rube MCP. It's designed for users who need to manage and automate blockchain infrastructure and deployments through Starton. The skill ensures proper setup, tool discovery, and execution while adhering to Starton's schema requirements.

When to Use

  • Automate blockchain deployments.
  • Manage and monitor blockchain nodes.
  • Trigger actions based on blockchain events.
  • Schedule recurring blockchain tasks.
  • Verify Starton connection status.
  • Discover available Starton tools.

Key Features

  • Automates Starton operations via Rube MCP.
  • Discovers available tools using RUBE_SEARCH_TOOLS.
  • Manages connections using RUBE_MANAGE_CONNECTIONS.
  • Executes tools using RUBE_MULTI_EXECUTE_TOOL.
  • Provides setup instructions and prerequisites.
  • Highlights common pitfalls and how to avoid them.

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Starton-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit starton
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schema Ref