Agent skill

Google Maps Travel Planning

by cablate in cablate/mcp-google-map

Build evidence-backed day trips, multi-day itineraries, and efficient stop sequences with Google Maps data through the standalone CLI.

MITAuto-check passedMarketing & SEO

Install Google Maps Travel Planning

skills CLI
$ npx skills add cablate/mcp-google-map --skill google-maps-travel-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cablate/mcp-google-map google-maps-travel-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cablate/mcp-google-map.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/google-maps-travel-planning .claude/skills/google-maps-travel-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
google-maps-travel-planning
GitHub stars
468
Token cost
~710 tokens
SKILL.md length
307 words
Files
2 (incl. references)
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Build evidence-backed day trips, multi-day itineraries, and efficient stop sequences with Google Maps data through the standalone CLI.

  • Works in 8 steps: Establish destination, dates or… → Read references/travel-planning.md… → Use maps_search_places to find candidate… → …
  • The desired output is a practical travel plan
  • SKILL.md covers Before calling the CLI, Workflow, CLI and Boundaries, plus 1 more section
  • Calls npx; needs GOOGLE_MAPS_API_KEY

What it does

Google Maps Travel Planning is an agent skill from cablate/mcp-google-map. Build evidence-backed day trips, multi-day itineraries, and efficient stop sequences with Google Maps data through the standalone CLI. Use when the desired output is a practical travel plan, not merely a route or list of places.

Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/travel-planning.md`).

It sits in Marketing & SEO, covering Local SEO. It works with Google Maps Platform and Model Context Protocol. The repository describes itself as: 18 Google Maps tools and 3 Agent Skills for place search, routes, travel planning, and local SEO—via MCP or standalone CLI. The licence is MIT.

When your agent uses it

  • The desired output is a practical travel plan
  • Not merely a route

Example prompts

  • “/google-maps-travel-planning”

Requirements

  • Node.js
  • A credential in GOOGLE_MAPS_API_KEY

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Establish destination, dates or duration, fixed anchors, mobility constraints, pace, and relevant preferences. Ask only for omissions that…
  2. Read references/travel-planning.md before designing the itinerary.
  3. Use maps_search_places to find candidate anchors, then group nearby anchors into one-direction daily arcs.
  4. Use maps_search_along_route for meals and breaks between anchors. Use maps_place_details for hours, ratings, and source metadata.
  5. Validate every day with maps_plan_route or maps_directions. Do not present estimated timing as validated timing.
  6. Check weather and air quality when they affect the plan. Respect regional weather limitations described in the reference.
  7. When useful, produce a numbered static map after the stop order is final.
  8. Present a day-by-day schedule with travel time, visit duration, reservations or opening-hour caveats, and clearly marked fallbacks.

What it can do on your machine

Read from SKILL.md and the folder at commit bc2c31f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GOOGLE_MAPS_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Google Maps Travel Planning loads about 710 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 307 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~710
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cablate/mcp-google-map at commit bc2c31f, republished under its MIT licence (© cablate). 307 words, ~710 tokens.

Download SKILL.mdSave it as .claude/skills/google-maps-travel-planning/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
google-maps-travel-planning
description
Build evidence-backed day trips, multi-day itineraries, and efficient stop sequences with Google Maps data through the standalone CLI. Use when the desired output is a practical travel plan, not merely a route or list of places.
license
MIT

Google Maps Travel Planning

Build a time-ordered itinerary whose geography, travel times, opening constraints, and along-route stops have been checked. Use the standalone CLI; no MCP connection is required.

Before calling the CLI

  • On the first call in a session, or after an execution failure, read ../_shared/setup-and-diagnostics.md and run the non-billable local preflight.
  • The user must supply GOOGLE_MAPS_API_KEY. Never expose its value.
  • Read ../_shared/content-attribution.md before presenting reviews, photos, or Google-generated summaries.

Workflow

  1. Establish destination, dates or duration, fixed anchors, mobility constraints, pace, and relevant preferences. Ask only for omissions that materially change the itinerary.
  2. Read references/travel-planning.md before designing the itinerary.
  3. Use maps_search_places to find candidate anchors, then group nearby anchors into one-direction daily arcs.
  4. Use maps_search_along_route for meals and breaks between anchors. Use maps_place_details for hours, ratings, and source metadata.
  5. Validate every day with maps_plan_route or maps_directions. Do not present estimated timing as validated timing.
  6. Check weather and air quality when they affect the plan. Respect regional weather limitations described in the reference.
  7. When useful, produce a numbered static map after the stop order is final.
  8. Present a day-by-day schedule with travel time, visit duration, reservations or opening-hour caveats, and clearly marked fallbacks.

CLI

bash
npx -y @cablate/mcp-google-map exec <tool> '<json_params>'

For exact tool parameters, read ../google-maps/references/tools-api.md only for the tools selected by the plan.

Boundaries

  • A request for only A-to-B directions or a simple multi-stop ordering belongs to google-maps.
  • A request to assess business visibility or local search rankings belongs to google-maps-local-seo.
  • Do not infer that a venue is accessible, open, safe, or suitable when the API response does not establish it.
  • Do not silently substitute web estimates for unavailable Google Maps results; identify the alternate source.

References

  • references/travel-planning.md: required methodology, timing budgets, geographic arcs, and anti-patterns.
  • ../google-maps/references/tools-api.md: exact parameters and response shapes for selected tools.
  • ../_shared/setup-and-diagnostics.md: first-run and failure recovery.
  • ../_shared/content-attribution.md: Places presentation requirements.

© cablate, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/google-maps-travel-planning of cablate/mcp-google-map.

  • SKILL.md
  • references/travel-planning.md

Open the folder on GitHubat commit bc2c31f

Compare with similar skills

Google Maps Travel Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Google Maps Travel Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Google Maps Travel Planning this skillcablate/mcp-google-map468—~710Automated safety check: PassMIT
SEO Project Setuppetera2c/simple-table2292 repos~1.5kAutomated safety check: PassMIT
Maps Intelligence for Local SEOAgriciDaniel/claude-seo18k1 repos~3.1kAutomated safety check: PassMIT
SeogTerminalSkills/skills163—~3.4kAutomated safety check: PassApache-2.0
Local SEOnowork-studio/notfair-plugin3.9k—~1.6kAutomated safety check: PassMIT
Local SEO Manageralirezarezvani/claude-skills28k—~3.3kAutomated safety check: PassMIT

Similar skills

  • SEO Project Setup

    petera2c/simple-table

    Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.

    229 GitHub starsUsed in 2 repos~1.5k tokens
    Marketing & SEOAuto-check passed
  • Maps Intelligence for Local SEO

    AgriciDaniel/claude-seo

    Audits how a local business appears across Google Maps, Bing Places, Apple Maps, and OpenStreetMap, with geo-grid rank tracking.

    18k GitHub starsUsed in 1 repo~3.1k tokens
    Marketing & SEOAuto-check passed
  • Seog

    TerminalSkills/skills

    Run local SEO from your terminal via the SEOG MCP server — Google Business Profile management, map-pack rank tracking and geo-grid scans, review sync and replies published to Google, competitor…

    163 GitHub stars~3.4k tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed
  • Local SEO

    nowork-studio/notfair-plugin

    Local SEO and Google Business Profile audit: diagnose why a business isn't ranking in the local pack / map results and produce a fix plan.

    3.9k GitHub stars~1.6k tokensUpdated 7 days ago
    Marketing & SEOAuto-check passed
  • Local SEO Manager

    alirezarezvani/claude-skills

    Manage local SEO for service-area businesses — appliance repair, HVAC, plumbing, cleaning, and any business that serves customers at their location.

    28k GitHub stars~3.3k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Nap Consistency

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing a local business website for local SEO.

    74k GitHub stars~613 tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

More from cablate/mcp-google-map

  • Google Maps

    cablate/mcp-google-map

    Search places, resolve addresses, compare routes, inspect neighborhoods, and retrieve geographic or environmental facts through the standalone @cablate/mcp-google-map CLI.

    468 GitHub stars~909 tokensUpdated 11 days ago
    Auto-check passed
  • Google Maps Local SEO

    cablate/mcp-google-map

    Analyze Google Business Profile visibility, geographic grid rankings, local search keywords, and nearby competitors through the standalone Google Maps CLI.

    468 GitHub stars~633 tokensUpdated 11 days ago
    Auto-check passed
  • MCP Google Map Project

    cablate/mcp-google-map

    Project knowledge for developing and maintaining @cablate/mcp-google-map.

    468 GitHub stars~774 tokensUpdated 11 days ago
    Auto-check passed

Questions about Google Maps Travel Planning

What does Google Maps Travel Planning do?

Build evidence-backed day trips, multi-day itineraries, and efficient stop sequences with Google Maps data through the standalone CLI. Google Maps Travel Planning is an agent skill from cablate/mcp-google-map. Build evidence-backed day trips, multi-day itineraries, and efficient stop sequences with Google Maps data through the standalone CLI.

When should I use Google Maps Travel Planning?

Google Maps Travel Planning fits situations like: the desired output is a practical travel plan; not merely a route.

How do I install Google Maps Travel Planning in Claude Code?

Run `npx skills add cablate/mcp-google-map --skill google-maps-travel-planning -a claude-code`. Or copy the skill folder (skills/google-maps-travel-planning in cablate/mcp-google-map) into .claude/skills/google-maps-travel-planning in your project. Claude Code loads it when a task matches its description.

How do I install Google Maps Travel Planning in Codex?

Run `npx skills add cablate/mcp-google-map --skill google-maps-travel-planning -a codex`. Or copy the skill folder (skills/google-maps-travel-planning in cablate/mcp-google-map) into .agents/skills/google-maps-travel-planning in your project. Codex loads it when a task matches its description.

Can I use Google Maps Travel Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cablate/mcp-google-map --skill google-maps-travel-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-maps-travel-planning, .gemini/skills/google-maps-travel-planning, .github/skills/google-maps-travel-planning and .opencode/skills/google-maps-travel-planning in your project.

What does Google Maps Travel Planning need to run?

Going by SKILL.md and its folder, Google Maps Travel Planning needs the command-line tools its instructions call (npx) and credentials named GOOGLE_MAPS_API_KEY. Our summary lists: Node.js; A credential in GOOGLE_MAPS_API_KEY.

Does Google Maps Travel Planning access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Google Maps Travel Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Google Maps Travel Planning use?

Google Maps Travel Planning is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Google Maps Travel Planning use?

About 710 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Google Maps Travel Planning?

Skills that share tags, products or a category with Google Maps Travel Planning: SEO Project Setup (petera2c/simple-table, 229 stars), Maps Intelligence for Local SEO (AgriciDaniel/claude-seo, 18k stars), Seog (TerminalSkills/skills, 163 stars) and Local SEO (nowork-studio/notfair-plugin, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Google Maps Travel Planning?

cablate (a GitHub user) maintains it in cablate/mcp-google-map, which has 468 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 26, 2026.

Source: cablate/mcp-google-map on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.