venly-automation

Automate Venly operations through the Rube MCP gateway using structured tool discovery and execution.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill venly-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: venly-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/venly-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill venly-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of manually navigating Venly's API by providing a standardized, agent-driven workflow for discovering and executing blockchain-related operations.

Core Features & Use Cases

  • Dynamic Tool Discovery: Automatically fetches current Venly tool schemas and input requirements via Rube MCP.
  • Connection Management: Handles secure authentication and session state for Venly toolkits.
  • Use Case: A developer needs to perform bulk wallet operations or asset transfers; this Skill allows the agent to discover the exact required parameters and execute the transaction safely within a managed session.

Quick Start

Call the Rube MCP to search for Venly tools and execute the required operation using the discovered schema.

Frequently Asked Questions about venly-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Venly tools?

Call the RUBE_SEARCH_TOOLS function with a query related to your specific Venly task. This returns the current tool slugs, input schemas, and execution plans required for your operation.

How do I verify my Venly connection status?

Use the RUBE_MANAGE_CONNECTIONS tool with the 'venly' toolkit argument. The response will indicate if your connection is ACTIVE or if you need to follow an authentication link.

Can I hardcode tool slugs for Venly operations?

No, you should never hardcode tool slugs or arguments. Tool schemas change frequently, so always call RUBE_SEARCH_TOOLS first to ensure you are using the most current and valid schema.

What is the purpose of the memory parameter in RUBE_MULTI_EXECUTE_TOOL?

The memory parameter maintains state across tool calls within a workflow. Always include it in your execution calls, even if it is an empty object, to ensure compatibility with the Rube MCP execution engine.