playbooks

home / skills / composiohq / awesome-claude-skills / y-gy-automation

y-gy-automation skill

/y-gy-automation

This skill automates Y Gy tasks through Rube MCP, always discovering current tool schemas before execution to ensure accurate tool selection.

npx playbooks add skill composiohq/awesome-claude-skills --skill y-gy-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.8 KB
---
name: y-gy-automation
description: "Automate Y Gy tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# 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](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `y_gy`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Y Gy tasks by orchestrating Composio's Y Gy toolkit through the Rube MCP bridge. It guides tool discovery, connection management, and schema-compliant execution so workflows run reliably. Follow the prescribed search-first pattern to avoid schema drift and connection errors.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover available Y Gy tools and their input schemas, then verifies or establishes a toolkit connection via RUBE_MANAGE_CONNECTIONS. After confirming an ACTIVE connection and reusing a session ID, it executes operations with RUBE_MULTI_EXECUTE_TOOL (including a memory object) or runs bulk jobs via RUBE_REMOTE_WORKBENCH. Always consult returned schemas and pagination tokens before building arguments.

When to use it

  • Automating recurrent Y Gy operations that require Composio toolkit actions.
  • Running multi-step flows that must discover available tools dynamically.
  • Executing bulk or remote workbench jobs against Y Gy toolchains.
  • Integrating Y Gy tasks into broader agent workflows where schema stability matters.
  • When you need safe, repeatable orchestration that checks connections first.

Best practices

  • Always run RUBE_SEARCH_TOOLS first; never hardcode tool slugs or argument shapes.
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for toolkit 'y_gy' before executing tools.
  • Include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls to satisfy the API.
  • Reuse session IDs for a single workflow and generate new sessions for distinct workflows.
  • Handle pagination: inspect response tokens and fetch additional pages until complete.

Example use cases

  • Discover available Y Gy APIs and execute a single tool call with schema-validated inputs.
  • Run a multi-step automation that chains several Y Gy tools using RUBE_MULTI_EXECUTE_TOOL.
  • Perform bulk processing of records via RUBE_REMOTE_WORKBENCH and run_composio_tool().
  • Automate connection setup by directing users to auth links returned from RUBE_MANAGE_CONNECTIONS.
  • Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building complex payloads.

FAQ

Do I need an API key to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration.

What if a tool schema changes?

Run RUBE_SEARCH_TOOLS again to get the current schema and update your arguments to match exact field names and types.

Can I skip the memory parameter?

No. RUBE_MULTI_EXECUTE_TOOL expects a memory field; provide {} if you have no state to pass.