Do I always need to search tools first before executing?

Yes. RUBE_SEARCH_TOOLS fetches current tool schemas, ensuring you use valid tool slugs and arguments.

How do I know the Serply connection is ready?

Call RUBE_MANAGE_CONNECTIONS for the serply toolkit and confirm the status is ACTIVE before running workflows.

What if I have no data for memory?

Include memory in RUBE_MULTI_EXECUTE_TOOL even if it's an empty object to satisfy the required payload shape.

serply-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Serply Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/serply

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Serply operations using Composio's Serply toolkit via Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing any task, ensuring active connections, and correctly passing memory and schema-compliant arguments.

How This Skill Works

You first discover available Serply tools with RUBE_SEARCH_TOOLS, then verify the Serply connection status using RUBE_MANAGE_CONNECTIONS. Once ACTIVE, you execute the chosen tool through RUBE_MULTI_EXECUTE_TOOL, supplying memory and the exact fields from the discovered tool schema.

When to Use It

You need to automate a Serply operation via Rube MCP for repeatable tasks.
Tool schemas may change; you must fetch current schemas with RUBE_SEARCH_TOOLS before running anything.
You want to verify and establish an ACTIVE Serply connection via RUBE_MANAGE_CONNECTIONS before workflows.
You plan to run a sequence of tools in one workflow and need to manage a session with memory across calls.
You are performing bulk operations or inspecting full tool schemas (RUBE_GET_TOOL_SCHEMAS) before execution.

Quick Start

Step 1: Verify Rube MCP is connected and call RUBE_SEARCH_TOOLS to retrieve current Serply tool schemas.
Step 2: Select a tool_slug from the search results that matches your use case.
Step 3: Check the connection status with RUBE_MANAGE_CONNECTIONS and, if ACTIVE, execute the tool with RUBE_MULTI_EXECUTE_TOOL including memory and the discovered arguments.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; don't hardcode slugs or args.
Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens to fetch all tools.

Example Use Cases

Discover a Serply tool with RUBE_SEARCH_TOOLS, pick TOOL_SLUG_FROM_SEARCH, then execute with RUBE_MULTI_EXECUTE_TOOL using discovered arguments and memory.
Establish a Serply connection via RUBE_MANAGE_CONNECTIONS, confirm ACTIVE, then run a sequence of tools in a single session.
Bulk multiple Serply tool executions using RUBE_REMOTE_WORKBENCH with run_composio_tool() on a prepared list of tool_slugs and memory payloads.
Fetch the full set of tool schemas using RUBE_GET_TOOL_SCHEMAS to validate required fields before execution.
Handle a workflow that requires pagination by repeatedly calling RUBE_SEARCH_TOOLS until no tokens remain, then execute the desired tool.

Frequently Asked Questions

Add this skill to your agents