360 Secure SkillHub
360 安全技能中心

Google Maps

该 Skill 通过 OOMOL 的 oo CLI 调用 google_maps 连接器，支持地点自动补全、地点搜索、附近搜索、地点详情、地理编码、反向地理编码、路线计算和路线矩阵。它依赖 OOMOL 账号与 Google Maps 连接，凭据由服务端注入；所有动作均为读取，不含写入或删除。

oomol
oomol
热度 15.61
最近更新 2026-09-15 13:41:36
分类：搜索依赖：代码执行 / 第三方 API应用场景：旅行 / 推荐 / 研究 / 数据处理

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-google-maps
Metadata
name
oo-google-maps
description
Google Maps (mapsplatform.google.com). Use this skill for ANY Google Maps request — searching and reading data. Whenever a task involves Google Maps, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Google Maps","author":"OOMOL","version":"1.0.0","services":["google_maps"],"icon":"https://static.oomol.com/logo/third-party/google_maps.svg"}

Google Maps

Operate Google Maps through your OOMOL-connected account. This skill calls the google_maps connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Google Maps. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "google_maps" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "google_maps" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • autocomplete_places — Return Google Places autocomplete predictions for text input.
  • compute_route_matrix — Compute routes for every origin and destination combination with Google Routes.
  • compute_routes — Compute one or more routes between an origin and destination with Google Routes.
  • geocode_address — Convert an address into geographic coordinates with Google Geocoding.
  • get_place — Get details for a Google Place by place ID.
  • reverse_geocode — Convert geographic coordinates into addresses with Google Geocoding.
  • search_nearby_places — Search Google Places near a geographic point.
  • search_places — Search Google Places using a text query.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Google Maps state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Google Maps is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=google_maps

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources