Do I always need to search tools before each workflow?

Yes. Tool schemas can change; RUBE_SEARCH_TOOLS returns current tool slugs, schemas, and execution plans.

How do I ensure Zylvie is connected and ready?

Call RUBE_MANAGE_CONNECTIONS with toolkit zylvie and confirm the session status is ACTIVE before executing tools.

What should I include in memory when executing tools?

Pass a non-null memory object (even if empty {}) in RUBE_MULTI_EXECUTE_TOOL to satisfy the API and support session data.

zylvie-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Zylvie Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/zylvie

Prerequisites

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

Step 2: Check Connection

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

Overview

Zylvie Automation via Rube MCP orchestrates Zylvie operations using Composio's toolkit. It requires discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows to avoid outdated slugs and arguments, and ensures secure, connected automation through RUBE_MANAGE_CONNECTIONS.

How This Skill Works

Connect Rube MCP to the Zylvie toolkit, verify an ACTIVE connection, then discover available tools with RUBE_SEARCH_TOOLS. Use the returned tool slugs and schemas to execute workflows via RUBE_MULTI_EXECUTE_TOOL, passing the exact field names and memory payload per the discovered schema.

When to Use It

When automating a Zylvie task end-to-end and need up-to-date tool schemas
When validating connectivity to Zylvie before running a workflow
When reusing a session to chain multiple Zylvie operations in a single run
When performing bulk or batch Zylvie actions via RUBE_REMOTE_WORKBENCH
When debugging tool discovery and schema changes (including pagination) before execution

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case Zylvie operations to discover available tools and schemas
Step 2: RUBE_MANAGE_CONNECTIONS to ensure the zylvie toolkit connection is ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and memory: {} using the discovered arguments

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE for the zylvie toolkit before execution
Use exact field names and types from the search results; do not hardcode slugs or args
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow to maintain continuity, but generate new sessions for new workflows

Example Use Cases

Automate a Zylvie operation by discovering tools, validating the connection, and executing TOOL_SLUG with proper arguments
Batch multiple Zylvie actions using RUBE_REMOTE_WORKBENCH and run_composio_tool()
Update and adapt to schema changes by re-searching tools before each workflow
Resume a workflow after a failed step by reusing the session_id and re-checking the connection
Handle tool pagination by continuing tool discovery until all pages are retrieved

Frequently Asked Questions

Add this skill to your agents