{"id":"32d3ce00-d0ab-4dd5-b87c-ce2f8c25da79","entityType":"agent","slug":"clawhub-hith3sh-google-maps-places","name":"Google Maps","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-google-maps-places","canonicalPath":"/agent/clawhub-hith3sh-google-maps-places","generatedAt":"2026-10-09T19:17:25.583Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T11:16:19.793Z","emptyReason":null},"description":"Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when u... Skill: Google Maps Owner: hith3sh Summary: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when u... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:10:12.420Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic s","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.8K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:google-maps-places","sourceUrl":"https://clawhub.ai/hith3sh/google-maps-places","homepage":"https://clawhub.ai/hith3sh/skills/google-maps-places","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/google-maps-places","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/google-maps-places","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":69,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when u..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:16:19.793Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:16:19.793Z","emptyReason":null},"stars":null,"forks":null,"downloads":2832,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"2.8K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:16:19.793Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T11:16:19.793Z","lastCrawledAt":"2026-10-09T11:16:19.793Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T11:16:19.793Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-06-09T07:10:12.420Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":6002},{"version":"1.0.5","createdAt":"2026-06-09T06:09:22.405Z","changelog":"- Updated the Google Maps brand logo image link for improved resource loading. - Removed the redundant skill-card.md file. - No functional or usage changes to tools or setup flow.","fileCount":3,"zipByteSize":6100},{"version":"1.0.4","createdAt":"2026-06-09T04:55:58.190Z","changelog":"- Removed the file skill-card.md to clean up redundant documentation. - No changes to functionality or main documentation.","fileCount":3,"zipByteSize":5880},{"version":"1.0.1","createdAt":"2026-06-08T16:37:32.427Z","changelog":"- Added a Google Maps brand logo at the top of the documentation for clearer identification. - Minor documentation update in SKILL.md; no feature or functional changes. - Removed the file: skill-card.md (no longer included in this version).","fileCount":3,"zipByteSize":5962},{"version":"0.1.1","createdAt":"2026-06-07T13:30:50.878Z","changelog":"Full rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.","fileCount":3,"zipByteSize":5993},{"version":"0.1.0","createdAt":"2026-05-16T17:50:05.575Z","changelog":"- Initial release of the google-maps-places skill. - Enables searching places, geocoding, routing, and accessing Google Maps data via chat. - Integrates with ClawLink for secure connection and credential management—no separate Google API setup required. - Provides clear setup and usage instructions, including pairing and tool discovery steps. - Enforces best practices around permission checks, confirmation for sensitive actions, and live tool capability validation.","fileCount":3,"zipByteSize":3538}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:google-maps-places","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T19:17:25.581Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-google-maps-places/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T11:16:19.793Z","emptyReason":null},"readme":"Skill: Google Maps\n\nOwner: hith3sh\n\nSummary: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when u...\n\nTags: latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-06-09T07:10:12.420Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.5 | 2026-06-09T06:09:22.405Z | auto\n\n- Updated the Google Maps brand logo image link for improved resource loading.\n- Removed the redundant skill-card.md file.\n- No functional or usage changes to tools or setup flow.\n\nv1.0.4 | 2026-06-09T04:55:58.190Z | auto\n\n- Removed the file skill-card.md to clean up redundant documentation.\n- No changes to functionality or main documentation.\n\nv1.0.1 | 2026-06-08T16:37:32.427Z | auto\n\n- Added a Google Maps brand logo at the top of the documentation for clearer identification.\n- Minor documentation update in SKILL.md; no feature or functional changes.\n- Removed the file: skill-card.md (no longer included in this version).\n\nv0.1.1 | 2026-06-07T13:30:50.878Z | user\n\nFull rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.\n\nv0.1.0 | 2026-05-16T17:50:05.575Z | auto\n\n- Initial release of the google-maps-places skill.\n- Enables searching places, geocoding, routing, and accessing Google Maps data via chat.\n- Integrates with ClawLink for secure connection and credential management—no separate Google API setup required.\n- Provides clear setup and usage instructions, including pairing and tool discovery steps.\n- Enforces best practices around permission checks, confirmation for sensitive actions, and live tool capability validation.\n\nArchive index:\n\nArchive v1.0.6: 3 files, 6002 bytes\n\nFiles: skill-card.md (2476b), SKILL.md (14231b), _meta.json (137b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: google-maps-places\ndescription: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when users want to look up locations, convert addresses to coordinates, or get routing information.\n---\n\n# Google Maps\n\n![Google Maps](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/google-maps.svg?v=2)\n\nAccess Google Maps and Places API via ClawLink managed credentials. Search places, geocode addresses, calculate routes, get directions, and retrieve location data.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-maps-places) for hosted connection flows and credentials so you do not need to configure Google Maps API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Maps |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Maps |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│   Google Maps   │\n│   (User Chat)   │     │   (OAuth)    │     │  (Places/Routes) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Maps      │                       │\n         │                       │  4. Secure Token       │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │  Google  │\n   │  File    │           │ Auth     │           │  Maps    │\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Maps again.\"\n\n## Quick Start\n\n```bash\n# Search for places\nclawlink_call_tool --tool \"googlemaps_search_places\" --params '{\"query\": \"coffee shop nearby\"}'\n\n# Geocode an address\nclawlink_call_tool --tool \"googlemaps_geocode\" --params '{\"address\": \"1600 Amphitheatre Parkway, Mountain View, CA\"}'\n\n# Get directions\nclawlink_call_tool --tool \"googlemaps_directions\" --params '{\"origin\": \"San Francisco, CA\", \"destination\": \"Los Angeles, CA\"}'\n```\n\n## Authentication\n\nAll Google Maps tool calls are authenticated automatically by ClawLink using the user's connected Google account or API key.\n\n**No API key is required in chat.** ClawLink handles credential management and injects it into every Google Maps API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=google-maps and connect Google Maps.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `google-maps` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-maps\n```\n\n**Response:** Returns the live tool catalog for Google Maps.\n\n### Reconnect\n\nIf Google Maps tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-maps\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-maps`\n\n## Security & Permissions\n\n- Access is scoped to location and routing data available through the Google Maps API.\n- **Write operations require explicit user confirmation.** Before executing any call that modifies data, confirm the target and intended effect with the user.\n- Geocoding and routing are read-only operations that do not modify any data.\n\n## Tool Reference\n\n### Place Search & Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_search_places` | Search for places by text query, category, or name | Read |\n| `googlemaps_nearby_search` | Find places near a location within a radius | Read |\n| `googlemaps_place_details` | Get detailed information about a specific place | Read |\n| `googlemaps_find_place` | Find a place from a text query or phone number | Read |\n| `googlemaps_autocomplete` | Get place suggestions as the user types | Read |\n\n### Geocoding & Address Lookup\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geocode` | Convert an address to latitude/longitude coordinates | Read |\n| `googlemaps_reverse_geocode` | Convert coordinates back to a human-readable address | Read |\n\n### Routing & Directions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_directions` | Get directions between origin and destination with multiple modes | Read |\n| `googlemaps_distance_matrix` | Calculate distances and travel times between multiple origins and destinations | Read |\n| `googlemaps_route_matrix` | Get route information for multiple origin-destination pairs | Read |\n\n### Elevation & Terrain\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_elevation` | Get elevation data for locations on the earth | Read |\n| `googlemaps_elevation_along_path` | Get elevation data along a path | Read |\n\n### Time Zone\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_timezone` | Get the time zone for a location | Read |\n\n### Roads\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_snap_to_roads` | Snap GPS points to the nearest road segments | Read |\n| `googlemaps_nearest_roads` | Get the nearest road segments to given coordinates | Read |\n\n### Geolocation\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geolocate` | Get a device's location from cell towers and WiFi nodes | Read |\n\n### Static Maps\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_static_maps` | Generate a static map image with markers and paths | Read |\n\n## Code Examples\n\n### Search for a place\n\n```bash\nclawlink_call_tool --tool \"googlemaps_search_places\" \\\n  --params '{\n    \"query\": \"Italian restaurant\",\n    \"location\": {\"latitude\": 37.7749, \"longitude\": -122.4194},\n    \"radius\": 1000\n  }'\n```\n\n### Geocode an address\n\n```bash\nclawlink_call_tool --tool \"googlemaps_geocode\" \\\n  --params '{\n    \"address\": \"1 Apple Park Way, Cupertino, CA 95014\"\n  }'\n```\n\n### Get directions\n\n```bash\nclawlink_call_tool --tool \"googlemaps_directions\" \\\n  --params '{\n    \"origin\": \"San Francisco, CA\",\n    \"destination\": \"Yosemite National Park, CA\",\n    \"mode\": \"driving\",\n    \"waypoints\": [{\"stop_over\": true, \"location\": \"Palo Alto, CA\"}]\n  }'\n```\n\n### Get distance matrix\n\n```bash\nclawlink_call_tool --tool \"googlemaps_distance_matrix\" \\\n  --params '{\n    \"origins\": [\"San Francisco, CA\", \"Oakland, CA\"],\n    \"destinations\": [\"Los Angeles, CA\", \"San Diego, CA\"],\n    \"mode\": \"driving\"\n  }'\n```\n\n### Get place details\n\n```bash\nclawlink_call_tool --tool \"googlemaps_place_details\" \\\n  --params '{\n    \"place_id\": \"YOUR_PLACE_ID\",\n    \"fields\": [\"name\", \"formatted_address\", \"rating\", \"reviews\", \"opening_hours\"]\n  }'\n```\n\n### Reverse geocode\n\n```bash\nclawlink_call_tool --tool \"googlemaps_reverse_geocode\" \\\n  --params '{\n    \"location\": {\"latitude\": 37.4220, \"longitude\": -122.0841}\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Maps is connected.\n2. Call `clawlink_list_tools --integration google-maps` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-maps`.\n5. If no Google Maps tools appear, direct the user to https://claw-link.dev/dashboard?add=google-maps.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  search → get → geocode → directions → call                 │\n│                                                             │\n│  Example: Search places → Get details → Show results       │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE / HIGH-IMPACT OPERATIONS                             │\n│  describe → preview → confirm → call                        │\n│                                                             │\n│  Example: Describe tool → Preview → User approves            │\n│           → Execute                                          │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes.\n4. For write operations or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Most Google Maps API calls are read-only (geocoding, directions, place search).\n- API quotas and limits apply — check the Google Cloud Console for your project limits.\n- Place IDs are stable but may change over time — always capture fresh IDs from search responses.\n- Routing results depend on real-time traffic data when available.\n- `snap_to_roads` requires a Google Maps Roads API-enabled project.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-maps`. |\n| Missing connection | Google Maps is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-maps. |\n| `NOT_FOUND` | Place or location does not exist. Check the place_id or query. |\n| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| `OVER_QUERY_LIMIT` | API quota exceeded. Wait and retry, or check Google Cloud quotas. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `google-maps`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation)\n- [Places API](https://developers.google.com/places/web-service/overview)\n- [Directions API](https://developers.google.com/maps/documentation/directions/overview)\n- [Geocoding API](https://developers.google.com/maps/documentation/geocoding/overview)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-maps-places\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-maps-places)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.6:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"google-maps-places\",\n  \"version\": \"1.0.6\",\n  \"publishedAt\": 1780989012420\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nGoogle Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when users want to look up locations, convert addresses to coordinates, or get routing information.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and external users use this skill to search places, geocode addresses, retrieve place details, calculate routes, and obtain Google Maps location data through ClawLink-managed Google Maps access.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill asks users to install and persistently allowlist an unpinned third-party ClawLink plugin.\n\nMitigation: Install only after verifying the ClawLink plugin publisher, source, or version, and keep allowlisting limited to the intended plugin.\n\nRisk: Google Maps requests may include precise addresses, routes, nearby searches, or cell/WiFi geolocation data.\n\nMitigation: Require explicit user approval before precise location, route, nearby-search, or geolocation requests, and connect only the intended Google Maps credential.\n\n## Reference(s):\n\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation)\n- [Places API](https://developers.google.com/places/web-service/overview)\n- [Directions API](https://developers.google.com/maps/documentation/directions/overview)\n- [Geocoding API](https://developers.google.com/maps/documentation/geocoding/overview)\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/google-maps-places)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration, API Calls, Markdown]\n\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces tool-selection guidance and ClawLink Google Maps calls; results depend on the live connected Google Maps tool catalog.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.5: 3 files, 6100 bytes\n\nFiles: skill-card.md (2887b), SKILL.md (14018b), _meta.json (137b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: google-maps-places\ndescription: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when users want to look up locations, convert addresses to coordinates, or get routing information.\n---\n\n# Google Maps\n\n![Google Maps](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/google-maps.svg?v=2)\n\nAccess Google Maps and Places API via ClawLink managed credentials. Search places, geocode addresses, calculate routes, get directions, and retrieve location data.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Maps API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Maps |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Maps |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│   Google Maps   │\n│   (User Chat)   │     │   (OAuth)    │     │  (Places/Routes) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Maps      │                       │\n         │                       │  4. Secure Token       │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │  Google  │\n   │  File    │           │ Auth     │           │  Maps    │\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Maps again.\"\n\n## Quick Start\n\n```bash\n# Search for places\nclawlink_call_tool --tool \"googlemaps_search_places\" --params '{\"query\": \"coffee shop nearby\"}'\n\n# Geocode an address\nclawlink_call_tool --tool \"googlemaps_geocode\" --params '{\"address\": \"1600 Amphitheatre Parkway, Mountain View, CA\"}'\n\n# Get directions\nclawlink_call_tool --tool \"googlemaps_directions\" --params '{\"origin\": \"San Francisco, CA\", \"destination\": \"Los Angeles, CA\"}'\n```\n\n## Authentication\n\nAll Google Maps tool calls are authenticated automatically by ClawLink using the user's connected Google account or API key.\n\n**No API key is required in chat.** ClawLink handles credential management and injects it into every Google Maps API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=google-maps and connect Google Maps.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `google-maps` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-maps\n```\n\n**Response:** Returns the live tool catalog for Google Maps.\n\n### Reconnect\n\nIf Google Maps tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-maps\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-maps`\n\n## Security & Permissions\n\n- Access is scoped to location and routing data available through the Google Maps API.\n- **Write operations require explicit user confirmation.** Before executing any call that modifies data, confirm the target and intended effect with the user.\n- Geocoding and routing are read-only operations that do not modify any data.\n\n## Tool Reference\n\n### Place Search & Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_search_places` | Search for places by text query, category, or name | Read |\n| `googlemaps_nearby_search` | Find places near a location within a radius | Read |\n| `googlemaps_place_details` | Get detailed information about a specific place | Read |\n| `googlemaps_find_place` | Find a place from a text query or phone number | Read |\n| `googlemaps_autocomplete` | Get place suggestions as the user types | Read |\n\n### Geocoding & Address Lookup\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geocode` | Convert an address to latitude/longitude coordinates | Read |\n| `googlemaps_reverse_geocode` | Convert coordinates back to a human-readable address | Read |\n\n### Routing & Directions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_directions` | Get directions between origin and destination with multiple modes | Read |\n| `googlemaps_distance_matrix` | Calculate distances and travel times between multiple origins and destinations | Read |\n| `googlemaps_route_matrix` | Get route information for multiple origin-destination pairs | Read |\n\n### Elevation & Terrain\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_elevation` | Get elevation data for locations on the earth | Read |\n| `googlemaps_elevation_along_path` | Get elevation data along a path | Read |\n\n### Time Zone\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_timezone` | Get the time zone for a location | Read |\n\n### Roads\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_snap_to_roads` | Snap GPS points to the nearest road segments | Read |\n| `googlemaps_nearest_roads` | Get the nearest road segments to given coordinates | Read |\n\n### Geolocation\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geolocate` | Get a device's location from cell towers and WiFi nodes | Read |\n\n### Static Maps\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_static_maps` | Generate a static map image with markers and paths | Read |\n\n## Code Examples\n\n### Search for a place\n\n```bash\nclawlink_call_tool --tool \"googlemaps_search_places\" \\\n  --params '{\n    \"query\": \"Italian restaurant\",\n    \"location\": {\"latitude\": 37.7749, \"longitude\": -122.4194},\n    \"radius\": 1000\n  }'\n```\n\n### Geocode an address\n\n```bash\nclawlink_call_tool --tool \"googlemaps_geocode\" \\\n  --params '{\n    \"address\": \"1 Apple Park Way, Cupertino, CA 95014\"\n  }'\n```\n\n### Get directions\n\n```bash\nclawlink_call_tool --tool \"googlemaps_directions\" \\\n  --params '{\n    \"origin\": \"San Francisco, CA\",\n    \"destination\": \"Yosemite National Park, CA\",\n    \"mode\": \"driving\",\n    \"waypoints\": [{\"stop_over\": true, \"location\": \"Palo Alto, CA\"}]\n  }'\n```\n\n### Get distance matrix\n\n```bash\nclawlink_call_tool --tool \"googlemaps_distance_matrix\" \\\n  --params '{\n    \"origins\": [\"San Francisco, CA\", \"Oakland, CA\"],\n    \"destinations\": [\"Los Angeles, CA\", \"San Diego, CA\"],\n    \"mode\": \"driving\"\n  }'\n```\n\n### Get place details\n\n```bash\nclawlink_call_tool --tool \"googlemaps_place_details\" \\\n  --params '{\n    \"place_id\": \"YOUR_PLACE_ID\",\n    \"fields\": [\"name\", \"formatted_address\", \"rating\", \"reviews\", \"opening_hours\"]\n  }'\n```\n\n### Reverse geocode\n\n```bash\nclawlink_call_tool --tool \"googlemaps_reverse_geocode\" \\\n  --params '{\n    \"location\": {\"latitude\": 37.4220, \"longitude\": -122.0841}\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Maps is connected.\n2. Call `clawlink_list_tools --integration google-maps` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-maps`.\n5. If no Google Maps tools appear, direct the user to https://claw-link.dev/dashboard?add=google-maps.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  search → get → geocode → directions → call                 │\n│                                                             │\n│  Example: Search places → Get details → Show results       │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE / HIGH-IMPACT OPERATIONS                             │\n│  describe → preview → confirm → call                        │\n│                                                             │\n│  Example: Describe tool → Preview → User approves            │\n│           → Execute                                          │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes.\n4. For write operations or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Most Google Maps API calls are read-only (geocoding, directions, place search).\n- API quotas and limits apply — check the Google Cloud Console for your project limits.\n- Place IDs are stable but may change over time — always capture fresh IDs from search responses.\n- Routing results depend on real-time traffic data when available.\n- `snap_to_roads` requires a Google Maps Roads API-enabled project.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-maps`. |\n| Missing connection | Google Maps is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-maps. |\n| `NOT_FOUND` | Place or location does not exist. Check the place_id or query. |\n| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| `OVER_QUERY_LIMIT` | API quota exceeded. Wait and retry, or check Google Cloud quotas. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `google-maps`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation)\n- [Places API](https://developers.google.com/places/web-service/overview)\n- [Directions API](https://developers.google.com/maps/documentation/directions/overview)\n- [Geocoding API](https://developers.google.com/maps/documentation/geocoding/overview)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"google-maps-places\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1780985362405\n}\n\nFile v1.0.5:skill-card.md\n\n## Description: <br>\nGoogle Maps and Places API integration for searching places, geocoding addresses, calculating routes, getting directions, and retrieving location data. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and external users use this skill to connect an agent to Google Maps through ClawLink for place search, geocoding, routing, distance, elevation, timezone, road, geolocation, and static map workflows. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Addresses, coordinates, route queries, and device-location signals pass through ClawLink and Google Maps. <br>\nMitigation: Avoid sending sensitive home, workplace, real-time, or third-party location data unless needed, and review ClawLink and Google Maps privacy and retention terms for the use case. <br>\nRisk: The skill requires OAuth or sensitive credential handling through ClawLink-managed connection flows. <br>\nMitigation: Install only when comfortable using ClawLink as a hosted proxy for Google Maps credentials and verify the Google Maps connection before using tools. <br>\nRisk: Incorrect or stale live tool assumptions can lead to failed or inappropriate Google Maps requests. <br>\nMitigation: Use the live ClawLink tool catalog and tool descriptions as the source of truth before unfamiliar, ambiguous, write, or high-impact calls. <br>\n\n\n## Reference(s): <br>\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation) <br>\n- [Places API Documentation](https://developers.google.com/places/web-service/overview) <br>\n- [Directions API Documentation](https://developers.google.com/maps/documentation/directions/overview) <br>\n- [Geocoding API Documentation](https://developers.google.com/maps/documentation/geocoding/overview) <br>\n- [ClawLink](https://claw-link.dev) <br>\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw) <br>\n- [ClawLink Verification](https://claw-link.dev/verify) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON tool-call examples] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May include Google Maps API results, location data, routes, place details, map image requests, and troubleshooting guidance.] <br>\n\n## Skill Version(s): <br>\n1.0.5 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.4: 3 files, 5880 bytes\n\nFiles: skill-card.md (2440b), SKILL.md (14014b), _meta.json (137b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: google-maps-places\ndescription: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when users want to look up locations, convert addresses to coordinates, or get routing information.\n---\n\n# Google Maps\n\n![Google Maps](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/google-maps.svg)\n\nAccess Google Maps and Places API via ClawLink managed credentials. Search places, geocode addresses, calculate routes, get directions, and retrieve location data.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Maps API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Maps |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Maps |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│   Google Maps   │\n│   (User Chat)   │     │   (OAuth)    │     │  (Places/Routes) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Maps      │                       │\n         │                       │  4. Secure Token       │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │  Google  │\n   │  File    │           │ Auth     │           │  Maps    │\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Maps again.\"\n\n## Quick Start\n\n```bash\n# Search for places\nclawlink_call_tool --tool \"googlemaps_search_places\" --params '{\"query\": \"coffee shop nearby\"}'\n\n# Geocode an address\nclawlink_call_tool --tool \"googlemaps_geocode\" --params '{\"address\": \"1600 Amphitheatre Parkway, Mountain View, CA\"}'\n\n# Get directions\nclawlink_call_tool --tool \"googlemaps_directions\" --params '{\"origin\": \"San Francisco, CA\", \"destination\": \"Los Angeles, CA\"}'\n```\n\n## Authentication\n\nAll Google Maps tool calls are authenticated automatically by ClawLink using the user's connected Google account or API key.\n\n**No API key is required in chat.** ClawLink handles credential management and injects it into every Google Maps API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=google-maps and connect Google Maps.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `google-maps` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-maps\n```\n\n**Response:** Returns the live tool catalog for Google Maps.\n\n### Reconnect\n\nIf Google Maps tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-maps\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-maps`\n\n## Security & Permissions\n\n- Access is scoped to location and routing data available through the Google Maps API.\n- **Write operations require explicit user confirmation.** Before executing any call that modifies data, confirm the target and intended effect with the user.\n- Geocoding and routing are read-only operations that do not modify any data.\n\n## Tool Reference\n\n### Place Search & Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_search_places` | Search for places by text query, category, or name | Read |\n| `googlemaps_nearby_search` | Find places near a location within a radius | Read |\n| `googlemaps_place_details` | Get detailed information about a specific place | Read |\n| `googlemaps_find_place` | Find a place from a text query or phone number | Read |\n| `googlemaps_autocomplete` | Get place suggestions as the user types | Read |\n\n### Geocoding & Address Lookup\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geocode` | Convert an address to latitude/longitude coordinates | Read |\n| `googlemaps_reverse_geocode` | Convert coordinates back to a human-readable address | Read |\n\n### Routing & Directions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_directions` | Get directions between origin and destination with multiple modes | Read |\n| `googlemaps_distance_matrix` | Calculate distances and travel times between multiple origins and destinations | Read |\n| `googlemaps_route_matrix` | Get route information for multiple origin-destination pairs | Read |\n\n### Elevation & Terrain\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_elevation` | Get elevation data for locations on the earth | Read |\n| `googlemaps_elevation_along_path` | Get elevation data along a path | Read |\n\n### Time Zone\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_timezone` | Get the time zone for a location | Read |\n\n### Roads\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_snap_to_roads` | Snap GPS points to the nearest road segments | Read |\n| `googlemaps_nearest_roads` | Get the nearest road segments to given coordinates | Read |\n\n### Geolocation\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geolocate` | Get a device's location from cell towers and WiFi nodes | Read |\n\n### Static Maps\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_static_maps` | Generate a static map image with markers and paths | Read |\n\n## Code Examples\n\n### Search for a place\n\n```bash\nclawlink_call_tool --tool \"googlemaps_search_places\" \\\n  --params '{\n    \"query\": \"Italian restaurant\",\n    \"location\": {\"latitude\": 37.7749, \"longitude\": -122.4194},\n    \"radius\": 1000\n  }'\n```\n\n### Geocode an address\n\n```bash\nclawlink_call_tool --tool \"googlemaps_geocode\" \\\n  --params '{\n    \"address\": \"1 Apple Park Way, Cupertino, CA 95014\"\n  }'\n```\n\n### Get directions\n\n```bash\nclawlink_call_tool --tool \"googlemaps_directions\" \\\n  --params '{\n    \"origin\": \"San Francisco, CA\",\n    \"destination\": \"Yosemite National Park, CA\",\n    \"mode\": \"driving\",\n    \"waypoints\": [{\"stop_over\": true, \"location\": \"Palo Alto, CA\"}]\n  }'\n```\n\n### Get distance matrix\n\n```bash\nclawlink_call_tool --tool \"googlemaps_distance_matrix\" \\\n  --params '{\n    \"origins\": [\"San Francisco, CA\", \"Oakland, CA\"],\n    \"destinations\": [\"Los Angeles, CA\", \"San Diego, CA\"],\n    \"mode\": \"driving\"\n  }'\n```\n\n### Get place details\n\n```bash\nclawlink_call_tool --tool \"googlemaps_place_details\" \\\n  --params '{\n    \"place_id\": \"YOUR_PLACE_ID\",\n    \"fields\": [\"name\", \"formatted_address\", \"rating\", \"reviews\", \"opening_hours\"]\n  }'\n```\n\n### Reverse geocode\n\n```bash\nclawlink_call_tool --tool \"googlemaps_reverse_geocode\" \\\n  --params '{\n    \"location\": {\"latitude\": 37.4220, \"longitude\": -122.0841}\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Maps is connected.\n2. Call `clawlink_list_tools --integration google-maps` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-maps`.\n5. If no Google Maps tools appear, direct the user to https://claw-link.dev/dashboard?add=google-maps.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  search → get → geocode → directions → call                 │\n│                                                             │\n│  Example: Search places → Get details → Show results       │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE / HIGH-IMPACT OPERATIONS                             │\n│  describe → preview → confirm → call                        │\n│                                                             │\n│  Example: Describe tool → Preview → User approves            │\n│           → Execute                                          │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes.\n4. For write operations or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Most Google Maps API calls are read-only (geocoding, directions, place search).\n- API quotas and limits apply — check the Google Cloud Console for your project limits.\n- Place IDs are stable but may change over time — always capture fresh IDs from search responses.\n- Routing results depend on real-time traffic data when available.\n- `snap_to_roads` requires a Google Maps Roads API-enabled project.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-maps`. |\n| Missing connection | Google Maps is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-maps. |\n| `NOT_FOUND` | Place or location does not exist. Check the place_id or query. |\n| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| `OVER_QUERY_LIMIT` | API quota exceeded. Wait and retry, or check Google Cloud quotas. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `google-maps`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation)\n- [Places API](https://developers.google.com/places/web-service/overview)\n- [Directions API](https://developers.google.com/maps/documentation/directions/overview)\n- [Geocoding API](https://developers.google.com/maps/documentation/geocoding/overview)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"google-maps-places\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1780980958190\n}\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nGoogle Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users and developers use this skill to search places, geocode addresses, calculate routes, retrieve directions, and work with Google Maps location data through ClawLink-managed credentials. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Precise geolocation, WiFi, or cell tower details can expose sensitive location information. <br>\nMitigation: Provide precise location signals only when the task requires them and confirm where the data will be sent or stored before using geolocation features. <br>\nRisk: The skill relies on OAuth or sensitive credentials managed through ClawLink. <br>\nMitigation: Use the documented connection flow and verify that Google Maps is connected before making tool calls. <br>\n\n\n## Reference(s): <br>\n- [Google Maps ClawHub Page](https://clawhub.ai/hith3sh/google-maps-places) <br>\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation) <br>\n- [Places API Documentation](https://developers.google.com/places/web-service/overview) <br>\n- [Directions API Documentation](https://developers.google.com/maps/documentation/directions/overview) <br>\n- [Geocoding API Documentation](https://developers.google.com/maps/documentation/geocoding/overview) <br>\n- [ClawLink](https://claw-link.dev) <br>\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, shell commands, configuration, API calls, text] <br>\n**Output Format:** [Markdown with inline bash commands and JSON tool parameters] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses ClawLink-managed credentials and live Google Maps tool catalogs when available.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 3 files, 5962 bytes\n\nFiles: skill-card.md (2654b), SKILL.md (14014b), _meta.json (137b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: google-maps-places\ndescription: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when users want to look up locations, convert addresses to coordinates, or get routing information.\n---\n\n# Google Maps\n\n![Google Maps](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/google-maps.svg)\n\nAccess Google Maps and Places API via ClawLink managed credentials. Search places, geocode addresses, calculate routes, get directions, and retrieve location data.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Maps API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Maps |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Maps |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│   Google Maps   │\n│   (User Chat)   │     │   (OAuth)    │     │  (Places/Routes) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Maps      │                       │\n         │                       │  4. Secure Token       │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │  Google  │\n   │  File    │           │ Auth     │           │  Maps    │\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Maps again.\"\n\n## Quick Start\n\n```bash\n# Search for places\nclawlink_call_tool --tool \"googlemaps_search_places\" --params '{\"query\": \"coffee shop nearby\"}'\n\n# Geocode an address\nclawlink_call_tool --tool \"googlemaps_geocode\" --params '{\"address\": \"1600 Amphitheatre Parkway, Mountain View, CA\"}'\n\n# Get directions\nclawlink_call_tool --tool \"googlemaps_directions\" --params '{\"origin\": \"San Francisco, CA\", \"destination\": \"Los Angeles, CA\"}'\n```\n\n## Authentication\n\nAll Google Maps tool calls are authenticated automatically by ClawLink using the user's connected Google account or API key.\n\n**No API key is required in chat.** ClawLink handles credential management and injects it into every Google Maps API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=google-maps and connect Google Maps.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `google-maps` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-maps\n```\n\n**Response:** Returns the live tool catalog for Google Maps.\n\n### Reconnect\n\nIf Google Maps tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-maps\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-maps`\n\n## Security & Permissions\n\n- Access is scoped to location and routing data available through the Google Maps API.\n- **Write operations require explicit user confirmation.** Before executing any call that modifies data, confirm the target and intended effect with the user.\n- Geocoding and routing are read-only operations that do not modify any data.\n\n## Tool Reference\n\n### Place Search & Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_search_places` | Search for places by text query, category, or name | Read |\n| `googlemaps_nearby_search` | Find places near a location within a radius | Read |\n| `googlemaps_place_details` | Get detailed information about a specific place | Read |\n| `googlemaps_find_place` | Find a place from a text query or phone number | Read |\n| `googlemaps_autocomplete` | Get place suggestions as the user types | Read |\n\n### Geocoding & Address Lookup\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geocode` | Convert an address to latitude/longitude coordinates | Read |\n| `googlemaps_reverse_geocode` | Convert coordinates back to a human-readable address | Read |\n\n### Routing & Directions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_directions` | Get directions between origin and destination with multiple modes | Read |\n| `googlemaps_distance_matrix` | Calculate distances and travel times between multiple origins and destinations | Read |\n| `googlemaps_route_matrix` | Get route information for multiple origin-destination pairs | Read |\n\n### Elevation & Terrain\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_elevation` | Get elevation data for locations on the earth | Read |\n| `googlemaps_elevation_along_path` | Get elevation data along a path | Read |\n\n### Time Zone\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_timezone` | Get the time zone for a location | Read |\n\n### Roads\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_snap_to_roads` | Snap GPS points to the nearest road segments | Read |\n| `googlemaps_nearest_roads` | Get the nearest road segments to given coordinates | Read |\n\n### Geolocation\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geolocate` | Get a device's location from cell towers and WiFi nodes | Read |\n\n### Static Maps\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_static_maps` | Generate a static map image with markers and paths | Read |\n\n## Code Examples\n\n### Search for a place\n\n```bash\nclawlink_call_tool --tool \"googlemaps_search_places\" \\\n  --params '{\n    \"query\": \"Italian restaurant\",\n    \"location\": {\"latitude\": 37.7749, \"longitude\": -122.4194},\n    \"radius\": 1000\n  }'\n```\n\n### Geocode an address\n\n```bash\nclawlink_call_tool --tool \"googlemaps_geocode\" \\\n  --params '{\n    \"address\": \"1 Apple Park Way, Cupertino, CA 95014\"\n  }'\n```\n\n### Get directions\n\n```bash\nclawlink_call_tool --tool \"googlemaps_directions\" \\\n  --params '{\n    \"origin\": \"San Francisco, CA\",\n    \"destination\": \"Yosemite National Park, CA\",\n    \"mode\": \"driving\",\n    \"waypoints\": [{\"stop_over\": true, \"location\": \"Palo Alto, CA\"}]\n  }'\n```\n\n### Get distance matrix\n\n```bash\nclawlink_call_tool --tool \"googlemaps_distance_matrix\" \\\n  --params '{\n    \"origins\": [\"San Francisco, CA\", \"Oakland, CA\"],\n    \"destinations\": [\"Los Angeles, CA\", \"San Diego, CA\"],\n    \"mode\": \"driving\"\n  }'\n```\n\n### Get place details\n\n```bash\nclawlink_call_tool --tool \"googlemaps_place_details\" \\\n  --params '{\n    \"place_id\": \"YOUR_PLACE_ID\",\n    \"fields\": [\"name\", \"formatted_address\", \"rating\", \"reviews\", \"opening_hours\"]\n  }'\n```\n\n### Reverse geocode\n\n```bash\nclawlink_call_tool --tool \"googlemaps_reverse_geocode\" \\\n  --params '{\n    \"location\": {\"latitude\": 37.4220, \"longitude\": -122.0841}\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Maps is connected.\n2. Call `clawlink_list_tools --integration google-maps` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-maps`.\n5. If no Google Maps tools appear, direct the user to https://claw-link.dev/dashboard?add=google-maps.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  search → get → geocode → directions → call                 │\n│                                                             │\n│  Example: Search places → Get details → Show results       │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE / HIGH-IMPACT OPERATIONS                             │\n│  describe → preview → confirm → call                        │\n│                                                             │\n│  Example: Describe tool → Preview → User approves            │\n│           → Execute                                          │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes.\n4. For write operations or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Most Google Maps API calls are read-only (geocoding, directions, place search).\n- API quotas and limits apply — check the Google Cloud Console for your project limits.\n- Place IDs are stable but may change over time — always capture fresh IDs from search responses.\n- Routing results depend on real-time traffic data when available.\n- `snap_to_roads` requires a Google Maps Roads API-enabled project.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-maps`. |\n| Missing connection | Google Maps is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-maps. |\n| `NOT_FOUND` | Place or location does not exist. Check the place_id or query. |\n| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| `OVER_QUERY_LIMIT` | API quota exceeded. Wait and retry, or check Google Cloud quotas. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `google-maps`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation)\n- [Places API](https://developers.google.com/places/web-service/overview)\n- [Directions API](https://developers.google.com/maps/documentation/directions/overview)\n- [Geocoding API](https://developers.google.com/maps/documentation/geocoding/overview)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"google-maps-places\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1780936652427\n}\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nGoogle Maps and Places API integration for searching places, geocoding addresses, calculating routes, getting directions, and retrieving location data. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users and developers use this skill to search places, geocode addresses, calculate routes, get directions, and retrieve location data through Google Maps and Places API access managed by ClawLink. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can send map queries, addresses, routes, coordinates, or device-derived location data to Google Maps through ClawLink. <br>\nMitigation: Avoid sending precise home, work, or other sensitive locations unless needed, and disconnect the Google Maps integration or ClawLink plugin when access is no longer wanted. <br>\nRisk: The skill requires OAuth or sensitive credential handling through a connected integration. <br>\nMitigation: Use the managed ClawLink connection flow, verify the Google Maps integration is active before use, and do not paste API keys or credentials into chat. <br>\n\n\n## Reference(s): <br>\n- [Google Maps Skill on ClawHub](https://clawhub.ai/hith3sh/google-maps-places) <br>\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation) <br>\n- [Places API Documentation](https://developers.google.com/places/web-service/overview) <br>\n- [Directions API Documentation](https://developers.google.com/maps/documentation/directions/overview) <br>\n- [Geocoding API Documentation](https://developers.google.com/maps/documentation/geocoding/overview) <br>\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON tool-call examples] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May guide calls that return Google Maps API data such as place results, geocoding results, route details, coordinates, time zones, road matching, and static map outputs.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v0.1.1: 3 files, 5993 bytes\n\nFiles: skill-card.md (2680b), SKILL.md (13895b), _meta.json (137b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: google-maps-places\ndescription: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when users want to look up locations, convert addresses to coordinates, or get routing information.\n---\n\n# Google Maps\n\nAccess Google Maps and Places API via ClawLink managed credentials. Search places, geocode addresses, calculate routes, get directions, and retrieve location data.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Google Maps API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Maps |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Maps |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│   Google Maps   │\n│   (User Chat)   │     │   (OAuth)    │     │  (Places/Routes) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Maps      │                       │\n         │                       │  4. Secure Token       │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │  Google  │\n   │  File    │           │ Auth     │           │  Maps    │\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Maps again.\"\n\n## Quick Start\n\n```bash\n# Search for places\nclawlink_call_tool --tool \"googlemaps_search_places\" --params '{\"query\": \"coffee shop nearby\"}'\n\n# Geocode an address\nclawlink_call_tool --tool \"googlemaps_geocode\" --params '{\"address\": \"1600 Amphitheatre Parkway, Mountain View, CA\"}'\n\n# Get directions\nclawlink_call_tool --tool \"googlemaps_directions\" --params '{\"origin\": \"San Francisco, CA\", \"destination\": \"Los Angeles, CA\"}'\n```\n\n## Authentication\n\nAll Google Maps tool calls are authenticated automatically by ClawLink using the user's connected Google account or API key.\n\n**No API key is required in chat.** ClawLink handles credential management and injects it into every Google Maps API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=google-maps and connect Google Maps.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `google-maps` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration google-maps\n```\n\n**Response:** Returns the live tool catalog for Google Maps.\n\n### Reconnect\n\nIf Google Maps tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=google-maps\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration google-maps`\n\n## Security & Permissions\n\n- Access is scoped to location and routing data available through the Google Maps API.\n- **Write operations require explicit user confirmation.** Before executing any call that modifies data, confirm the target and intended effect with the user.\n- Geocoding and routing are read-only operations that do not modify any data.\n\n## Tool Reference\n\n### Place Search & Discovery\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_search_places` | Search for places by text query, category, or name | Read |\n| `googlemaps_nearby_search` | Find places near a location within a radius | Read |\n| `googlemaps_place_details` | Get detailed information about a specific place | Read |\n| `googlemaps_find_place` | Find a place from a text query or phone number | Read |\n| `googlemaps_autocomplete` | Get place suggestions as the user types | Read |\n\n### Geocoding & Address Lookup\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geocode` | Convert an address to latitude/longitude coordinates | Read |\n| `googlemaps_reverse_geocode` | Convert coordinates back to a human-readable address | Read |\n\n### Routing & Directions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_directions` | Get directions between origin and destination with multiple modes | Read |\n| `googlemaps_distance_matrix` | Calculate distances and travel times between multiple origins and destinations | Read |\n| `googlemaps_route_matrix` | Get route information for multiple origin-destination pairs | Read |\n\n### Elevation & Terrain\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_elevation` | Get elevation data for locations on the earth | Read |\n| `googlemaps_elevation_along_path` | Get elevation data along a path | Read |\n\n### Time Zone\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_timezone` | Get the time zone for a location | Read |\n\n### Roads\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_snap_to_roads` | Snap GPS points to the nearest road segments | Read |\n| `googlemaps_nearest_roads` | Get the nearest road segments to given coordinates | Read |\n\n### Geolocation\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_geolocate` | Get a device's location from cell towers and WiFi nodes | Read |\n\n### Static Maps\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `googlemaps_static_maps` | Generate a static map image with markers and paths | Read |\n\n## Code Examples\n\n### Search for a place\n\n```bash\nclawlink_call_tool --tool \"googlemaps_search_places\" \\\n  --params '{\n    \"query\": \"Italian restaurant\",\n    \"location\": {\"latitude\": 37.7749, \"longitude\": -122.4194},\n    \"radius\": 1000\n  }'\n```\n\n### Geocode an address\n\n```bash\nclawlink_call_tool --tool \"googlemaps_geocode\" \\\n  --params '{\n    \"address\": \"1 Apple Park Way, Cupertino, CA 95014\"\n  }'\n```\n\n### Get directions\n\n```bash\nclawlink_call_tool --tool \"googlemaps_directions\" \\\n  --params '{\n    \"origin\": \"San Francisco, CA\",\n    \"destination\": \"Yosemite National Park, CA\",\n    \"mode\": \"driving\",\n    \"waypoints\": [{\"stop_over\": true, \"location\": \"Palo Alto, CA\"}]\n  }'\n```\n\n### Get distance matrix\n\n```bash\nclawlink_call_tool --tool \"googlemaps_distance_matrix\" \\\n  --params '{\n    \"origins\": [\"San Francisco, CA\", \"Oakland, CA\"],\n    \"destinations\": [\"Los Angeles, CA\", \"San Diego, CA\"],\n    \"mode\": \"driving\"\n  }'\n```\n\n### Get place details\n\n```bash\nclawlink_call_tool --tool \"googlemaps_place_details\" \\\n  --params '{\n    \"place_id\": \"YOUR_PLACE_ID\",\n    \"fields\": [\"name\", \"formatted_address\", \"rating\", \"reviews\", \"opening_hours\"]\n  }'\n```\n\n### Reverse geocode\n\n```bash\nclawlink_call_tool --tool \"googlemaps_reverse_geocode\" \\\n  --params '{\n    \"location\": {\"latitude\": 37.4220, \"longitude\": -122.0841}\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Google Maps is connected.\n2. Call `clawlink_list_tools --integration google-maps` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-maps`.\n5. If no Google Maps tools appear, direct the user to https://claw-link.dev/dashboard?add=google-maps.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  search → get → geocode → directions → call                 │\n│                                                             │\n│  Example: Search places → Get details → Show results       │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE / HIGH-IMPACT OPERATIONS                             │\n│  describe → preview → confirm → call                        │\n│                                                             │\n│  Example: Describe tool → Preview → User approves            │\n│           → Execute                                          │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes.\n4. For write operations or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Most Google Maps API calls are read-only (geocoding, directions, place search).\n- API quotas and limits apply — check the Google Cloud Console for your project limits.\n- Place IDs are stable but may change over time — always capture fresh IDs from search responses.\n- Routing results depend on real-time traffic data when available.\n- `snap_to_roads` requires a Google Maps Roads API-enabled project.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration google-maps`. |\n| Missing connection | Google Maps is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-maps. |\n| `NOT_FOUND` | Place or location does not exist. Check the place_id or query. |\n| `INVALID_ARGUMENT` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| `OVER_QUERY_LIMIT` | API quota exceeded. Wait and retry, or check Google Cloud quotas. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `google-maps`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation)\n- [Places API](https://developers.google.com/places/web-service/overview)\n- [Directions API](https://developers.google.com/maps/documentation/directions/overview)\n- [Geocoding API](https://developers.google.com/maps/documentation/geocoding/overview)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v0.1.1:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"google-maps-places\",\n  \"version\": \"0.1.1\",\n  \"publishedAt\": 1780839050878\n}\n\nFile v0.1.1:skill-card.md\n\n## Description: <br>\nGoogle Maps and Places API integration for searching places, geocoding addresses, calculating routes, getting directions, and retrieving location data. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and OpenClaw users use this skill to access Google Maps and Places capabilities from an agent workflow. It helps with place discovery, address lookup, route planning, distance calculations, elevation, time zone, roads, static maps, and deliberate geolocation requests. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Location, routing, and geolocation requests can expose sensitive place, route, or inferred device-location data. <br>\nMitigation: Invoke Google Maps tools only for user-authorized tasks, and treat googlemaps_geolocate as sensitive because it can infer location from cell tower or WiFi data. <br>\nRisk: The skill requires ClawLink access for Google Maps tools and depends on a connected account or API key. <br>\nMitigation: Install only when ClawLink access is acceptable for the environment, verify the Google Maps connection before use, and review setup commands before applying them. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/hith3sh/google-maps-places) <br>\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation) <br>\n- [Places API](https://developers.google.com/places/web-service/overview) <br>\n- [Directions API](https://developers.google.com/maps/documentation/directions/overview) <br>\n- [Geocoding API](https://developers.google.com/maps/documentation/geocoding/overview) <br>\n- [ClawLink OpenClaw documentation](https://docs.claw-link.dev/openclaw) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, shell commands, configuration, API calls] <br>\n**Output Format:** [Markdown with inline shell commands and JSON tool-call examples] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses live Google Maps tool catalogs and ClawLink-managed credentials; outputs can include location, routing, place, elevation, time zone, roads, geolocation, and static map results.] <br>\n\n## Skill Version(s): <br>\n0.1.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v0.1.0: 3 files, 3538 bytes\n\nFiles: skill-card.md (2541b), SKILL.md (5032b), _meta.json (137b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: google-maps-places\ndescription: Use Google Maps for places, geocoding, routes, distance, directions, and location data - powered by ClawLink.\n---\n\n# Google Maps\n\nWork with Google Maps from chat - search places, geocode addresses, calculate routes, and inspect location data.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Google Maps API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect Google Maps at [claw-link.dev/dashboard?add=google-maps](https://claw-link.dev/dashboard?add=google-maps)\n7. When the user confirms Google Maps is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `google-maps` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting Google Maps\n\nTell the user to open https://claw-link.dev/dashboard?add=google-maps and connect Google Maps there. The page opens the add-connection panel filtered to Google Maps. ClawLink's hosted page runs the provider connection flow. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `google-maps`.\n\n## Using Google Maps tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm Google Maps is connected.\n2. Call `clawlink_list_tools` with integration `google-maps`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-maps`.\n5. If no Google Maps tools appear, direct the user to https://claw-link.dev/dashboard?add=google-maps.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer read, list, search, and get operations before writes.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical Google Maps tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- Search places and points of interest\n- Geocode or reverse geocode addresses\n- Calculate routes, directions, and distances\n- Inspect place details and location metadata\n- Use map data for planning and lookup workflows\n\n## Rules\n\n- Always use ClawLink tools for Google Maps. Do not ask the user for separate Google Maps credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before destructive, external-facing, or bulk write actions.\n- If Google Maps is not connected, direct the user to https://claw-link.dev/dashboard?add=google-maps.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- Google Maps API: https://developers.google.com/maps/documentation\n\nFile v0.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"google-maps-places\",\n  \"version\": \"0.1.0\",\n  \"publishedAt\": 1778953805575\n}\n\nFile v0.1.0:skill-card.md\n\n## Description: <br>\nUse Google Maps for places, geocoding, routes, distance, directions, and location data - powered by ClawLink. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nOpenClaw users and agents use this skill to set up ClawLink and access Google Maps capabilities for place search, geocoding, routing, directions, distance, and location-data workflows. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Google Maps access is brokered through ClawLink and Google, so sensitive location details may be processed outside the chat environment. <br>\nMitigation: Approve only the intended ClawLink device and Google Maps connection, avoid pasting raw credentials, and avoid highly sensitive location details unless the user accepts ClawLink and Google processing them. <br>\nRisk: Available tools and schemas can vary by connected account, permissions, scopes, and the current ClawLink catalog. <br>\nMitigation: List, search, and describe live ClawLink Google Maps tools in the current turn before claiming or using a capability. <br>\nRisk: External-facing, destructive, or bulk actions could have effects outside the chat if a connected tool supports them. <br>\nMitigation: Preview actions and get explicit user confirmation before executing anything marked as requiring confirmation or involving writes, destructive changes, or bulk operations. <br>\n\n\n## Reference(s): <br>\n- [ClawLink](https://claw-link.dev) <br>\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw) <br>\n- [ClawLink Verification](https://claw-link.dev/verify) <br>\n- [Google Maps API Documentation](https://developers.google.com/maps/documentation) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, shell commands, configuration] <br>\n**Output Format:** [Markdown instructions with inline shell commands, tool names, and URLs] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses the live ClawLink tool catalog as the source of truth for available Google Maps actions.] <br>\n\n## Skill Version(s): <br>\n0.1.0 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Google Maps Owner: hith3sh Summary: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when u... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:10:12.420Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic s","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│   Google Maps   │\n│   (User Chat)   │     │   (OAuth)    │     │  (Places/Routes) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Maps      │                       │\n         │                       │  4. Secure Token       │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │  Google  │\n   │  File    │           │ Auth     │           │  Maps    │\n   └──────────┘           └──────────┘           └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# Search for places\nclawlink_call_tool --tool \"googlemaps_search_places\" --params '{\"query\": \"coffee shop nearby\"}'\n\n# Geocode an address\nclawlink_call_tool --tool \"googlemaps_geocode\" --params '{\"address\": \"1600 Amphitheatre Parkway, Mountain View, CA\"}'\n\n# Get directions\nclawlink_call_tool --tool \"googlemaps_directions\" --params '{\"origin\": \"San Francisco, CA\", \"destination\": \"Los Angeles, CA\"}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration google-maps"},{"language":"bash","snippet":"clawlink_call_tool --tool \"googlemaps_search_places\" \\\n  --params '{\n    \"query\": \"Italian restaurant\",\n    \"location\": {\"latitude\": 37.7749, \"longitude\": -122.4194},\n    \"radius\": 1000\n  }'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: google-maps-places\ndescription: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when users want to look up locations, convert addresses to coordinates, or get routing information.\n---\n\n# Google Maps\n\n![Google Maps](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/google-maps.svg?v=2)\n\nAccess Google Maps and Places API via ClawLink managed credentials. Search places, geocode addresses, calculate routes, get directions, and retrieve location data.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-maps-places) for hosted connection flows and credentials so you do not need to configure Google Maps API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Google Maps |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Google Maps |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│   Google Maps   │\n│   (User Chat)   │     │   (OAuth)    │     │  (Places/Routes) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Maps      │                       │\n         │                       │  4. Secure Token       │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │  Google  │\n   │  File    │           │ Auth     │           │  Maps    │\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Google Maps again.\"\n\n## Quick Start\n\n```bash\n# Search for places\nclawlink_call_tool --tool \"googlemaps_search_places\" --params '{\"query\": \"coffee shop nearby\"}'\n\n# Geocode an address\nclawlink_call_tool --tool"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"google-maps-places\",\n  \"version\": \"1.0.6\",\n  \"publishedAt\": 1780989012420\n}"},{"path":"skill-card.md","content":"## Description:\n\nGoogle Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when users want to look up locations, convert addresses to coordinates, or get routing information.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and external users use this skill to search places, geocode addresses, retrieve place details, calculate routes, and obtain Google Maps location data through ClawLink-managed Google Maps access.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill asks users to install and persistently allowlist an unpinned third-party ClawLink plugin.\n\nMitigation: Install only after verifying the ClawLink plugin publisher, source, or version, and keep allowlisting limited to the intended plugin.\n\nRisk: Google Maps requests may include precise addresses, routes, nearby searches, or cell/WiFi geolocation data.\n\nMitigation: Require explicit user approval before precise location, route, nearby-search, or geolocation requests, and connect only the intended Google Maps credential.\n\n## Reference(s):\n\n- [Google Maps Platform Documentation](https://developers.google.com/maps/documentation)\n- [Places API](https://developers.google.com/places/web-service/overview)\n- [Directions API](https://developers.google.com/maps/documentation/directions/overview)\n- [Geocoding API](https://developers.google.com/maps/documentation/geocoding/overview)\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/google-maps-places)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration, API Calls, Markdown]\n\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces tool-selection guidance and ClawLink Google Maps calls; results depend on the live connected Google Maps tool catalog.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when u... Skill: Google Maps Owner: hith3sh Summary: Google Maps and Places API integration. Search places, geocode addresses, calculate routes, get directions, and retrieve location data. Use this skill when u... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:10:12.420Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic s","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1068,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T11:16:19.793Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T11:16:19.793Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T19:17:25.583Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}