cablatecablate/mcp-google-map/skills/google-maps/SKILL.md

google-maps

Skill480 starsChanged 48 days agoMITView on GitHub

Search places, resolve addresses, compare routes, inspect neighborhoods, and retrieve geographic or environmental facts through the standalone @cablate/mcp-google-map CLI. Use for concrete location questions; use the travel-planning or local-seo Skill for those specialized outcomes.

Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

Optimusprimekbu/claude-skillstheir own version, first seen Jun 2, 2026
aiagenta2z/onekey-gatewaytheir own version, first seen Apr 10, 2026
refly-ai/refly-skillstheir own version, first seen Jan 25, 2026

Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
refly-ai/refly-skills★ 204same name
aiagenta2z/onekey-gateway★ 52same name
Optimusprimekbu/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- mcp-google-map-projectSkill
- google-maps-local-seoSkill
- google-maps-travel-planningSkill

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Before presenting Places reviews, photos, or AI summaries, read ../_shared/content-attribution.md.
line 15
Very specific:
Read references/tools-api.md when exact parameters, response fields, or a multi-tool recipe are needed.
line 20
Very specific:
Prefer coordinates over ambiguous addresses and place_id over repeated name searches.
line 21
Very specific:
Treat nonzero exit status or { "success": false } as a failure, not as geographic data.
line 23

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Google Maps

Answer real-world location questions with the package's standalone exec CLI. Do not start or configure an MCP server for this workflow.

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 print it or place it in a command unless the user explicitly accepts shell-history and process-list exposure.
Before presenting Places reviews, photos, or AI summaries, read ../_shared/content-attribution.md.

Workflow

Identify the concrete location outcome and missing inputs. Do not request details that can be resolved by geocoding or place search.
Read references/tools-api.md when exact parameters, response fields, or a multi-tool recipe are needed.
Prefer coordinates over ambiguous addresses and place_id over repeated name searches.
Chain only the calls needed for the outcome. Reuse returned identifiers and coordinates.
Treat nonzero exit status or { "success": false } as a failure, not as geographic data.
Summarize the useful result rather than returning raw JSON. Preserve source and attribution metadata where required.

Tool selection

Outcome	Preferred tools
Address or landmark to coordinates	`maps_geocode`
Coordinates to address	`maps_reverse_geocode`
Nearby discovery	`maps_search_nearby`, then `maps_place_details`
Natural-language place search	`maps_search_places`, then `maps_place_details`
Compare candidate places	`maps_compare_places` or search → details → distance matrix
Route or travel-mode comparison	`maps_directions`, `maps_distance_matrix`
Multi-stop route without a broader itinerary	`maps_plan_route`
Things along a route	`maps_search_along_route`
Neighborhood facts	`maps_explore_area` plus targeted nearby searches
Elevation, timezone, weather, or air quality	corresponding environment tool; geocode first when needed
Visual map	`maps_static_map` after locations or a route are known

Invocation

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

The CLI accepts both MCP-style names such as maps_geocode and short names such as geocode. Each call is stateless and returns JSON on stdout.

Boundaries

For a multi-day itinerary, trip schedule, or travel-day optimization, use google-maps-travel-planning instead.
For Google Business Profile visibility, grid ranking, keyword coverage, or competitor audits, use google-maps-local-seo instead.
maps_weather is unavailable in Japan, China, South Korea, Cuba, Iran, North Korea, and Syria; use a current web source there.
Transit waypoint optimization is unsupported; use optimize: false for transit routes.
Geographic proximity and elevation alone do not establish safety, accessibility, flood risk, or suitability. State those limitations when relevant.

References

references/tools-api.md: read for exact parameters, response shapes, and generic chaining recipes.
../_shared/setup-and-diagnostics.md: read for first-run checks and error classification.
../_shared/content-attribution.md: read before displaying regulated Google Maps content.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free