什么是 geomanic？

Geomanic 是 Openclaw Skills 的强大集成，允许用户与其以隐私为中心的 GPS 追踪数据进行交互。它通过 Geomanic MCP API 提供全面的旅行分析工具。利用此技能，开发人员可以编程访问旅行指标，如总距离、海拔以及分国家/地区的明细数据。

该技能专为重视数据主权的开发人员打造，将原始 GPS 航点转化为具有参考价值的洞察。无论您是构建个人旅行仪表板还是自动化基于位置的报告，Openclaw Skills 生态系统中的 Geomanic 技能都能通过标准化的 JSON-RPC 接口确保安全、结构化地访问您的移动历史记录。

下载入口:https://github.com/openclaw/skills/tree/main/skills/weltspion/geomanic

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

geomanic 应用场景

• 生成特定日期范围内的自动旅行摘要，包括总距离、平均速度和最高海拔。
• 通过编程创建、更新或删除特定航点来清理和管理位置历史记录。
• 通过检索旅途中在各国家停留时间的具体细分来分析国际旅行。
• 将外部 GPS 数据同步到 Geomanic 平台，以维护统一、隐私优先的旅行历史记录。

1. 技能使用存储在 GEOMANIC_TOKEN 环境变量中的 Bearer 令牌初始化与 Geomanic API 的连接。
2. 当调用工具时，该技能会构造一个 JSON-RPC 2.0 请求，其中包含特定方法和所需的参数（如 ISO 8601 时间戳）。
3. 请求通过安全的 POST 请求发送到 Geomanic MCP 端点。
4. API 处理 GPS 数据并返回结构化响应，包括计算得出的指标或航点列表。
5. Openclaw Skills 代理会解析响应，从结果内容中提取相关的旅行数据呈现给用户。

geomanic 配置指南

要在 Openclaw Skills 上开始使用 Geomanic，您必须从 Geomanic 帐户获取 API 密钥。将此密钥设置为环境变量：

export GEOMANIC_TOKEN='your_api_key_here'

您可以通过调用日期范围工具来验证您的设置：

curl -s -X POST https://geomanic.com/api/v1/mcp r
  -H "Content-Type: application/json" r
  -H "Authorization: Bearer $GEOMANIC_TOKEN" r
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_date_range","arguments":{}}}'

geomanic 数据架构与分类体系

Geomanic 技能使用精确的模式组织旅行数据，以确保与 Openclaw Skills 集成的兼容性：

name: geomanic
description: Query and manage GPS travel data from Geomanic — your privacy-first GPS tracking platform.
metadata: {"clawdbot":{"emoji":"??","requires":{"env":["GEOMANIC_TOKEN"]},"primaryEnv":"GEOMANIC_TOKEN","homepage":"https://geomanic.com","source":"https://github.com/monswyk/geomanic-mcp"}}

Geomanic Skill

This skill connects to the Geomanic MCP API to query travel statistics, manage waypoints, and analyze journeys.

Authentication

The API key is stored in the environment variable GEOMANIC_TOKEN. All requests must include it as a Bearer token.

How to call the API

Use curl via the exec tool to send JSON-RPC requests to https://geomanic.com/api/v1/mcp:

curl -s -X POST https://geomanic.com/api/v1/mcp r
  -H "Content-Type: application/json" r
  -H "Authorization: Bearer $GEOMANIC_TOKEN" r
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"TOOL_NAME","arguments":{...}}}'

Available tools

get_statistics

Get aggregated travel statistics for a time period. Returns total distance (km), average/max speed (km/h), altitude, waypoint count, active days, and country breakdown with full/part days.

Required parameters: from (ISO 8601), to (ISO 8601). Optional: suppress_flights (boolean, default true).

Example:

curl -s -X POST https://geomanic.com/api/v1/mcp r
  -H "Content-Type: application/json" r
  -H "Authorization: Bearer $GEOMANIC_TOKEN" r
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_statistics","arguments":{"from":"2026-02-22T00:00:00Z","to":"2026-02-22T23:59:59Z"}}}'

get_date_range

Get the earliest and latest waypoint dates for the user. No parameters required.

curl -s -X POST https://geomanic.com/api/v1/mcp r
  -H "Content-Type: application/json" r
  -H "Authorization: Bearer $GEOMANIC_TOKEN" r
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_date_range","arguments":{}}}'

list_waypoints

List waypoints with optional time range, pagination, and sorting.

Optional parameters: from, to (ISO 8601), limit (default 50, max 200), offset (default 0), order ("asc" or "desc", default "desc").

curl -s -X POST https://geomanic.com/api/v1/mcp r
  -H "Content-Type: application/json" r
  -H "Authorization: Bearer $GEOMANIC_TOKEN" r
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_waypoints","arguments":{"from":"2026-02-22T00:00:00Z","to":"2026-02-22T23:59:59Z","limit":10}}}'

get_waypoint

Get a single waypoint by UUID.

Required: id (string, UUID).

create_waypoint

Create a new GPS waypoint.

Required: timestamp_utc (ISO 8601), latitude (number), longitude (number). Optional: speed_kmh, altitude, heading_deg, device_id.

update_waypoint

Update an existing waypoint by UUID.

Required: id (string, UUID). Optional: latitude, longitude, speed_kmh, altitude, heading_deg, country_iso, place, device_id.

delete_waypoint

Delete a waypoint by UUID.

Required: id (string, UUID).

Important notes

• All dates must be in ISO 8601 format with timezone (use UTC with Z suffix).
• For "today" queries, use the current date with T00:00:00Z to T23:59:59Z.
• The response is JSON-RPC. The actual data is inside result.content[0].text as a JSON string.
• Distance is in kilometers, speed in km/h, altitude in meters.