Maptiler Skills
Coding skill for building location-aware applications across the MapTiler platform.
Install
/plugin marketplace add maptiler/maptiler-skillsInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →MapTiler — Agent Skill
Expert coding skill for building location-aware applications across the full MapTiler platform. It gives AI coding agents the context to generate correct, production-ready code using MapTiler Cloud APIs, the MapTiler SDK, MapTiler GeoSplats SDK mobile SDKs, and on-premise tools.
Built on the Agent Skills open standard, so the same skill works across Claude Code, Gemini CLI, Cursor, Windsurf, and other compatible AI agents.
🌐 Website 🔑 Get API Key
Table of Contents
What it does
A skill is on-demand expertise: the agent loads it only when your request matches the skill's description, then follows its instructions instead of guessing. When you ask for maps, geocoding, weather, elevation, vector tiles, or any geospatial feature, this skill makes the agent:
- Generate platform-correct code for web (MapTiler SDK JS, Leaflet, OpenLayers), frameworks (React, Svelte, Vue, Angular, Cesium, deck.gl), mobile (iOS Swift, Android Kotlin, Flutter, React Native), and on-premise (MapTiler Server, MapTiler Engine).
- Call the right Cloud REST API (geocoding, weather, static maps, elevation, tiles, coordinates, IP geolocation, admin/tilesets) with correct endpoints and auth patterns.
- Apply modern v4 styles automatically, upgrading deprecated
*-v2/*-v3style IDs wherever they appear. - Use pinned, current versions for every SDK, CDN script, and dependency, with no unresolved template placeholders.
- Cross-reference vector tile schemas (Planet v4, Buildings, Contours, Outdoor, Ocean, Landcover, Landform, Cadastre) before inventing source-layer names, paint expressions, or filter keys.
- Handle framework lifecycle correctly — WebGL cleanup, stale-closure prevention in React, isolated reactivity, ES module vs UMD CDN selection.
How skills, plugins, and agents fit together
It helps to keep three layers separate, because the install steps below differ by layer:
- The skill is the portable content: a
SKILL.mdplus areferences/folder. This is what every agent actually reads, and it's identical across tools. - The plugin is a Claude Code–specific wrapper for distributing the skill through a marketplace. Other tools don't use it.
- The agent (Claude Code, Gemini CLI, Cursor, Windsurf…) is the tool that loads the skill from its own skills directory.
So there are three ways to install: with the Skills CLI (npx skills add, auto-detects your agent and works across dozens of them), through the Claude Code plugin marketplace (Claude Code only), or by copying the skill folder into any agent's skills directory (works everywhere).
What triggers a skill is the same in every tool: the description field in the SKILL.md frontmatter. The agent matches your request against that description to decide whether to activate the skill, so installation alone isn't enough — the skill also has to be registered and triggered.
📦 Installation
Universal — via Skills CLI
Similar plugs
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…
Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.
The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…