PromptShop

Opencage Automation

Geocode addresses in bulk. Reverse geocode coordinates. Find place details by ID. Automate location data enrichment. Monitor geocoding usage. Integrate locat...

Install

npx promptshop add opencage-automation

Details

What This Skill Does

When to Use

Geocode addresses in bulk. Reverse geocode coordinates. Find place details by ID. Automate location data enrichment. Monitor geocoding usage. Integrate location data into applications.

Key Features

Connects to Opencage via Rube MCP. Discovers available tools dynamically. Manages Opencage connections. Executes Opencage tools with schema validation. Provides a structured workflow pattern. Offers guidance on avoiding common pitfalls.

Manual Installation

  • Manual installation
  • View Full Skill Content
  • The complete markdown content that gets installed
  • Opencage Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/opencage

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Opencage connection via RUBE_MANAGE_CONNECTIONS with toolkit opencage Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit opencage 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: "Opencage 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 Opencage task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["opencage"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", }] memory: {} session_id: "your_session_id"

Known Pitfalls

Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Opencage-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit opencage
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef
  • Powered by Composio
  • Opencage Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/opencage

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Opencage connection via RUBE_MANAGE_CONNECTIONS with toolkit opencage Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit opencage 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: "Opencage 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 Opencage task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["opencage"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", }] memory: {} session_id: "your_session_id"

Known Pitfalls

Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Opencage-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit opencage
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef