home / skills / composiohq / awesome-claude-skills / zylvie-automation

zylvie-automation skill

safe

/zylvie-automation

This skill automates Zylvie tasks via Rube MCP, always sourcing up-to-date tool schemas before execution to ensure accurate, schema-compliant workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill zylvie-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: zylvie-automation
description: "Automate Zylvie tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Zylvie Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/zylvie](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zylvie`
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: "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](https://composio.dev)*

Overview

This skill automates Zylvie tasks through Composio’s Rube MCP (Composio toolkit "zylvie"). It guides discovery, connection management, and execution of Zylvie tools while enforcing schema compliance and session management. The workflow prioritizes calling the RUBE_SEARCH_TOOLS endpoint first to obtain current tool schemas and recommended arguments.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available Zylvie tools, their slugs, input schemas, and execution plans. It then verifies or establishes an active Zylvie connection via RUBE_MANAGE_CONNECTIONS and runs selected tools through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk operations), always including a memory object and reusing session IDs for the workflow. It enforces schema compliance, pagination handling, and connection status checks before any execution.

When to use it

Automating repeated Zylvie operations via Composio/Rube MCP
Orchestrating multi-step Zylvie workflows that require tool discovery and schema validation
Running bulk Zylvie tasks using remote workbench or multi-execute calls
Integrating Zylvie actions into broader agent workflows where tool schemas may change
When you need reliable session and connection management for Zylvie tool calls

Best practices

Always call RUBE_SEARCH_TOOLS first — do not hardcode tool slugs or arguments
Confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE for the zylvie toolkit before executing tools
Pass an explicit memory object (can be {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session_id across related steps; generate a new session for independent workflows
Respect the exact field names and types returned by search results and follow pagination tokens until complete

Example use cases

Discover available Zylvie endpoints for a given use case, then run a specific tool with schema-compliant args
Automate a multi-step Zylvie pipeline by sequencing RUBE_SEARCH_TOOLS → RUBE_MANAGE_CONNECTIONS → RUBE_MULTI_EXECUTE_TOOL
Perform bulk operations across many items using RUBE_REMOTE_WORKBENCH and run_composio_tool()
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building a higher-level orchestration or UI integration

FAQ

What must I call first when automating Zylvie tasks?

Always call RUBE_SEARCH_TOOLS first to retrieve current tool slugs, input schemas, and recommended execution plans.

What if RUBE_MANAGE_CONNECTIONS shows the connection as inactive?

Follow the auth link returned by the manage connections response to complete setup; confirm the status becomes ACTIVE before running tools.