What makes Trail Nav via Telegram (low-token) notable?

1K downloads. Trust evidence available

How should Trail Nav via Telegram (low-token) be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Trail Nav via Telegram (low-token)

Offline-capable hiking route guidance via Telegram location messages (OpenClaw). Use when building/operating an LLM agent workflow that: (1) imports a GPX/KM... Skill: Trail Nav via Telegram (low-token) Owner: jack4world Summary: Offline-capable hiking route guidance via Telegram location messages (OpenClaw). Use when building/operating an LLM agent workflow that: (1) imports a GPX/KM... Tags: latest:0.3.2 Version history: v0.3.2 | 2026-02-21T17:08:00.122Z | user Fix one-click OpenClaw config patcher to use new skills schema (skills.load.extraDirs + skills.entries), with leg

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.0k

Updated

Oct 11, 2026

Version

0.3.2

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1K downloadsadoption · observed Oct 11, 2026
Latest release: 0.3.2release · observed Feb 21, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17dbynx3685n8nahtb3yet8ks8586em:trail-nav-telegram

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: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-jack4world-trail-nav-telegram/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

74,416 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: trail-nav-telegram
description: "Offline-capable hiking route guidance via Telegram location messages (OpenClaw). Use when building/operating an LLM agent workflow that: (1) imports a GPX/KML route, (2) answers 'am I off-route / which way should I go' with low-token fixed outputs, (3) scrapes/publicly discovers route links from 2bulu track_search, and (4) prepares trip risk checklists + gear lists for an overnight hike."
---

# Trail Nav via Telegram (low-token)

## Goals
- Use Telegram (iOS) as the UI: user sends **location** + short commands.
- Keep token usage minimal: do **all geometry calculations deterministically**, use LLM only for optional wording.
- Respect access controls: **do not bypass logins/captchas** on external sites.

## Quick workflow
1) **Import route** (GPX/KML) → build a compact RoutePack (simplified polyline + bbox + endpoints).
2) **Bind** route to the chat (`/use <routeId>`).
3) **Guide**: user sends location (or `/g` + location) → reply with 2-line output (machine line + Chinese template).

## Token-saving rules (hard)
- Never send full KML/GPX text into the LLM context.
- Parse route once; store `routeId` + simplified points.
- Output is fixed schema (see references/guide-protocol.md).
- Cache per-chat state: `activeRouteId`, `lastIdx`.

## External discovery (2bulu)
Two supported modes:

1) **Public discovery (no login)**
- Only scrape **public list/search pages** (e.g. `/track/track_search.htm`, `/track/search-<keyword>.htm`).
- Store: title + url + scraped_at.

2) **Manual-login assist (optional)**
- If the user manually logs in (WeChat/QQ/etc.) in a persistent browser profile, automation may proceed **within that same profile**.
- Login/captcha steps must be completed by the user. Do **not** bypass access controls.

Preferred alternative (often simplest): ask the user to export/send the **GPX/KML file via Telegram**; then operate purely on the user-provided route file.

## Safety reminders
- Provide explicit **no-signal** / SOS guidance. See references/safety-checklist.md.
- Encourage “hard cutoffs” for overnight hikes (time, wind/fog, hydration).

