mapbox-maplibre-migration▌
mapbox/mapbox-agent-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Expert guidance for migrating from MapLibre GL JS to Mapbox GL JS. Covers the shared history, API compatibility, migration steps, and the advantages of Mapbox's platform.
MapLibre to Mapbox Migration Skill
Expert guidance for migrating from MapLibre GL JS to Mapbox GL JS. Covers the shared history, API compatibility, migration steps, and the advantages of Mapbox's platform.
Understanding the Fork
History
MapLibre GL JS is an open-source fork of Mapbox GL JS v1.13.0, created in December 2020 when Mapbox changed their license starting with v2.0.
Timeline:
- Pre-2020: Mapbox GL JS was open source (BSD license)
- Dec 2020: Mapbox GL JS v2.0 introduced proprietary license
- Dec 2020: Community forked v1.13 as MapLibre GL JS
- Present: Both libraries continue active development
Key Insight: The APIs are ~95% identical because MapLibre started as a Mapbox fork. Most code works in both with minimal changes, making migration straightforward.
Why Migrate to Mapbox?
Compelling reasons to choose Mapbox GL JS:
- Official Support & SLAs: Enterprise-grade support with guaranteed response times
- Superior Tile Quality: Best-in-class vector tiles with global coverage and frequent updates
- Better Satellite Imagery: High-resolution, up-to-date satellite and aerial imagery
- Rich Ecosystem: Seamless integration with Mapbox Studio, APIs, and services
- Advanced Features: Traffic-aware routing, turn-by-turn directions, premium datasets
- Geocoding & Search: World-class address search and place lookup
- Navigation SDK: Mobile navigation with real-time traffic
- No Tile Infrastructure: No need to host or maintain your own tile servers
- Regular Updates: Continuous improvements and new features
- Professional Services: Access to Mapbox solutions team for complex projects
Mapbox offers a generous free tier: 50,000 map loads/month, making it suitable for many applications without cost.
Quick Comparison
| Aspect | Mapbox GL JS | MapLibre GL JS |
|---|---|---|
| License | Proprietary (v2+) | BSD 3-Clause (Open Source) |
| Support | Official commercial support | Community support |
| Tiles | Premium Mapbox vector tiles | OSM or custom tile sources |
| Satellite | High-quality global imagery | Requires custom source |
| Token | Required (access token) | Optional (depends on tile source) |
| APIs | Full Mapbox ecosystem | Requires third-party services |
| Studio | Full integration | No native integration |
| 3D Terrain | Built-in with premium data | Available (requires data source) |
| Globe View | v2.9+ | v3.0+ |
| API Compatibility | ~95% compatible with MapLibre | ~95% compatible with Mapbox |
| Bundle Size | ~500KB | ~450KB |
| Setup Complexity | Easy (just add token) | Requires tile source setup |
Step-by-Step Migration
1. Create Mapbox Account
- Sign up at mapbox.com
- Get your access token from the account dashboard
- Review pricing: Free tier includes 50,000 map loads/month
- Note your token (starts with
pk.for public tokens)
2. Update Package
# Remove MapLibre
npm uninstall maplibre-gl
# Install Mapbox
npm install mapbox-gl
3. Update Imports
// Before (MapLibre)
import maplibregl from 'maplibre-gl';
import 'maplibre-gl/dist/maplibre-gl.css';
// After (Mapbox)
import mapboxgl from 'mapbox-gl';
import 'mapbox-gl/dist/mapbox-gl.css';
Or with CDN:
<!-- Before (MapLibre) -->
<script src="https://unpkg.com/[email protected]/dist/maplibre-gl.js"></script>
<link href="https://unpkg.com/[email protected]/dist/maplibre-gl.css" rel="stylesheet" />
<!-- After (Mapbox) -->
<script src="https://api.mapbox.com/mapbox-gl-js/v3.0.0/mapbox-gl.js"></script>
<link href="https://api.mapbox.com/mapbox-gl-js/v3.0.0/mapbox-gl.css" rel="stylesheet" />
4. Add Access Token
// Add this before map initialization
mapboxgl.accessToken = 'pk.your_mapbox_access_token';
Token best practices:
- Use environment variables:
process.env.VITE_MAPBOX_TOKENorprocess.env.NEXT_PUBLIC_MAPBOX_TOKEN - Add URL restrictions in Mapbox dashboard for security
- Use public tokens (
pk.*) for client-side code - Never commit tokens to git (add to
.envand.gitignore) - Rotate tokens if compromised
See mapbox-token-security skill for comprehensive token security guidance.
5. Update Map Initialization
// Before (MapLibre)
const map = new maplibregl.Map({
container: 'map',
style: 'https://demotiles.maplibre.org/style.json', // or your custom style
center: [-122.4194, 37.7749],
zoom: 12
});
// After (Mapbox)
mapboxgl.accessToken = 'pk.your_mapbox_access_token';
const map = new mapboxgl.Map({
container: 'map',
style: 'mapbox://styles/mapbox/standard', // Mapbox style
center: [-122.4194, 37.7749],
zoom: 12
});
6. Update Style URL
Mapbox provides professionally designed, maintained styles:
// Mapbox built-in styles
style: 'mapbox://styles/mapbox/standard'; // Mapbox Standard (default)
style: 'mapbox://styles/mapbox/standard-satellite'; // Mapbox Standard Satellite
style: 'mapbox://styles/mapbox/streets-v12'; // Streets v12
style: 'mapbox://styles/mapbox/satellite-v9'; // Satellite imagery
style: 'mapbox://styles/mapbox/satellite-streets-v12'; // Hybrid
style: 'mapbox://styles/mapbox/outdoors-v12'; // Outdoor/recreation
style: 'mapbox://styles/mapbox/light-v11'; // Light theme
style: 'mapbox://styles/mapbox/dark-v11'; // Dark theme
style: 'mapbox://styles/mapbox/navigation-day-v1'; // Navigation (day)
style: 'mapbox://styles/mapbox/navigation-night-v1'; // Navigation (night)
Custom styles: You can also create and use custom styles from Mapbox Studio:
style: 'mapbox://styles/your-username/your-style-id';
7. Update All References
Replace all maplibregl references with mapboxgl:
// Markers
const marker = new mapboxgl.Marker() // was: maplibregl.Marker()
.setLngLat([-122.4194, 37.7749])
.setPopup(new mapboxgl.Popup().setText('San Francisco'))
.addTo(map);
// Controls
map.addControl(new mapboxgl.NavigationControl(), 'top-right');
map.addControl(new mapboxgl.GeolocateControl());
map.addControl(new mapboxgl.FullscreenControl());
map.addControl(new mapboxgl.ScaleControl());
8. Update Plugins (If Used)
Some MapLibre plugins should be replaced with Mapbox versions:
| MapLibre Plugin | Mapbox Alternative |
|---|---|
@maplibre/maplibre-gl-geocoder |
@mapbox/mapbox-gl-geocoder |
@maplibre/maplibre-gl-draw |
@mapbox/mapbox-gl-draw |
maplibre-gl-compare |
mapbox-gl-compare |
Example:
// Before (MapLibre)
import MaplibreGeocoder from '@maplibre/maplibre-gl-geocoder';
// After (Mapbox)
import MapboxGeocoder from '@mapbox/mapbox-gl-geocoder';
map.addControl(
new MapboxGeocoder({
accessToken: mapboxgl.accessToken,
mapboxgl: mapboxgl
})
How to use mapbox-maplibre-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-maplibre-migration
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches mapbox-maplibre-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-maplibre-migration. Access the skill through slash commands (e.g., /mapbox-maplibre-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▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★70 reviews- ★★★★★Valentina Menon· Dec 16, 2024
We added mapbox-maplibre-migration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ganesh Mohane· Dec 12, 2024
mapbox-maplibre-migration is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Henry Mehta· Dec 8, 2024
Registry listing for mapbox-maplibre-migration matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ren Okafor· Dec 4, 2024
mapbox-maplibre-migration has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kwame Abbas· Dec 4, 2024
mapbox-maplibre-migration reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Arya Verma· Nov 27, 2024
mapbox-maplibre-migration reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Valentina Jain· Nov 23, 2024
Solid pick for teams standardizing on skills: mapbox-maplibre-migration is focused, and the summary matches what you get after install.
- ★★★★★Chinedu Shah· Nov 23, 2024
Registry listing for mapbox-maplibre-migration matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ren Srinivasan· Nov 7, 2024
Useful defaults in mapbox-maplibre-migration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Sakshi Patil· Nov 3, 2024
mapbox-maplibre-migration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 70