Do I need API keys to use mapbox-automation?

No API keys needed — add the MCP endpoint and ensure the Mapbox connection is established via RUBE_MANAGE_CONNECTIONS.

How do I ensure tool schemas stay up to date?

Always run RUBE_SEARCH_TOOLS first; tool slugs and argument schemas come from the current results and may change.

What if the tool execution fails due to incorrect arguments?

Review the exact field names and types from the search results, adjust your arguments accordingly, and retry with the updated payload.

mapbox-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Mapbox Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mapbox

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Mapbox operations through Composio's Mapbox toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS and ensuring an ACTIVE Mapbox connection before workflow execution.

How This Skill Works

It discovers available tools via RUBE_SEARCH_TOOLS, then checks the Mapbox connection with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id.

When to Use It

Starting a Mapbox workflow and discovering current tool schemas with RUBE_SEARCH_TOOLS
Verifying and establishing an ACTIVE Mapbox connection via RUBE_MANAGE_CONNECTIONS before running tools
Executing a discovered tool using RUBE_MULTI_EXECUTE_TOOL with correct tool_slug and arguments
Handling large tool sets or paginated tool lists through RUBE_SEARCH_TOOLS results
Preparing new Mapbox workflows by managing session IDs and avoiding stale sessions

Quick Start

Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Mapbox operations"}]
Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["mapbox"] and session_id as needed
Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, arguments per schema, and memory: {}

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Check connection status with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE
Use exact field names and types from search results; don't hardcode slugs/args
Include memory in every RUBE_MULTI_EXECUTE_TOOL call (even if empty {})
Reuse session IDs within a workflow; generate a new one for new workflows; handle pagination

Example Use Cases

Automate a tileset update: discover tools, connect, then execute a tileset-update tool with appropriate args
Batch geocoding: locate geocode tool, verify connection, run multiple tool invocations with memory state
Mapbox data validation: discover validation tool, run with sample payload and store results in memory
Automated style updates: discover map style tools, execute style apply tool with required fields
Pipelines with pagination: fetch tools with RUBE_SEARCH_TOOLS and iterate through pages until complete

Frequently Asked Questions

Add this skill to your agents