owl-protocol-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/owl-protocol-automation --openclawOwl Protocol Automation via Rube MCP
Automate Owl Protocol operations through Composio's Owl Protocol toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/owl_protocol
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Owl Protocol connection via
RUBE_MANAGE_CONNECTIONSwith toolkitowl_protocol - 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 toolkitowl_protocol - 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: "Owl Protocol 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 Owl Protocol task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["owl_protocol"]
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 Owl Protocol-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit owl_protocol |
| 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/owl-protocol-automation/SKILL.mdView on GitHub Overview
This skill automates Owl Protocol operations using Composio's Rube MCP toolkit. It emphasizes discovering tool schemas with RUBE_SEARCH_TOOLS before execution, establishing an Owl Protocol connection, and following a repeatable workflow to run tools safely.
How This Skill Works
The agent first calls RUBE_SEARCH_TOOLS to fetch current Owl Protocol tool schemas. It then establishes or verifies a connection via RUBE_MANAGE_CONNECTIONS with the owl_protocol toolkit. Finally, it executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying exact schema fields, and always including memory and a session_id for reliable workflow execution.
When to Use It
- You need to automate a routine Owl Protocol operation and want up-to-date tool schemas.
- You must verify and establish an Owl Protocol connection before running workflows.
- You want to run a sequence of Owl Protocol tools in a single session with proper memory context.
- Tool schemas change frequently and you want to avoid hardcoding tool slugs or arguments.
- You are performing bulk Owl Protocol tasks and want to orchestrate via multi-tool execution
Quick Start
- Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Owl Protocol operations", known_fields: ""}] with a session: {generate_id: true}.
- Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["owl_protocol"], session_id: "your_session_id".
- Step 3: RUBE_MULTI_EXECUTE_TOOL with tools: [{tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/* exact schema args */}}], memory: {}, session_id: "your_session_id".
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the discovered tool schemas.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs for a multi-step workflow and create new sessions for new tasks
Example Use Cases
- Discover Owl Protocol tools, connect with the owl_protocol toolkit, and execute a token transfer tool using the current schema.
- Fetch current tool schemas, establish a persistent session, and run a series of Owl Protocol operations in one workflow.
- When tool slugs change, re-run RUBE_SEARCH_TOOLS before selecting tools to avoid failures.
- Use RUBE_REMOTE_WORKBENCH with run_composio_tool() for bulk execution of multiple Owl Protocol tools.
- If the connection is not ACTIVE, follow the returned auth link and re-check until ACTIVE before proceeding.
