home / skills / composiohq / awesome-claude-skills / mapbox-automation

mapbox-automation skill

safe

/mapbox-automation

This skill automates Mapbox tasks via Rube MCP, discovering tools first and executing schema-compliant actions to streamline workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill mapbox-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.8 KB

---
name: mapbox-automation
description: "Automate Mapbox tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Mapbox Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/mapbox](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mapbox`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Mapbox tasks through Composio’s Mapbox toolkit using Rube MCP. It provides a repeatable pattern for discovering tools, validating connections, and executing Mapbox operations programmatically. The skill emphasizes always searching for current tool schemas before running any actions.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available Mapbox tool slugs and their input schemas. It then validates the Mapbox connection via RUBE_MANAGE_CONNECTIONS, ensuring the connection status is ACTIVE. Finally it runs one or more toolkit operations using RUBE_MULTI_EXECUTE_TOOL (including a memory parameter) or RUBE_REMOTE_WORKBENCH for bulk tasks, following the schema returned by the search.

When to use it

Automate repetitive Mapbox operations (style updates, uploads, dataset tasks).
Before running any Mapbox toolkit calls to avoid schema mismatches.
When orchestrating multi-step Mapbox workflows that require connection checks and session reuse.
For bulk or batched Mapbox tasks using remote workbench execution.
When integrating Mapbox operations into Claude AI workflows via Rube MCP.

Best practices

Always call RUBE_SEARCH_TOOLS first and use the returned schema and tool_slug—do not hardcode fields.
Verify the Mapbox connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before executing tools.
Include a memory object (even empty) in RUBE_MULTI_EXECUTE_TOOL calls and reuse session_id within a workflow.
Respect exact field names and types from the tool schema; validate inputs against schemaRef when available.
Handle pagination tokens in responses and iterate until results are complete.

Example use cases

Upload and publish Mapbox tilesets programmatically by discovering the upload tool and executing it with the schema-compliant arguments.
Batch-update map styles across multiple projects using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH for parallel runs.
Create or update datasets via discovered dataset management tools, validating connection status first.
Automate link-based authentication flows: trigger RUBE_MANAGE_CONNECTIONS, follow the returned auth link, then confirm ACTIVE status before work.
Fetch full tool schema via RUBE_GET_TOOL_SCHEMAS before building client-side form inputs or validation logic.

FAQ

Do I need API keys to use Rube MCP with this skill?

No API keys are required to add the Rube MCP endpoint. Authentication for Mapbox is handled via RUBE_MANAGE_CONNECTIONS and the returned auth flow if needed.

What do I do if a tool schema changes mid-workflow?

Stop execution, re-run RUBE_SEARCH_TOOLS to fetch the updated schema, adjust your arguments to match the new schema, and then continue with a fresh session_id if appropriate.