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

SKILL

tomtom-automation

Name: tomtom-automation
Author: Composio

Automate TomTom workflows via Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is primarily a prompt-style usage guide and does not directly require local secrets or include local code execution steps. However, its purpose is to connect to and operate Tomtom tools via Rube MCP/Composio, which brings normal considerations around external connectivity and data flow through an intermediary platform. The high-star open-source GitHub source materially lowers overall risk, so this is better rated as low-to-moderate caution rather than high risk.

CredentialsCaution

The material says there are no local API keys, but it still requires establishing a Tomtom connection via `RUBE_MANAGE_CONNECTIONS` and completing external authorization. This means credentials are not absent; they are handled through the Rube/Composio connection flow. No explicit credential abuse is described, but normal third-party OAuth/connection authorization risk remains.

Network egressCaution

The documentation explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing actions through Composio's Tomtom toolkit, so user requests and related business data will likely transit through Rube/Composio to Tomtom. The endpoint and purpose are declared, making this normal tool egress rather than a red flag, but data does leave the local environment.

Code executionLow risk

Based on the provided material, this skill is a prompt/workflow guide and does not include local scripts, shell commands, or requests for system-level privileges. There is no clear sign of local code execution beyond normal MCP usage instructions.

Data accessCaution

The skill is intended to 'Automate Tomtom operations' and supports tool discovery, connection management, tool execution, and bulk operations. This means its effective data access depends on the authorized Tomtom account and available tools. The material does not indicate local file access, but it may read/write remote business data within granted permissions, which is a normal caution item.

Supply chainLow risk

The source is an open-source GitHub repository with very strong community adoption (~64.9k stars), which supports auditability and source trust. The license and maintenance state are not explicit, and the skill depends on external Rube/Composio services, but the material does not show high-risk red flags such as opaque droppers, unknown download sources, or clearly misleading installation instructions.

Recommendations

Before connecting, verify the data handling, storage, and logging policies of Rube/Composio and Tomtom to avoid sending sensitive business content unnecessarily.
Grant only the minimum Tomtom permissions required, and periodically review or revoke unused authorizations.
Review the tool list and parameter schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid invoking high-impact actions by mistake.
Test bulk or write-oriented workflows in a non-production environment first to reduce the impact of accidental remote changes.

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 "tomtom-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/tomtom-automation/SKILL.md
2. Save it as ~/.claude/skills/tomtom-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Tomtom Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/tomtom

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["tomtom"]
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 Tomtom-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `tomtom`
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 Composio tasks via Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_