Skip to main content
Agent skill

Maps

Show places, directions and day plans on a map in the thread. Use when the user asks what is near a place (restaurants, cafés, a pharmacy, shops of a kind), how to get from A to B (walk, metro, car, bike), where something is, or to lay out a day or a trip on a map.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Maps when an AI agent needs a reusable SKILL.md workflow for this job: Show places, directions and day plans on a map in the thread. Use when the user asks what is near a place (restaurants, cafés, a pharmacy, shops of a kind), how to get from A to B (walk, metro, car, bike), where something is, or to lay out a day or a trip on a map.

When not to use it

Skip Maps when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/maps
# Save SKILL.md to ~/.claude/skills/maps/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/maps/SKILL.md. For a shared project, commit the folder at .claude/skills/maps/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Maps skill for this task: Use Maps when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
57/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Maps

One call shows a map under your tool row; the user can pan, zoom, pick a card, switch the route's mode, search again where they moved the map, and open it in the panel. Call the tools from `run_typescript` as `tools.maps.<tool>`. Each answers text you can read (the places with distances, the route's steps) and the user sees the same thing drawn: do not repeat the list, add what the map can't say (why this one, a tip).

A place is always one of: a name or an address (`"Gare de Lyon, Paris"`; add the city when it is ambiguous), `"48.8443, 2.3744"`, or `{name, lat, lon}`. Prefer coordinates you already have.

## What is near

```ts await tools.maps.search_places({ query: "ramen", near: "Gare de Lyon, Paris" }); await tools.maps.search_places({ query: "pharmacy", near: "48.853, 2.369", radius_m: 800, open_now: true, limit: 5 }); ```

`query` is a few words: a kind (`restaurants`, `vegan restaurant`, `bakery`, `supermarket`, `atm`, `hotel`, `museum`, `bike rental`...) or a name (`Shakespeare and Company`). Nearest first, 10 by default (20 at most), within 1500 m by default. Nothing found: try a wider `radius_m` or plainer words.

## How to get there

```ts await tools.maps.directions({ from: "Place de la Bastille, Paris", to: "Musée du Louvre", mode: "transit" }); ```

`mode`: `walk` (default), `transit`, `drive`, `bike`. `depart_at` (ISO) for a later departure. Without the Google key there is no transit: the answer gives the walking route and says so; tell the user once.

## Your own map (a day, a trip, a shortlist)

```ts await tools.maps.show_map({ title: "Saturday in Lyon", near: "Lyon", // find the names below around here markers: [ { name: "Les Halles Paul Bocuse", group: "Morning", note: "oysters at the counter" }, { name: "Fourvière Basilica", group: "Afternoon" }, "Vieux Lyon", ], routes: [{ from: "Les Halles Paul Bocuse", to: "Fourvière Basilica", mode: "transit", group: "Afternoon" }], }); ```

At most 60 markers and 12 routes. `group` (a day, a part of the day) gives each its color and a filter in the legend: use it for itineraries, one group per day. A marker that could not be found is "Left out" in the answer: fix its name or give its coordinates.

## Where is it

```ts const hits = await tools.maps.geocode({ query: "Shibuya Station" }); // no map: coordinates and address ```

## What comes back to you

When the user picks a place, switches a route's mode or searches another area, the view tells you ("The user picked …", "The user is looking at the transit route…"): answer from that, not from your first call. "Ask about it" on a card sends you "Tell me more about <place>".

## Providers

The plugin answers with OpenStreetMap when the user has set no key (no ratings, no "open now" check, no transit; opening hours as written in OSM), and with Google Maps when he set his key in the plugin's settings (ratings, price level, open now, transit). The answer names the provider. Never ask the user for the key in the chat: point him to the plugins page.

Intended uses

  • Use Maps when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.