venly-automation
Facilitates automated interaction with Venly services via Rube MCP.
Install
mkdir -p .claude/skills/venly-automation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11032" && unzip -o skill.zip -d .claude/skills/venly-automation && rm skill.zipInstalls to .claude/skills/venly-automation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Automate Venly tasks via Rube MCP (Composio). Always search tools first for current schemas.Key capabilities
- →Discover Venly tools
- →Manage Venly connections
- →Execute blockchain operations
- →Automate Venly workflows
How it works
It uses the Rube MCP to search for available tools, verify connection status, and execute schema-compliant Venly operations.
Inputs & outputs
When to use venly-automation
- →Trigger blockchain actions
- →Automate venly wallet operations
- →Fetch status for venly transactions
About this skill
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_CONNECTIONSwith toolkitvenly - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitvenly - 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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
When not to use it
- →When the Rube MCP is not connected
- →When the Venly connection is not active
Prerequisites
Limitations
- →Requires active Venly connection
How it compares
It provides a standardized, schema-aware approach to Venly automation via Composio toolkits.
Compared to similar skills
venly-automation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| venly-automation (this skill) | 0 | 3mo | No flags | Intermediate |
| mixpanel-automation | 0 | 5mo | No flags | Intermediate |
| linkup-automation | 0 | 3mo | No flags | Intermediate |
| 0 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by onfire7777
View all by onfire7777 →You might also like
mixpanel-automation
mk-knight23
Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.
linkup-automation
manu14357
Automate Linkup tasks via Rube MCP (Composio). Always search tools first for current schemas.
FISCFED9
Integracao completa com Instagram via Graph API. Publicacao, analytics, comentarios, DMs, hashtags, agendamento, templates e gestao de contas Business/Creator.
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
n8n-workflow-patterns
czlonkowski
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.