Skip to content
Back to search

maplibre-agent-skills

Community-maintained agent skills for MapLibre GL JS — helping AI coding assistants write better mapping code

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/maplibre/maplibre-agent-skills with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/maplibre/maplibre-agent-skills'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/maplibre--maplibre-agent-skills/badge.svg)](/listings/maplibre--maplibre-agent-skills)

HTML

<a href="/listings/maplibre--maplibre-agent-skills"><img src="/api/listings/maplibre--maplibre-agent-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Installing skills into your project means AI assistants automatically pick them up when you describe a task — no need to define context manually each time.

An install copies skill directories only. If an installed skill turns out to be wrong, don't fix it in place — that copy is overwritten on the next update, and no one else benefits. Every `SKILL.md` ends with a link to the [AI failure report](https://github.com/maplibre/maplibre-agent-skills/issues/new?template=ai-failure-report.md) form for exactly that.

Without the CLI

Skills are plain markdown.

- **Paste into chat**: Open any `SKILL.md` above and paste it directly into your AI assistant's context window. - **Copy to your project**: Copy `skills/<name>/` to `.agents/skills/<name>/`, which Cursor, GitHub Copilot and Codex read, or to `.claude/skills/<name>/` for Claude Code. - **Symlink for local development**:

mkdir -p .claude
ln -s /path/to/maplibre-agent-skills/skills .claude/skills

As a Claude Code plugin

/plugin install maplibre-agent-skills --marketplace maplibre/maplibre-agent-skills

The plugin carries every skill in `skills/` except the maintainers' eval runbook.

Via the skills CLI

