What makes trek-agent-control notable?

1.1K downloads. Trust evidence available

How should trek-agent-control 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

trek-agent-control

配套 Trek 微信旅行小程序的自动化 Skill，主要面向 WorkBuddy，也兼容 Codex、Claude、OpenClaw、Hermes 等 Agent。通过认证的远程 MCP 研究国内外目的地、读取或修改行程，并把日程、地点、预订、住宿、费用、清单、待办、附件和协作提案安全同步回小程序。Use when WorkBuddy or another agent needs to plan travel, inspect Trek data, synchronize structured itinerary fields, upload tickets, or run safe diagnostics with a user-provided Trek Agent Key. Skill: trek-agent-control Owner: super21-bat Summary: 配套 Trek 微信旅行小程序的自动化 Skill，主要面向 WorkBuddy，也兼容 Codex、Claude、OpenClaw、Hermes 等 Agent。通过认证的远程 MCP 研究国内外目的地、读取或修改行程，并把日程、地点、预订、住宿、费用、清单、待办、附件和协作提案安全同步回小程序。Use when WorkBuddy or another agent needs to plan travel, inspect Trek data, synchronize structured itinerary fields, upload tickets, or run safe diagnostics with a user-provided Trek Agent Key. Tags: latest:1.1.3 Ve

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.1.3

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.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: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.1.3release · observed Sep 23, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s175az8cpcd2sbfx08gyskcaen83hyj2:trek-agent-control

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-super21-bat-trek-agent-control/snapshot"

Documentation

CLAWHUB

145,148 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: trek-agent-control
description: 配套 Trek 微信旅行小程序的自动化 Skill，主要面向 WorkBuddy，也兼容 Codex、Claude、OpenClaw、Hermes 等 Agent。通过认证的远程 MCP 研究国内外目的地、读取或修改行程，并把日程、地点、预订、住宿、费用、清单、待办、附件和协作提案安全同步回小程序。Use when WorkBuddy or another agent needs to plan travel, inspect Trek data, synchronize structured itinerary fields, upload tickets, or run safe diagnostics with a user-provided Trek Agent Key.
---

# Trek Agent Control

Control the user's real Trek data through MCP. Treat web research and Trek synchronization as separate phases: research first, then show a concrete change preview, then write and read back.

## Product workspace

Trek 微信旅行小程序是用户查看、编辑、导航、分享和协作的行程工作区；本
Skill 是它的 Agent 自动化层。用户先在小程序创建行程和独立 Agent Key，
Agent 再研究资料并把结构化结果同步回同一行程。不要创建与小程序脱离的第二份
行程数据，也不要把聊天回答误报成已同步。

