$ ~/registry/skill/composiohq-composio-skills-mapbox-automation

SKILL

mapbox-automation

Name: mapbox-automation
Author: Composio

Automate Mapbox tasks through Rube MCP for mapping and workflow operations.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt/instruction wrapper with strong GitHub community signals, so the overall risk is not high. However, its real functionality depends on third-party Rube MCP and Composio/Mapbox connections, which introduces remote data flow and delegated account access that should be reviewed carefully.

CredentialsCaution

The material says there is 'no API key', but the README explicitly requires creating a `mapbox` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth-link flow, which implies delegated Mapbox credentials or OAuth sessions handled by Rube/Composio. The skill does not directly request secrets, but third-party managed connections introduce normal credential-boundary concerns.

Network egressCaution

The README instructs users to configure `https://rube.app/mcp` as an MCP server and execute operations through Composio's Mapbox toolkit. This means user instructions, tool arguments, and related business data are expected to be sent to Rube/Composio and may then act on Mapbox. This is network egress consistent with the stated purpose, with no additional unknown endpoints identified in the provided material.

Code executionLow risk

Per the objective checks, this is `prompt-only`: it provides workflow guidance and tool-calling order, with no bundled local executable code, install script, or requirement to start additional local processes. Its execution surface lies primarily in the external MCP tools rather than in the skill text itself.

Data accessCaution

The material does not show any ability to read local files or system data, but it is designed to automate Mapbox operations through a connected toolkit and remote workflows. Therefore, its main data-access scope is authorized Mapbox resources plus task parameters sent to the MCP service; this is function-related access, but the connected account should still be reviewed under least-privilege principles.

Supply chainCaution

Positive signals include an open-source GitHub source and high community star count, which materially reduce supply-chain risk. However, the license is undeclared, maintenance status is unknown, and the actual functionality depends on third-party online services (Rube/Composio) whose server-side behavior cannot be fully audited from this repository, so 'caution' is more appropriate than a fully low-risk rating.

Recommendations

Before connecting, verify the data-handling terms for `rube.app`, Composio, and Mapbox, and confirm what request content may be logged or forwarded by third parties.
Use a least-privilege Mapbox account for the connection, avoiding unrelated write scopes or production permissions.
Validate `RUBE_SEARCH_TOOLS`, the authorization flow, and actual execution behavior in a test project/account before using it on production resources.
Keep session and action audit records, and regularly review and revoke Rube/Composio connections that are no longer needed.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "mapbox-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/mapbox-automation/SKILL.md
2. Save it as ~/.claude/skills/mapbox-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Radar tasks and workflows through Rube MCP integrations.

ComposioGet→

$ loading_