modelry-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/modelry-automation --openclawModelry Automation via Rube MCP
Automate Modelry operations through Composio's Modelry toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/modelry
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Modelry connection via
RUBE_MANAGE_CONNECTIONSwith toolkitmodelry - 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 toolkitmodelry - 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: "Modelry 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 Modelry task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["modelry"]
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 Modelry-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit modelry |
| 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/modelry-automation/SKILL.mdView on GitHub Overview
Automate Modelry operations through Composio's Rube MCP toolkit. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before every run, and ensuring an ACTIVE Modelry connection via RUBE_MANAGE_CONNECTIONS. This keeps tool usage up to date and execution reliable.
How This Skill Works
Connect Rube MCP by adding the MCP endpoint. Use RUBE_SEARCH_TOOLS to fetch available Modelry tools and their input schemas. When ready, verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then execute a selected tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered tool_slug, proper arguments, memory, and session_id.
When to Use It
- Starting a new Modelry workflow: always search tools first to get current schemas.
- Automating a sequence of Modelry tasks in a session: reuse session_id to maintain context.
- Before any execution, ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
- Handling tool schema changes: re-fetch schemas rather than hardcoding slugs.
- Bulk operations or batch runs using RUBE_REMOTE_WORKBENCH or multi-execute patterns.
Quick Start
- Step 1: Verify RUBE_SEARCH_TOOLS responds and fetch tool schemas.
- Step 2: Connect to Modelry via RUBE_MANAGE_CONNECTIONS and ensure ACTIVE.
- Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug, correct arguments, memory, and an active session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before any run to grab current tool slugs and schemas.
- Confirm RUBE_MANAGE_CONNECTIONS status is ACTIVE before execution.
- Use exact field names and types from the search results; avoid hardcoding.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty).
- Reuse session IDs within a workflow, but generate new IDs for new workflows.
Example Use Cases
- Discover tools for a specific Modelry task and execute the chosen tool.
- Establish an ACTIVE connection and run a tool with discovered input args.
- Continue a long-running workflow by reusing a session_id across steps.
- Update a workflow after tool schemas change by re-running RUBE_SEARCH_TOOLS.
- Perform a bulk operation using RUBE_REMOTE_WORKBENCH to run multiple tools.
