360 Secure SkillHub
360 安全技能中心

Govee

该 Skill 通过 oo CLI 调用 OOMOL 的 govee 连接器，可列出 Govee 设备及其支持的能力、读取单台设备状态、列出灯光与 DIY 场景，并向设备发送电源、亮度、颜色、模式、温度等能力控制指令。凭据由 OOMOL 服务端注入；首次使用需安装 CLI、登录并连接 Govee，写操作与破坏性操作前会提示确认。

oomol
oomol
热度 38.55
最近更新 2026-09-20 11:35:01
分类：自动化依赖：代码执行 / 第三方 API应用场景：工作流 / 自动化脚本

安装技能

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

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

Govee

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

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

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

  • control_capability — Send one documented Govee capability value to a device, such as power, brightness, color, mode, or temperature. [destructive]
  • get_device_state — Get the current state for one Govee device by sku and device id.
  • list_devices — List Govee devices visible to the API key, including each device's supported capabilities.
  • list_diy_scenes — List dynamic DIY scenes available for one Govee device.
  • list_light_scenes — List dynamic light scenes available for one Govee device.

Safety

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

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

Resources