Openclaw Skills for LIFX lets you manage lights, scenes, power, colors, and effects through the OOMOL-connected oo CLI without handling raw API tokens.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install oo-lifx
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install oo-lifx using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
This Openclaw Skills package provides a safe, CLI-driven way to operate LIFX devices through an OOMOL-connected account. Instead of calling the LIFX API directly, it uses the oo connector workflow to inspect each action's live schema, then execute validated read or write operations against your account.
The skill is designed for reliable smart-light automation, with clear separation between read actions and state-changing actions. It supports common LIFX tasks like listing lights and scenes, activating scenes, setting color or brightness, toggling power, validating color strings, and turning effects off, while keeping credentials server-side and out of your hands.
oo CLI and connected the LIFX provider in OOMOL.--data to send an empty object when supported.oo connector run "lifx" and capture the returned data and meta.executionId.[write] action changes device state.oo, sign in, reconnect LIFX, or fix billing issues.oo CLI if it is not already available.curl -fsSL https://cli.oomol.com/install.sh | bash
On Windows PowerShell:
irm https://cli.oomol.com/install.ps1 | iex
oo auth login
https://console.oomol.com/app-connections?provider=lifx
OOMOL_INSUFFICIENT_CREDIT error.https://console.oomol.com/billing/token-recharge
oo connector schema "lifx" --action "<action_name>"
oo connector run "lifx" --action "<action_name>" --data '{"selector":"all"}' --json
The skill organizes work around connector actions, live schemas, and execution metadata rather than local files.
| Element | Purpose | Notes |
|---|---|---|
| Connector | lifx |
The OOMOL connector used for all operations |
| Action | activate_scene, list_lights, list_scenes, set_state, toggle_power, turn_effects_off, validate_color |
Must be checked with oo connector schema before use |
| Payload | JSON object passed via --data |
Can be inline JSON or @path/to/file.json |
| Result | { "data": ..., "meta": { "executionId": "..." } } |
Execution ID is returned under meta.executionId |
list_lights, list_scenes, validate_coloractivate_scene, set_statetoggle_power, turn_effects_offmetadata.title: LIFXmetadata.author: OOMOLmetadata.version: 1.0.0metadata.services: lifxallowed-tools: Bash(oo *)[write] actions must be confirmed before execution.[destructive] actions require explicit approval before running.Loading
Openclaw Skills for Pod AI lets you securely inspect schemas and run Pod AI actions through the oo CLI without handling raw tokens.

Openclaw Skills for Minerstat lets you safely read coin, hardware, and pool data through the oo CLI without handling raw credentials.

Openclaw Skills for Octopus Deploy lets you safely inspect deployments, releases, environments, projects, spaces, and tasks through the oo CLI.

Openclaw Skills for Postalytics provides schema-driven CLI access to read campaigns, contacts, templates, and stats through a connected account.

Openclaw Skills for Leonardo.Ai provide a schema-driven CLI workflow to inspect contracts, run actions, and manage generations through a connected OOMOL account.

Openclaw Skills for OCR Web Service lets AI agents inspect schemas, run OCR actions, and extract text safely through the oo CLI.








