## Bundled resources
- Scripts:
  - `scripts/scrape_2bulu_tracks.js` list-page scraper → JSON/CSV + screenshot
  - `scripts/parse_2bulu_kml.js` parse KML → stats + geojson + routepack
  - `scripts/render_route_map.js` render route HTML+PNG map for sharing
  - `scripts/render_route_map_annotated.js` render annotated map (GeoJSON + alerts) to HTML+PNG
  - `scripts/guide_route.js` deterministic off-route guidance from GeoJSON + current location (outputs the 2-4 line guide protocol)
  - `scripts/weather_alert.js` deterministic weather change alert (Open-Meteo) for day_hike/summit_camp/trail_run modes
  - `scripts/outsideclaw_setup.sh` one-command install/update outsideclaw repo into ~/.outsideclaw/app/outsideclaw
  - `scripts/generate_openclaw_snippet.js` prints an OpenClaw config snippet pointing to the installed outsideclaw skill
  - `scripts/patch_openclaw_confi

_meta.json

{
  "ownerId": "kn78xejze79zk1q8vrfhe4dk8n80nd6n",
  "slug": "trail-nav-telegram",
  "version": "0.3.2",
  "publishedAt": 1771693680122
}

references/2bulu-notes.md

# 2bulu notes (public scraping)

## Useful pages
- Track search/list: https://www.2bulu.com/track/track_search.htm
- Keyword search results: https://www.2bulu.com/track/search-<urlencoded>.htm

## What is safe to do
- Scrape public list/search results: titles + URLs.
- Treat as discovery links; store minimal metadata.

## Manual login (allowed with user involvement)
- Manual login is allowed: user completes WeChat/QQ login and any captcha in the browser.
- Automation may continue **only in the same persisted browser profile**.

## What to avoid
- Do not bypass login/captcha.
- Track-detail downloads may redirect to login; prefer user-exported GPX/KML sent via Telegram when possible.

## Data quality
- List page may contain duplicate links with query params (e.g. ?tabType=2). Normalize and de-duplicate.

references/gear-list-overnight.md

# Gear list (2-person, 1-night ridge/summit camp)

## Must
- Shelter: tent + stakes + guylines
- Sleep: sleeping bag (rated for windchill) + sleeping pad
- Light: headlamp per person + spare power
- Power: power bank
- Clothing: wind/rain shell + insulation layer + spare base + hat + gloves
- Safety: basic first-aid + emergency blanket + whistle
- Water: assume no refill; carry enough
- Food: dinner + breakfast + trail snacks + 20% buffer

## Strongly recommended
- Extra guylines, stronger stakes, tape/zip ties
- Electrolytes
- Trekking poles

## Optional
- Knee support, camp light, sit pad

references/guide-protocol.md

# Low-token guide protocol (Telegram)

Route ID used in examples: `qiniangshan_jinghua`

## Route acquisition
- Preferred: user exports/sends GPX/KML via Telegram → deterministic parsing.
- Optional: user manually logs in to 2bulu in a persistent browser profile; automation may assist after login (no bypass).

## Commands
- `/use <routeId>` bind route to current chat.
- `/g` guide once. Location-only message may be treated as `/g`.

## Output (2-4 lines)
Line 1 (machine):
`G S:<0|1|2> D:<m> B:<deg><dir> GO:<m> IDX:<n>`

- S: 0=on_route, 1=off_route, 2=arrived
- D: distance to route (m)
- B: bearing degrees + dir (N/NE/E/SE/S/SW/W/NW)
- GO: recommended distance (m) to rejoin/advance
- IDX: nearest point index (for incremental window search)

Line 2 (Chinese template, deterministic):
- on_route: `在路线内（偏离{D}米）。朝{dir}（{B}°）前进约{GO}米。`
- off_route: `你已偏离路线约{D}米。请朝{dir}（{B}°）走约{GO}米回到路线。`
- arrived: `你已接近终点（{D}米内）。建议在此附近确认营地/下撤方向。`

Line 3 (optional alert, if near a key node):
`ALERT <letter>: <message>`

Line 4 (optional weather alert, if enabled and sharp change detected):
`WX ALERT: <CODE> <brief>`

## Defaults
- toleranceM=50
- arrivedM=60
- lookaheadM=120
- bboxGuardM=2000 (if far from bbox, return E:OUT_OF_BBOX)

## Reference implementation
- `scripts/guide_route.js`: given a GeoJSON LineString + (lat,lon) (+ optional lastIdx), prints the 2-3 line response.
  - Add `--alerts references/<route>_alerts.json` to enable key-node alerts.
  - Add `--state /tmp/guide_state.json --cooldown-sec 1800` to dedupe alerts.

## Errors (single line)
- `E:NO_ROUTE`
- `E:OUT_OF_BBOX`
- `E:GPS_BAD`

Github ReposUpdated 2d agoRank 70

AionUi

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!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

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

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.