How do I ensure tool schemas are up to date?

Always run RUBE_SEARCH_TOOLS before executing; tool slugs and arguments can change, so avoid hardcoding.

What if the Y Gy connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then retry until ACTIVE.

Is an API key required to use MCP?

No API keys are needed; simply add the MCP endpoint (https://rube.app/mcp) in your client configuration.

y-gy-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Y Gy Automation via Rube MCP

Automate Y Gy operations through Composio's Y Gy toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/y_gy

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Y Gy operations using Composio's Y Gy toolkit through the Rube MCP bridge. The workflow focuses on discovering current tool schemas, establishing an active Y Gy connection, and executing tools safely with the validated schemas.

How This Skill Works

The system first uses RUBE_SEARCH_TOOLS to fetch up-to-date Y Gy tool schemas. Next, it establishes or verifies an active connection to the y_gy toolkit via RUBE_MANAGE_CONNECTIONS. Finally, it runs the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and arguments, always including a memory object and reusing a session_id for continuity.

When to Use It

When automating a routine Y Gy operation using the latest tool schemas
When you need to validate tool availability before running a workflow
When you must ensure the Y Gy connection is ACTIVE before execution
When you want to reuse a session across steps within a workflow
When handling multiple tools or paginated results during discovery

Quick Start

Step 1: Add the MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
Step 2: Connect to the Y Gy toolkit with RUBE_MANAGE_CONNECTIONS (toolkit: y_gy) and ensure ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with memory: {} and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to fetch current tool schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results (no hardcoding)
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and generate new ones only for new tasks

Example Use Cases

Discover available Y Gy tools with RUBE_SEARCH_TOOLS and execute a TOOL_SLUG_FROM_SEARCH with proper arguments
Connect to the y_gy toolkit via RUBE_MANAGE_CONNECTIONS and run a selected tool in a managed session
Perform multiple tools in one workflow using RUBE_MULTI_EXECUTE_TOOL and a shared session_id
Use RUBE_REMOTE_WORKBENCH to run a composio tool in bulk operations
Retrieve the full tool schema with RUBE_GET_TOOL_SCHEMAS before integrating into an automation

Frequently Asked Questions

Add this skill to your agents