What is required to start Geokeo automation?

A connected Rube MCP, an active Geokeo connection (RUBE_MANAGE_CONNECTIONS with toolkit geokeo), and the ability to call RUBE_SEARCH_TOOLS to fetch current tool schemas.

Why always search tools first?

Tool schemas change over time. Always calling RUBE_SEARCH_TOOLS prevents hardcoding slugs or arguments that may be outdated.

How do I verify readiness before running?

Ensure RUBE_MANAGE_CONNECTIONS reports ACTIVE for the geokeo toolkit and that you have a valid session_id before executing tools.

geokeo-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/geokeo-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Geokeo Automation via Rube MCP

Automate Geokeo operations through Composio's Geokeo toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/geokeo

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Geokeo connection via RUBE_MANAGE_CONNECTIONS with toolkit geokeo
Always call RUBE_SEARCH_TOOLS first 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_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit geokeo
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: "Geokeo 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 Geokeo task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["geokeo"]
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_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, 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 Geokeo-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `geokeo`
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/geokeo-automation/SKILL.mdView on GitHub

Overview

Geokeo automation enables running Geokeo operations through Composio's Geokeo toolkit powered by Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing, to avoid deprecated slugs and arguments.

How This Skill Works

The integration uses RUBE MCP to discover available Geokeo tool slugs and input schemas, then validates that the Geokeo connection is ACTIVE via RUBE_MANAGE_CONNECTIONS. Once ready, you execute the selected tool with RUBE_MULTI_EXECUTE_TOOL, passing a memory payload and session_id to enable workflow continuity.

When to Use It

When you need to locate current Geokeo tools and schemas before running tasks
When setting up a new Geokeo workflow via Rube MCP
When you must verify ACTIVE Geokeo connection before execution
When chaining multiple Geokeo tools in a single session for end-to-end processing
When troubleshooting failures caused by outdated tool slugs or schemas

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
Step 2: Connect Geokeo with RUBE_MANAGE_CONNECTIONS (toolkit: geokeo) and ensure ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run RUBE_MULTI_EXECUTE_TOOL with memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Check RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
Use exact field names and types from the tool schemas
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

Discover a Geokeo operation with RUBE_SEARCH_TOOLS, then run it using RUBE_MULTI_EXECUTE_TOOL with the correct tool_slug and input args.
Set up a new Geokeo workflow by connecting via RUBE_MANAGE_CONNECTIONS, validating ACTIVE, then executing a sequence of tools in a single session.
Chain multiple Geokeo tools to perform data extraction, transformation, and loading within one workflow, reusing the same session_id.
Regularly refresh tool schemas by re-running RUBE_SEARCH_TOOLS before updating any hardcoded slugs or arguments.
Execute bulk Geokeo tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool() to process multiple items efficiently.

Frequently Asked Questions

Add this skill to your agents