MCP Google Map Project Agent Skill
Project knowledge for developing and maintaining @cablate/mcp-google-map. Architecture, Google Maps API guide, GIS domain knowledge, and design decisions. Read this skill to onboard onto the project or make informed development decisions.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/cablate/mcp-google-map --skill mcp-google-map-projectThe instruction itself
6 sections, as written by the authormcp-google-map — Project Knowledge
Overview
This skill contains everything needed to develop, maintain, and extend the @cablate/mcp-google-map MCP server. Reading these files gives you full context on architecture, API specifics, domain knowledge, and the reasoning behind design decisions.
For the agent skill (how to USE the tools), see skills/google-maps/SKILL.md.
Quick Orientation
| Aspect | Summary |
|--------|---------|
| What | MCP server providing Google Maps tools for AI agents |
| Stack | TypeScript, Node.js, Express, MCP SDK, Zod |
| Tools | 17 tools (14 atomic + 3 composite) |
| Transports | stdio, Streamable HTTP, standalone exec CLI |
| APIs | Places API (New), Directions, Geocoding, Elevation, Timezone, Weather, Air Quality, Static Maps, Search Along Route |
Reference Files
| File | Content | When to read |
|------|---------|--------------|
| references/architecture.md | System architecture, 3-layer design, transport modes, tool registration flow, 9-file checklist, code map | Start here when onboarding. Also read when adding new tools. |
| references/google-maps-api-guide.md | All Google Maps API endpoints used, pricing, coverage limits, rate limits, common gotchas, Places New vs Legacy | When debugging API errors, evaluating new APIs, or checking costs |
| references/geo-domain-knowledge.md | GIS fundamentals — coordinates, distance, geocoding, place types, spatial search, map projection, Japan-specific knowledge | When making tool design decisions that involve geographic concepts |
| references/decisions.md | 10 Architecture Decision Records (ADR) with context and rationale | When asking "why was X built this way?" or considering changes to existing design |
How to Add a New Tool
See references/architecture.md § "9-File Tool Change Checklist" for the complete procedure. Summary:
- Create
src/tools/maps/<toolName>.ts(NAME, DESCRIPTION, SCHEMA, ACTION) - Register in
src/config.ts - Add exec case in
src/cli.ts - Add to
tests/smoke.test.ts(expectedTools + API call test) - Update
README.md(count + table + exec list + project structure) - Update
skills/google-maps/SKILL.md(Tool Map) - Update
skills/google-maps/references/tools-api.md(params + chaining) - Check
server.jsonandpackage.jsondescriptions
When to Update This Skill
| Trigger | What to update |
|---------|----------------|
| Architecture change | references/architecture.md |
| New Google Maps API integrated | references/google-maps-api-guide.md |
| New design decision made | references/decisions.md (add ADR) |
| New GIS concept relevant to tools | references/geo-domain-knowledge.md |
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take cablate/mcp-google-map-project from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.