Skip to content
TrustedSkillsbeta
Back to all skills

Mapbox Google Maps Migration

Official
mapbox·vlatest·database·MIT

Seamlessly migrate Mapbox data and styles to Google Maps, preserving functionality and visual fidelity.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add mapbox/mapbox-agent-skills --skill mapbox-google-maps-migration -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

mapbox

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned mapbox/mapbox-agent-skills at f71cd72b8d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
f71cd72b8d
Manifest
skills/mapbox-google-maps-migration/SKILL.md
Scanned
8 files, 1,363 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill facilitates the migration of mapping applications from Google Maps to Mapbox, streamlining the transition process for developers. It handles the necessary code adjustments and configuration changes required to switch map providers seamlessly within an AI agent's workflow.

When to use it

  • You are building a location-based application currently dependent on Google Maps APIs and want to reduce costs or improve performance with Mapbox.
  • Your project requires switching map tiles, routing engines, or geocoding services from Google to the Mapbox ecosystem.
  • You need automated assistance to refactor legacy code that relies heavily on Google Maps JavaScript API structures.

Key capabilities

  • Identifies existing Google Maps API integrations within a codebase.
  • Generates updated code snippets compatible with Mapbox GL JS.
  • Assists in reconfiguring map layers, markers, and interaction events for the new provider.
  • Provides guidance on migrating geocoding and directions services.

Example prompts

  • "Help me migrate my current Google Maps integration to use Mapbox for better tile customization."
  • "What changes do I need to make to switch from Google Directions API to Mapbox Routing?"
  • "Refactor this code snippet that uses Google Places API to work with Mapbox Geocoding."

Tips & gotchas

Ensure you have a valid Mapbox access token ready before attempting the migration, as the skill will require authentication to generate functional map configurations. Be prepared to manually review generated code for specific business logic that may not translate automatically between the two platforms.