Do I need an active Venly connection to run workflows?

Yes. You must have an ACTIVE Venly connection configured via RUBE_MANAGE_CONNECTIONS with the venly toolkit before executing tools.

How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS first; tool slugs and input fields come from the latest schemas.

What should I do if tool schemas change mid-workflow?

Fetch fresh schemas with RUBE_SEARCH_TOOLS, avoid hardcoding slugs, and adapt the workflow to the new input fields; reuse session IDs where possible.

venly-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Venly Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/venly

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Venly operations through Composio's Venly toolkit using Rube MCP. This skill relies on discovering current tool schemas with RUBE_SEARCH_TOOLS and maintaining an ACTIVE Venly connection via RUBE_MANAGE_CONNECTIONS before executing workflows. It avoids hardcoding tool slugs by always querying the latest schemas.

How This Skill Works

First, discover available Venly tools with RUBE_SEARCH_TOOLS to get up-to-date slugs and input schemas. Next, ensure the Venly connection is ACTIVE using RUBE_MANAGE_CONNECTIONS. Finally, execute a tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug and exact schema fields, memory, and session_id.

When to Use It

When you need to automate Venly operations and keep up with schema changes by always querying tool schemas first.
When you must verify and establish an ACTIVE Venly connection before running workflows.
When orchestrating a sequence of Venly tasks in a single session using the discovered tool slugs.
When you want to bulk-run Venly tools or integrate with Composio's broader toolset.
When reusing session IDs to maintain context across related Venly workflows.

Quick Start

Step 1: Add Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS is available and returns Venly tool slugs and schemas.
Step 3: Run a small workflow: discover tools, check connection, and execute a tool with memory and a session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS before selecting tools to ensure current schemas.
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before execution.
Use the exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow and create new sessions only for separate workflows.

Example Use Cases

Automate a Venly token transfer by discovering the TOOL_SLUG and required arguments, then executing with a single session.
Run a sequence of Venly wallet checks and updates within one session using RUBE_MULTI_EXECUTE_TOOL.
Adapt automation after a tool schema update by re-searching tools and re-running a workflow with new slugs.
Connect Venly toolkit and perform bulk operations via RUBE_REMOTE_WORKBENCH with run_composio_tool.
Monitor and log tool execution outcomes for auditing by capturing session_id and tool responses.

Frequently Asked Questions

Add this skill to your agents