![微信扫码打开 Trek 旅行小程序](https://raw.githubusercontent.com/super21-bat/trek-agent-control/main/assets/trek-miniapp-code.png)

当前二维码为测试阶段入口，是否可直接进入以微信侧体验权限为准。

## Connect

1. Never paste the `trek_` key into files, prompts, logs, screenshots, commits, or shell history intended for sharing.
2. Prefer the agent's native Streamable HTTP MCP support. Configure:
- URL: `https://api.superd.fun/mcp`
- Header: `Authorization: Bearer <user-key>`
3. Use the Trek CLI to install/sync this Skill, verify the connection, and diagnose failures:

```bash
npm install -g https://github.com/super21-bat/trek-agent-control/archive/refs/heads/main.tar.gz
trek config init --api-key 'trek_...' --url 'https://api.superd.fun/mcp'
trek skill sync --global
trek doctor
```

The mini program presents this to ordinary users as two steps: copy once, then send the copied bundle to WorkBuddy. WorkBuddy should complete installation, configuration, Skill sync, and `doctor` without asking the user to run commands manually. Treat the whole bundle as a secret. If native remote MCP is unavailable or unreliable, execute all operations through `trek`; it calls the same MCP endpoint. Read [references/configuration.md](references/configuration.md) for runtime details.

## Fast paths for common user requests

Do not load the large-planning workflow for these small writes. Use the exact
recipe, then stop:

- “加到待定/候选地点”：resolve the trip with `list_trips`, then run
`trek add-pending <trip-id> <title> [--place-id <saved-place-id>]` or call
native MCP `add_pending_place`. If the place already exists in 收藏, pass its
`placeId`; the server links/reuses that place instead of creating a duplicate.
For a newly researched candidate, include a short stable `description` and a
representative `imageUrl` when available; put the trip-specific recommendation
in `reason`. A name plus address alone is not enough context for group voting.
`apply_trip_change` with `action: "add_pending"` remains a compatible fallback.
Never use `create_place` for 待选/候选/待决定.
- “设置行程封面”：run `trek set-cover <trip-id>
<absolute-image>` or call native MCP `apply_trip_change` with `action:
"set_cover"`. The server owns upload, binding and readback as one

_meta.json

{
  "ownerId": "kn70axt20cegjzmp4nnsrs1fmx82khb0",
  "slug": "trek-agent-control",
  "version": "1.1.3",
  "publishedAt": 1790151980760
}

references/configuration.md

# Runtime configuration

## WorkBuddy first

The mini program gives the user only two steps: tap “创建并复制”, then send the copied bundle to WorkBuddy. WorkBuddy must complete the commands, Skill sync, and `doctor` itself. Do not ask a non-technical user to choose between MCP and CLI.

Use native Streamable HTTP MCP when WorkBuddy exposes it. Otherwise use the CLI fallback from the same copied bundle.

## Native Streamable HTTP MCP

Use the runtime's secret manager for `TREK_MCP_TOKEN`. The common configuration shape is:

```json
{
"mcpServers": {
"trek": {
"type": "streamable-http",
"url": "https://api.superd.fun/mcp",
"headers": {
"Authorization": "Bearer ${TREK_MCP_TOKEN}"
}
}
}
}
```

Runtimes may spell the type `http`, `streamable_http`, or `streamable-http`. Do not copy the key into a shared JSON file if that runtime cannot expand environment variables.

## Universal shell fallback

Requirements: Node.js 18 or newer and outbound HTTPS.

The mini program provides the endpoint, commands, and one-time key in one copied Agent access bundle. Do not split or repost that bundle. `trek config init` stores the key in `~/.trek/config.json` with mode `0600` on POSIX systems.

The public bootstrap source is the repository's stable branch tarball. Do not use
the `github:owner/repo` npm shorthand for global installation: some npm versions
link it to a temporary clone and leave a broken `trek` command after cleanup.
After `@trek-cn/cli` is published to npm, the shorter
`npm install -g @trek-cn/cli@latest` command may replace the GitHub install.

Optional environment overrides:

- `TREK_CONFIG`: custom config path.
- `TREK_MCP_TOKEN`: override the stored key.
- `TREK_MCP_URL`: defaults to `https://api.superd.fun/mcp`.
- `TREK_MCP_TIMEOUT_MS`: per-request timeout, default `20000`.
- `TREK_MCP_RETRIES`: retry count for 429/502/503/504 and network errors, default `7`.

## Other compatible agents

Codex, Claude, OpenClaw, Hermes and other terminal-capable agents follow the same connection sequence:

1. Install the CLI and run `trek skill sync --global`.
2. Run `trek config init` with the user's one-time key.
3. Add the native MCP block when supported.
4. Otherwise allow the agent to execute `trek ...`.
5. Run `doctor`; require `ok: true`, a protocol version, a positive tool count, and successful `list_trips` before giving write access.

`trek skill sync --global` delegates common Agent locations to the installed
Skills runner. Trek also installs real copies into detected WorkBuddy
`~/.workbuddy/skills/trek-agent-control` and Hermes
`~/.hermes/skills/trek-agent-control` directories. Start a new WorkBuddy task or
restart the Hermes gateway after syncing. A cross-directory symlink is not
enough for Hermes: it

references/field-guide.md

# Dynamic tool and field guide

Always discover the live schemas with `tools/list`. The server evolves and the live schema is authoritative.

## Core read path

- `list_trips`: identify accessible trips.
- `get_trip_summary`: trip, top-level deduplicated places, days, assignments, reservations, accommodations, budget, packing items and bags, todos, notes and members.
- Relevant `list_*`: obtain full records before editing or deleting.

## Common write groups

- Trip: `create_trip`, `update_trip`, `delete_trip`.
- Schedule: day, place and assignment tools.
- Search: `search_place` with `query`, explicit `market` (`china` or `global`), and either a Mainland `region` or overseas ISO `countryCode`.
- Decisions: `*_trip_proposal` and collaboration polls.
- Logistics: reservation and accommodation tools.
- Money: budget item, member, payer and settlement tools.
- Preparation: packing and todo tools.
- Collaboration: note, poll and chat tools when enabled.

## Idempotency keys for agent reasoning

The MCP tools do not promise a universal idempotency token. Before creating, compare:

- trip: normalized title + start/end dates
- place: normalized name + address + coordinates
- assignment: day ID + place ID + start time
- reservation: type + title + linked day/place
- accommodation: place + start/end day
- cost: category + name + amount
- packing/todo: normalized name
- note: normalized title

Reuse/update a match instead of creating a duplicate.

## Saved and pending place visibility

- 收藏 and 待决定 share the same place facts: name, address, description, notes,
image, website and phone. Moving between the two states must preserve them.
- For a researched candidate, `description` answers “what is this place”; `reason`
answers “why consider it for this trip”. Do not put both meanings into one field.
- Include a representative image only when its source is usable and stable. Never
fabricate a photo URL. A candidate without verified media may omit `imageUrl`,
but should still have a concise description whenever facts are available.
- Verify rich candidate fields with `list_trip_proposals`; verify 收藏 fields with
`list_places`. Do not report synchronization if the description was dropped.

## Itinerary detail and ticket fields

The mini program opens an itinerary detail sheet when the user taps a day assignment. To make agent-written plans useful there:

- Route fields by ownership instead of putting everything into one note:

| User meaning | MCP field/tool | Mini program visibility |
| --- | --- | --- |
| Instructions for this specific visit | `update_assignment_time.notes` | `本次安排` in the assignment detail |
| Start/end time for this visit | `create_and_assign_place.place_time` / `.end_time` for a new place; `assign_place_to_day.place_time` / `.end_time` for a saved place; `update_assignment_time` for later edits | Time shown on that day's assignment, not a reusable place field |
| Stable POI introduction | `create_place.description` / `update_place.

references/workflows.md

# Research and synchronization workflows

## Research a new trip

1. Collect hard constraints: travelers, ages, accessibility, origin, dates, fixed bookings, work/school windows, budget and transport.
2. Verify time-sensitive claims online. Prefer official attraction, venue, carrier, hotel, government and map sources.
3. Use `search_place` for each real destination. In Mainland China pass `market: "china"` and an administrative region such as `深圳` or `清远`; overseas pass `market: "global"` and a two-letter country code such as `JP` or `FR`.
4. Design each day around geography, opening windows, heat/rain, meals, rest and transfer buffers. Extract every planned POI/activity into `expectedAssignmentsByDate`; do not leave locations only in narrative text.
5. Mark every item as confirmed, recommended, optional or pending confirmation.
6. Preview the plan before creating data.

## Create or update a trip

1. `list_trips` and normalize titles/dates to detect an existing trip.
2. Create only when no match exists; otherwise use the current trip ID.
3. `get_trip_summary` and map its day IDs to ISO dates.
4. Create/reuse places, then assign every expected POI/activity to the correct day with start/end time, duration, transport mode and assignment notes. New place: `create_and_assign_place`; existing place: `assign_place_to_day`. Pass `place_time`/`end_time` in that same creation call when known; both fields belong to the daily assignment. Use `update_assignment_time` only for later edits. A CLI batch can therefore contain one create action per visit without referencing a previous action's assignment ID.
5. Add reservations/accommodations only from evidence. Accommodation tools create a date range, not a daily assignment; if the hotel/check-in is part of the visible daily plan, also assign the hotel place to that day.
6. Add costs as estimates unless receipts/orders establish actual values.
7. Add packing items for traveler and destination needs.
8. Add todos for unresolved bookings, deadlines, safety checks and missing documents. Use due dates and priority.
9. Add collaboration notes for cross-cutting instructions that must remain visible.
10. When adding a trip cover or place image, upload the image, write the returned authenticated `file.url` to `trip.cover_image` or `place.image_url`, and verify both values on readback. A successful file upload without the entity field is incomplete.
11. Read back and compare each date's normalized assignment place names/IDs to `expectedAssignmentsByDate`. Any planned day with zero assignments, any expected place missing, or any POI present only in day-note text is a failed synchronization. Fix it before reporting completion. Intentional rest/location-free travel days must be marked explicitly.

Save the full expected checklist as a JSON object when using the bundled audit command. An empty array explicitly marks a rest/location-free day:

```json
{
"2026-09-23": ["金门大桥", "Presidio"],
"2026-09-24": [],
"2026-09-25":

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.