The [skills CLI](https://github.com/vercel-labs/skills) is a package manager for AI agent skills. It installs each skill where your agent looks for it.

# List available skills
npx skills add maplibre/maplibre-agent-skills --list

# Install all skills
npx skills add maplibre/maplibre-agent-skills

# Install a single skill
npx skills add maplibre/maplibre-agent-skills --skill maplibre-tile-sources

By default, skills are installed per project. To install globally (e.g. to your user profile):

npx skills add maplibre/maplibre-agent-skills -g

To install for a specific agent:

npx skills add maplibre/maplibre-agent-skills -a claude-code
npx skills add maplibre/maplibre-agent-skills -a cursor
npx skills add maplibre/maplibre-agent-skills -a github-copilot

See [Supported Agents](https://github.com/vercel-labs/skills?tab=readme-ov-file#supported-agents) for the full list.

Once installed, you can manage skills with:

| Command | Description | | ---------------------------- | ---------------------------------------------- | | `npx skills list` | List installed skills (alias: `ls`) | | `npx skills find [query]` | Search for skills interactively or by keyword | | `npx skills remove [skills]` | Remove installed skills from agents | | `npx skills check` | Check for available skill updates | | `npx skills update` | Update all installed skills to latest versions | | `npx skills init [name]` | Create a new SKILL.md template |

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 29 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "maplibre",
  3. "owner": {
  4. "name": "MapLibre"
  5. },
  6. "metadata": {
  7. "description": "Agent skills for building MapLibre apps"
  8. },
  9. "plugins": [
  10. {
  11. "name": "maplibre-agent-skills",
  12. "description": "MapLibre GL JS and Native guidance: tile sources and source wiring, PMTiles, terrain, fonts and glyphs, sprites and icons, cartography, and migrations from Mapbox and from GL JS v5",
  13. "source": "./",
  14. "strict": false,
  15. "skills": [
  16. "./skills/maplibre-cartography",
  17. "./skills/maplibre-fonts-glyphs",
  18. "./skills/maplibre-mapbox-migration",
  19. "./skills/maplibre-pmtiles-patterns",
  20. "./skills/maplibre-skill-authoring",
  21. "./skills/maplibre-source-wiring",
  22. "./skills/maplibre-sprites-icons",
  23. "./skills/maplibre-terrain-rendering",
  24. "./skills/maplibre-tile-sources",
  25. "./skills/maplibre-v6-migration"
  26. ]
  27. }
  28. ]
  29. }
README.md · README · 163 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # MapLibre Agent Skills
  2. Curated guidance for AI assistants building MapLibre applications — covering ecosystem and open-source best practices.
  3. Agent skills are markdown files that AI coding assistants read as context. When you ask an AI agent to implement something using MapLibre, these skills give the AI the judgment to avoid common API gotchas, and suggest patterns that work.
  4. New skills are prioritized by reported AI failures, recent API/library changes, and long-standing issues documented in GitHub, Stack Overflow, or the community Slack.
  5. ## Correctness Guarantee
  6. We strive to make sure the skills in this repo are:
  7. - **Accurate** — Matches MapLibre and referenced APIs/docs
  8. - **Actionable** — Clear guidance, not just general, declarative descriptions
  9. - **Warranted** — Targets something an AI assistant actually gets wrong without the skill
  10. - **Attribution** — Reference primary sources wherever possible, and always preserve Mapbox copyright where content is adapted
  11. - **Consistent** — Format and style in line with existing skills
  12. If you find any inconsistency with this quality bar, please file an issue or PR.
  13. ## What Status Means
  14. Each skill is tested with [Promptfoo](https://promptfoo.dev/) evals to verify it improves AI responses on real developer questions. The `metadata.status` field in a skill's front matter records where it stands (e.g. whether an eval has proven it fixes a real failure). See [`evals/README.md`](evals/README.md) for how evals work.
  15. | Status | Means |
  16. | ---------------- | -------------------------------------------------------------------------------------------------------------- |
  17. | ✅ `verified` | An eval proved the skill fixes a real failure; results are committed to `evals/results/` |
  18. | 🧪 `provisional` | No eval rubric, an incomplete one, or a rubric that no longer validates the skill's gap |
  19. | `process` | About maintaining this repo, not MapLibre — [eval-exempt](CONTRIBUTING.md#4-process-skills), no `status` badge |
  20. Note that provisional skills are not necessarily lower quality or less reliable. See [CONTRIBUTING.md](CONTRIBUTING.md) for how a skill moves between `provisional` and `verified`.
  21. ## Available Skills
  22. Each skill's front matter is the source of truth for its current status — see [What Status Means](#what-status-means).
  23. <!-- skills-table:start -->
  24. <!-- Rows are regenerated at release by `npm run generate:skills-table`: sorted by name, new skills added, removed skills dropped. Edit the "Use when" text in place; it is preserved. -->
  25. | Skill | Use when |
  26. | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  27. | [`maplibre-cartography`](skills/maplibre-cartography/SKILL.md) | Styling a map; making labels, markers, or roads readable on imagery or vector basemaps |
  28. | [`maplibre-fonts-glyphs`](skills/maplibre-fonts-glyphs/SKILL.md) | Text labels aren't rendering in the intended font, setting up a glyphs server, choosing between self-hosting and generating font PBFs, or handling non-Latin scripts |
  29. | [`maplibre-mapbox-migration`](skills/maplibre-mapbox-migration/SKILL.md) | Moving an existing Mapbox GL JS app to MapLibre; evaluating MapLibre as an open-source alternative |
  30. | [`maplibre-pmtiles-patterns`](skills/maplibre-pmtiles-patterns/SKILL.md) | Hosting tiles without a tile server; static or serverless deployments; converting from MBTiles; generating tiles from OSM or GeoJSON |
  31. | [`maplibre-skill-authoring`](skills/maplibre-skill-authoring/SKILL.md) | At the end of a MapLibre task that took real research, or when asked to capture one as a skill |
  32. | [`maplibre-source-wiring`](skills/maplibre-source-wiring/SKILL.md) | A source is configured but nothing is drawing, or when setFeatureState does nothing |
  33. | [`maplibre-sprites-icons`](skills/maplibre-sprites-icons/SKILL.md) | Deciding how to put icons on a map, when a symbol layer's icons never appear, when adding your own icons to a style whose sprite you do not control, or when shields are missing their badge |
  34. | [`maplibre-terrain-rendering`](skills/maplibre-terrain-rendering/SKILL.md) | Relief looks harsh, flat, or absent, or when the layer type or property for an elevation effect is unclear |
  35. | [`maplibre-tile-sources`](skills/maplibre-tile-sources/SKILL.md) | Choosing how to supply map data; deciding between GeoJSON and tiles; configuring a basemap; debugging blank maps or missing labels |
  36. | [`maplibre-v6-migration`](skills/maplibre-v6-migration/SKILL.md) | A v5 app breaks after upgrading to v6, or before pinning a v6 install |
  37. <!-- skills-table:end -->
  38. ## Development
  39. Each skill lives under `skills/<skill-name>/` as a single **SKILL.md**: YAML front matter (`name`, `description`, and `metadata.status`) plus markdown content.
  40. See [CONTRIBUTING.md](CONTRIBUTING.md) to add or improve a skill. All experience levels welcome, well-behaved and supervised AI agents are welcome to contribute too.
  41. The repo root carries an [**AGENTS.md**](AGENTS.md) to orient an AI agent working in a clone of this repo and instruct agents on how to report failures.
  42. **Using the convention in your own repo:** if you maintain a repo within the MapLibre organization or ecosystem, put an [`AGENTS.md`](AGENTS.md) file with a short stub that routes AI failures related to MapLibre to this repo.
  43. Here is a template:
  44. ```markdown
  45. # AGENTS.md
  46. ## MapLibre coding help
  47. Before writing MapLibre code, install the MapLibre agent skills:
  48. npx skills add maplibre/maplibre-agent-skills
  49. Source: https://github.com/maplibre/maplibre-agent-skills
  50. If you encounter something you do not know how to do, consult the MapLibre docs and this collection of skills. If neither contains the information you are looking for, or MapLibre behaves differently than a skill says report it:
  51. https://github.com/maplibre/maplibre-agent-skills/issues/new?template=ai-failure-report.md
  52. ```
  53. ## Versioning
  54. This project follows [semver](https://semver.org/). Version numbers signal what changed between releases:
  55. - **Patch** (0.1.0 → 0.1.1) — content fixes, corrected examples, tooling changes. Safe to update without review.
  56. - **Minor** (0.1.0 → 0.2.0) — a new skill was added, a skill was removed, or how skills are consumed changed. Review the [CHANGELOG](CHANGELOG.md) to see what's new.
  57. - **Major** (0.x → 1.0) — a change that would break installed skills (renamed directories, restructured front matter, etc.).
  58. Each skill's front matter carries a `metadata.status` field — see [What Status Means](#what-status-means). The [CHANGELOG](CHANGELOG.md) records notable changes; entries are written by contributors via a structured PR field and accrued automatically on merge. See [CONTRIBUTING.md](CONTRIBUTING.md#how-to-fill-in-the-changelog-field) for how that works.
  59. ## Install
  60. Installing skills into your project means AI assistants automatically pick them up when you describe a task — no need to define context manually each time.
  61. An install copies skill directories only. If an installed skill turns out to be wrong, don't fix it in place — that copy is overwritten on the next update, and no one else benefits. Every `SKILL.md` ends with a link to the [AI failure report](https://github.com/maplibre/maplibre-agent-skills/issues/new?template=ai-failure-report.md) form for exactly that.
  62. ### Without the CLI
  63. Skills are plain markdown.
  64. - **Paste into chat**: Open any `SKILL.md` above and paste it directly into your AI assistant's context window.
  65. - **Copy to your project**: Copy `skills/<name>/` to `.agents/skills/<name>/`, which Cursor, GitHub Copilot and Codex read, or to `.claude/skills/<name>/` for Claude Code.
  66. - **Symlink for local development**:
  67. ```bash
  68. mkdir -p .claude
  69. ln -s /path/to/maplibre-agent-skills/skills .claude/skills
  70. ```
  71. ### As a Claude Code plugin
  72. ```text
  73. /plugin install maplibre-agent-skills --marketplace maplibre/maplibre-agent-skills
  74. ```
  75. The plugin carries every skill in `skills/` except the maintainers' eval runbook.
  76. ### Via the skills CLI
  77. The [skills CLI](https://github.com/vercel-labs/skills) is a package manager for AI agent skills. It installs each skill where your agent looks for it.
  78. ```bash
  79. # List available skills
  80. npx skills add maplibre/maplibre-agent-skills --list
  81. # Install all skills
  82. npx skills add maplibre/maplibre-agent-skills
  83. # Install a single skill
  84. npx skills add maplibre/maplibre-agent-skills --skill maplibre-tile-sources
  85. ```
  86. By default, skills are installed per project. To install globally (e.g. to your user profile):
  87. ```bash
  88. npx skills add maplibre/maplibre-agent-skills -g
  89. ```
  90. To install for a specific agent:
  91. ```bash
  92. npx skills add maplibre/maplibre-agent-skills -a claude-code
  93. npx skills add maplibre/maplibre-agent-skills -a cursor
  94. npx skills add maplibre/maplibre-agent-skills -a github-copilot
  95. ```
  96. See [Supported Agents](https://github.com/vercel-labs/skills?tab=readme-ov-file#supported-agents) for the full list.
  97. Once installed, you can manage skills with:
  98. | Command | Description |
  99. | ---------------------------- | ---------------------------------------------- |
  100. | `npx skills list` | List installed skills (alias: `ls`) |
  101. | `npx skills find [query]` | Search for skills interactively or by keyword |
  102. | `npx skills remove [skills]` | Remove installed skills from agents |
  103. | `npx skills check` | Check for available skill updates |
  104. | `npx skills update` | Update all installed skills to latest versions |
  105. | `npx skills init [name]` | Create a new SKILL.md template |
  106. ## License
  107. MIT License. Copyright (c) MapLibre and contributors. See [LICENSE.md](LICENSE.md) and [NOTICE](NOTICE) for more information.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.