How do I start using this skill?

Add the MCP server, ensure RUBE_SEARCH_TOOLS responds, verify the Geoapify connection via RUBE_MANAGE_CONNECTIONS, then proceed to discover tools and run workflows.

Are API keys required?

No API keys are needed—just add the MCP endpoint and use the toolkit as described.

How can I ensure tool schemas stay up to date?

Always run RUBE_SEARCH_TOOLS first to fetch current schemas and avoid hardcoding tool slugs or argument names; rely on schemaRef and live results.

geoapify-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Geoapify Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/geoapify

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Geoapify connection via RUBE_MANAGE_CONNECTIONS with toolkit geoapify
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 geoapify
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: "Geoapify 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 Geoapify task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["geoapify"]
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 Geoapify-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `geoapify`
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/geoapify-automation/SKILL.mdView on GitHub

Overview

Automate Geoapify operations through Composio's Geoapify toolkit via Rube MCP. It emphasizes discovering current tool schemas first and validating an ACTIVE Geoapify connection before running workflows.

How This Skill Works

Connect to an MCP server and ensure the Geoapify toolkit is ACTIVE. Use RUBE_SEARCH_TOOLS to fetch current tool schemas, select a tool slug, and execute with RUBE_MULTI_EXECUTE_TOOL using the required arguments and a memory payload, reusing the session_id as needed.

When to Use It

Automate recurring Geoapify tasks and keep tool schemas up to date
Set up a new Geoapify workflow and validate the connection before running
Execute multiple Geoapify operations in a single session
Adapt to tool schema changes without hardcoding slugs or arg names
Perform bulk/remote Geoapify operations via RUBE_REMOTE_WORKBENCH

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas are available
Step 3: Discover tools, check ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then execute with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and memory

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results; avoid hardcoding
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call (even if empty)
Reuse session IDs within a workflow and avoid creating new ones unnecessarily

Example Use Cases

Discover Geoapify tooling for a geocoding task and execute with the discovered tool slug and required args
Establish a Geoapify connection and run a routing task after confirming an ACTIVE status
Chain two Geoapify tools in a single session: discovery, then execution
Process paginated Geoapify results by iterating through search responses until complete
Bulk Geoapify operations using RUBE_REMOTE_WORKBENCH and run_composio_tool()

Frequently Asked Questions

Add this skill to your agents