← 返回 Skills 市场
🔌

Sensibo

作者 OOMOL · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ 安全检测通过
29
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install oo-sensibo
功能描述
Sensibo (home.sensibo.com). Use this skill for ANY Sensibo request — reading, creating, and updating data. Whenever a task involves Sensibo, use this skill i...
使用说明 (SKILL.md)

Sensibo

Operate Sensibo through your OOMOL-connected account. This skill calls the sensibo connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Productivity. Exposes 4 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Sensibo. 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 "sensibo" --action "\x3Caction_name>"

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

oo connector run "sensibo" --action "\x3Caction_name>" --data '\x3Cjson>' --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 below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

  • get_ac_states — Get current and previous AC states for one Sensibo device.
  • get_device — Get detailed information for one Sensibo device.
  • list_devices — List Sensibo devices linked to the authenticated user.
  • set_ac_state — Set the full AC state for one Sensibo device.

Safety

  • Read actions (get / list / search) are safe to run directly.
  • Create, update, send, or post actions change Sensibo state — confirm the exact payload and effect with the user before running.
  • Delete or remove actions are destructive — 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: \x3Chttps://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 — Sensibo 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=sensibo
    
  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

安全使用建议
Install this if you are comfortable using OOMOL as the bridge to your Sensibo account. Before allowing write actions, confirm the exact device and AC state payload, and treat the optional oo CLI installer command as code from the internet that should come from a trusted OOMOL source.
能力标签
requires-sensitive-credentials
能力评估
Purpose & Capability
The stated purpose, metadata, action files, and commands all align around operating Sensibo through the OOMOL oo CLI. The only write action is set_ac_state, which is clearly described as changing AC state.
Instruction Scope
Instructions tell the agent to inspect the live schema, use the sensibo connector actions, and confirm exact payloads before state-changing actions. The broad trigger language is bounded to Sensibo-related requests.
Install Mechanism
First-time setup includes curl|bash and PowerShell iex installers for the oo CLI, but they are disclosed, HTTPS-based, and only recommended after an oo command is missing rather than run proactively.
Credentials
Allowed tooling is limited to Bash(oo *), which fits the OOMOL connector workflow. No unrelated filesystem access, arbitrary shell guidance, or hidden network flow is present in the artifact.
Persistence & Privilege
Use requires an OOMOL account and a connected Sensibo credential/API key, with credentials injected server-side. The skill itself does not add background workers, persistence, privilege escalation, or local credential scraping.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install oo-sensibo
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /oo-sensibo 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
- Initial release of the `oo-sensibo` skill for operating Sensibo through an OOMOL-connected account using the `sensibo` connector and `oo` CLI. - Added device discovery with `list_devices` to retrieve Sensibo devices linked to the authenticated user. - Added `get_device` for fetching detailed information about a specific Sensibo device. - Added `get_ac_states` for reading current and previous AC states from a Sensibo device. - Added `set_ac_state` for updating the full AC state of a device, with explicit confirmation guidance for state-changing operations.
元数据
Slug oo-sensibo
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Sensibo 是什么?

Sensibo (home.sensibo.com). Use this skill for ANY Sensibo request — reading, creating, and updating data. Whenever a task involves Sensibo, use this skill i... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 29 次。

如何安装 Sensibo?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install oo-sensibo」即可一键安装,无需额外配置。

Sensibo 是免费的吗?

是的,Sensibo 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Sensibo 支持哪些平台?

Sensibo 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Sensibo?

由 OOMOL(@oomol)开发并维护,当前版本 v1.0.0。

💬 留言讨论