360 Secure SkillHub
360 安全技能中心

HotspotSystem

该 Skill 通过 oo CLI 调用 OOMOL 托管的 HotspotSystem 连接器，凭证由服务端注入，用户无需处理原始令牌。提供 7 个只读 action（查询操作员账号、位置、位置选项、客户与订阅者），执行前先用 schema 获取入参结构，再以 JSON 载荷运行并返回结构化结果。

oomol
oomol
热度 51.15
最近更新 2026-09-16 15:36:14
分类：搜索依赖：代码执行 / 第三方 API

安装技能

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

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

HotspotSystem

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

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

oo connector run "hotspotsystem" --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_current_owner — Verify the HotspotSystem API key and return the connected operator account.
  • list_customers — List HotspotSystem customers across all accessible locations.
  • list_location_customers — List HotspotSystem customers for one specific location.
  • list_location_options — List HotspotSystem locations as lightweight id-name options.
  • list_location_subscribers — List HotspotSystem subscribers for one specific location.
  • list_locations — List HotspotSystem locations owned by the authenticated operator.
  • list_subscribers — List HotspotSystem subscribers across all accessible locations.

Safety

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

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

Resources