geocodio-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/geocodio-automation --openclawGeocodio Automation via Rube MCP
Automate Geocodio operations through Composio's Geocodio toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/geocodio
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Geocodio connection via
RUBE_MANAGE_CONNECTIONSwith toolkitgeocodio - 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 toolkitgeocodio - 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: "Geocodio 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 Geocodio task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["geocodio"]
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 Geocodio-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit geocodio |
| 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/geocodio-automation/SKILL.mdView on GitHub Overview
Automate Geocodio tasks using Composio's Geocodio toolkit via Rube MCP. This skill emphasizes discovering current tool schemas before execution to adapt to changes, avoiding hardcoded slugs. It orchestrates discovery, connection, and execution across Geocodio workflows.
How This Skill Works
Start by calling RUBE_SEARCH_TOOLS to fetch current Geocodio tool schemas. Then verify or establish the Geocodio connection with RUBE_MANAGE_CONNECTIONS and ensure its status is ACTIVE. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and schema-compliant arguments, always including memory and the current session_id.
When to Use It
- When tool schemas change frequently and you can't hardcode tool slugs, requiring dynamic discovery.
- When you want a repeatable Geocodio workflow that can be reused across sessions.
- When you need to verify and establish a Geocodio connection before running tasks.
- When executing tools with dynamic input fields surfaced by discovery results.
- When handling large batches that require pagination-aware retrieval and continued tool discovery.
Quick Start
- Step 1: 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.
- Step 2: Verify RUBE_SEARCH_TOOLS responds and connect to Geocodio with RUBE_MANAGE_CONNECTIONS, ensuring the toolkit is ACTIVE.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, pick a discovered tool_slug, and execute it with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow; generate new ones for new workflows.
Example Use Cases
- Discover the Geocodio batch geocode tool via RUBE_SEARCH_TOOLS and execute it with a list of addresses using RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.
- Establish the Geocodio connection with RUBE_MANAGE_CONNECTIONS and run a geocoding task in a session to process multiple batches.
- Switch between tools as schemas evolve by re-running RUBE_SEARCH_TOOLS and updating the tool_slug used in RUBE_MULTI_EXECUTE_TOOL.
- Handle a long geocoding job by using pagination tokens from the tool responses and continuing to fetch until complete.
- Reuse a single session_id across several geocoding tasks to maintain context and improve performance.
