keen-io-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/keen-io-automation --openclawKeen IO Automation via Rube MCP
Automate Keen IO operations through Composio's Keen IO toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/keen_io
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Keen IO connection via
RUBE_MANAGE_CONNECTIONSwith toolkitkeen_io - 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 toolkitkeen_io - 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: "Keen IO 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 Keen IO task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["keen_io"]
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 Keen IO-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit keen_io |
| 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/keen-io-automation/SKILL.mdView on GitHub Overview
Automates Keen IO operations through Composio's Keen IO toolkit using Rube MCP. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS and validating ACTIVE connections via RUBE_MANAGE_CONNECTIONS before execution. This approach prevents hardcoded tool slugs and arguments by always using live schemas.
How This Skill Works
Technically, you connect Rube MCP to Keen IO, verify tool schemas via RUBE_SEARCH_TOOLS, then establish an active toolkit connection with RUBE_MANAGE_CONNECTIONS. You discover tools for a Keen IO use case, check the session, and execute them with RUBE_MULTI_EXECUTE_TOOL, passing the discovered tool slug, args, and memory. Remember to include memory even if empty and reuse sessions when appropriate.
When to Use It
- You need to automate Keen IO tasks end-to-end using up-to-date tool schemas.
- You must verify or refresh tool slugs and input schemas before execution.
- You require an ACTIVE Keen IO connection via RUBE_MANAGE_CONNECTIONS.
- You want to run a discovered Keen IO tool with RUBE_MULTI_EXECUTE_TOOL including the correct arguments.
- You want to reuse session IDs within a Keen IO workflow.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Confirm RUBE_SEARCH_TOOLS responds to fetch current Keen IO tool schemas.
- Step 3: Use RUBE_MANAGE_CONNECTIONS to connect the keen_io toolkit and run workflows with RUBE_MULTI_EXECUTE_TOOL.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from search results; do not hardcode slugs or args.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Discover Keen IO tool slugs for a new data ingestion task using RUBE_SEARCH_TOOLS.
- Establish an ACTIVE Keen IO connection via RUBE_MANAGE_CONNECTIONS before running a task.
- Execute a discovered Keen IO operation with RUBE_MULTI_EXECUTE_TOOL using the slug and args from search results.
- Perform bulk Keen IO operations with RUBE_REMOTE_WORKBENCH and run_composio_tool().
- Consult full tool schemas with RUBE_GET_TOOL_SCHEMAS to ensure compatibility before execution.
