corrently-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/corrently-automation --openclawCorrently Automation via Rube MCP
Automate Corrently operations through Composio's Corrently toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/corrently
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Corrently connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcorrently - 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 toolkitcorrently - 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: "Corrently 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 Corrently task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["corrently"]
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 Corrently-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit corrently |
| 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/corrently-automation/SKILL.mdView on GitHub Overview
Automate Corrently operations through Composio’s Corrently toolkit using Rube MCP. The process emphasizes discovering the latest tool schemas first via RUBE_SEARCH_TOOLS, establishing an ACTIVE Corrently connection with RUBE_MANAGE_CONNECTIONS, and executing tools with RUBE_MULTI_EXECUTE_TOOL using schema compliant arguments.
How This Skill Works
You add the Rube MCP endpoint, verify availability with RUBE_SEARCH_TOOLS, then establish a Corrently connection using RUBE_MANAGE_CONNECTIONS. Once connected, you run a discovered tool via RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments, memory, and a session_id to complete the workflow.
When to Use It
- When you are starting an automated Corrently workflow and need the latest tool schemas
- When you must verify that the Corrently connection is ACTIVE before executing any tools
- When chaining multiple Corrently tools in a single session within a workflow
- When performing bulk Corrently tasks using RUBE_REMOTE_WORKBENCH with run_composio_tool
- When updating scripts to schema changes by re searching tools instead of hardcoding slugs
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
- Step 2: Verify RUBE MCP availability by running RUBE_SEARCH_TOOLS and reviewing Corrently tool schemas
- Step 3: Manage the Corrently connection with RUBE_MANAGE_CONNECTIONS and execute tools with RUBE_MULTI_EXECUTE_TOOL using a session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current schemas
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before execution
- Use exact field names and types from the search results
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and generate new ones for new workflows
Example Use Cases
- A cron job automatically discovers Corrently tools with RUBE_SEARCH_TOOLS and executes a daily operation using a discovered tool slug
- A multi-step workflow validates the Corrently connection is ACTIVE and then runs two tools sequentially in the same session
- A script adapts to tool schema changes by re searching tools rather than hardcoding slugs
- A bulk operation performs multiple Corrently tasks via RUBE_REMOTE_WORKBENCH with run_composio_tool
- An automation ensures memory is always included in RUBE_MULTI_EXECUTE_TOOL calls even when no extra data is passed
