360 Secure SkillHub
360 安全技能中心

Sherpa

通过 OOMOL 的 oo CLI 调用 Sherpa 连接器，先读取 action 实时 schema，再以 JSON 负载执行，获取行程的个性化旅行限制、签证与证件要求详情或 Markdown 摘要。凭证由 OOMOL 服务端注入，首次使用需安装并登录 oo CLI 并连接 Sherpa。

oomol
oomol
热度 30.77
最近更新 2026-09-15 14:03:26
分类：生活依赖：第三方 API / 代码执行应用场景：旅行 / 摘要总结

安装技能

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

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

Sherpa

Operate Sherpa through your OOMOL-connected account. This skill calls the sherpa 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 Sherpa. 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 "sherpa" --action "<action_name>"

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

oo connector run "sherpa" --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

  • get_trip_details — Retrieve comprehensive personalized travel restrictions and document requirements for an itinerary.
  • get_trip_summary — Retrieve a concise Markdown summary of personalized travel and visa requirements for an itinerary.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Sherpa 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 — Sherpa 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=sherpa

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

Resources