mapbox-google-maps-migration▌
mapbox/mapbox-agent-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Comprehensive guidance for migrating from Google Maps Platform to Mapbox GL JS. Provides API equivalents, pattern translations, and strategies for successful migration.
Mapbox Google Maps Migration Skill
Comprehensive guidance for migrating from Google Maps Platform to Mapbox GL JS. Provides API equivalents, pattern translations, and strategies for successful migration.
Core Philosophy Differences
Google Maps: Imperative & Object-Oriented
- Create objects (Marker, Polygon, etc.)
- Add to map with
.setMap(map) - Update properties with setters
- Heavy reliance on object instances
Mapbox GL JS: Declarative & Data-Driven
- Add data sources
- Define layers (visual representation)
- Style with JSON
- Update data, not object properties
Key Insight: Mapbox treats everything as data + styling, not individual objects.
Map Initialization
Google Maps
const map = new google.maps.Map(document.getElementById('map'), {
center: { lat: 37.7749, lng: -122.4194 },
zoom: 12,
mapTypeId: 'roadmap' // or 'satellite', 'hybrid', 'terrain'
});
Mapbox GL JS
mapboxgl.accessToken = 'YOUR_MAPBOX_TOKEN';
const map = new mapboxgl.Map({
container: 'map',
style: 'mapbox://styles/mapbox/streets-v12', // or satellite-v9, outdoors-v12
center: [-122.4194, 37.7749], // [lng, lat] - note the order!
zoom: 12
});
Key Differences:
- Coordinate order: Google uses
{lat, lng}, Mapbox uses[lng, lat] - Authentication: Google uses API key in script tag, Mapbox uses access token in code
- Styling: Google uses map types, Mapbox uses full style URLs
API Equivalents Reference
Map Methods
| Google Maps | Mapbox GL JS | Notes |
|---|---|---|
map.setCenter(latLng) |
map.setCenter([lng, lat]) |
Coordinate order reversed |
map.getCenter() |
map.getCenter() |
Returns LngLat object |
map.setZoom(zoom) |
map.setZoom(zoom) |
Same behavior |
map.getZoom() |
map.getZoom() |
Same behavior |
map.panTo(latLng) |
map.panTo([lng, lat]) |
Animated pan |
map.fitBounds(bounds) |
map.fitBounds([[lng,lat],[lng,lat]]) |
Different bound format |
map.setMapTypeId(type) |
map.setStyle(styleUrl) |
Completely different approach |
map.getBounds() |
map.getBounds() |
Similar |
Map Events
| Google Maps | Mapbox GL JS | Notes |
|---|---|---|
google.maps.event.addListener(map, 'click', fn) |
map.on('click', fn) |
Simpler syntax |
event.latLng |
event.lngLat |
Event property name |
'center_changed' |
'move' / 'moveend' |
Different event names |
'zoom_changed' |
'zoom' / 'zoomend' |
Different event names |
'bounds_changed' |
'moveend' |
No direct equivalent |
'mousemove' |
'mousemove' |
Same |
'mouseout' |
'mouseleave' |
Different name |
Markers and Points
Simple Marker
Google Maps:
const marker = new google.maps.Marker({
position: { lat: 37.7749, lng: -122.4194 },
map: map,
title: 'San Francisco',
icon: 'custom-icon.png'
});
// Remove marker
marker.setMap(null);
Mapbox GL JS:
// Create marker
const marker = new mapboxgl.Marker()
.setLngLat([-122.4194, 37.7749])
.setPopup(new mapboxgl.Popup().setText('San Francisco'))
.addTo(map);
// Remove marker
marker.remove();
Multiple Markers
Google Maps:
const markers = locations.map(
(loc) =>
new google.maps.Marker({
position: { lat: loc.lat, lng: loc.lng },
map: map
})
);
Mapbox GL JS (Equivalent Approach):
// Same object-oriented approach
const markers = locations.map((loc) => new mapboxgl.Marker().setLngLat([loc.lng, loc.lat]).addTo(map));
Mapbox GL JS (Data-Driven Approach - Recommended for 100+ points):
// Add as GeoJSON source + layer (uses WebGL, not DOM)
map.addSource('points', {
type: 'geojson',
data: {
type: 'FeatureCollection',
features: locations.map((loc) => ({
type: 'Feature',
geometry: { type: 'Point', coordinates: [loc.lng, loc.lat] },
properties: { name: loc.name }
}))
}
});
map.addLayer({
id: 'points-layer',
type: 'circle', // or 'symbol' for icons
source: 'points',
paint: {
'circle-radius': 8,
'circle-color': '#ff0000'
}
});
Performance Advantage: Google Maps renders all markers as DOM elements (even when using the Data Layer), which becomes slow with 500+ markers. Mapbox's circle and symbol layers are rendered by WebGL, making them much faster for large datasets (1,000-10,000+ points). This is a significant advantage when building applications with many points.
Info Windows / Popups
Google Maps
const infowindow = new google.maps.InfoWindow({
content: '<h3>Title</h3><p>Content</p>'
});
marker.addListener('click', () => {
infowindow.open(map, marker);
});
Mapbox GL JS
// Option 1: Attach to marker
const marker = new mapboxgl.Marker()
.setLngLat([-122.4194,<How to use mapbox-google-maps-migration on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add mapbox-google-maps-migration
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches mapbox-google-maps-migration from GitHub repository mapbox/mapbox-agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate mapbox-google-maps-migration. Access the skill through slash commands (e.g., /mapbox-google-maps-migration) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★44 reviews- ★★★★★Ren Malhotra· Dec 20, 2024
mapbox-google-maps-migration is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aanya Harris· Dec 20, 2024
Keeps context tight: mapbox-google-maps-migration is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Dec 16, 2024
Solid pick for teams standardizing on skills: mapbox-google-maps-migration is focused, and the summary matches what you get after install.
- ★★★★★Alexander Liu· Dec 8, 2024
mapbox-google-maps-migration reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kabir Garcia· Dec 4, 2024
I recommend mapbox-google-maps-migration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kabir Johnson· Nov 23, 2024
Keeps context tight: mapbox-google-maps-migration is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ava Khanna· Nov 11, 2024
Useful defaults in mapbox-google-maps-migration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Diego Chen· Nov 11, 2024
I recommend mapbox-google-maps-migration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Piyush G· Nov 7, 2024
We added mapbox-google-maps-migration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Shikha Mishra· Oct 26, 2024
mapbox-google-maps-migration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 44