Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Control LIFX smart lights via natural language. Toggle, set colors/brightness, activate scenes, create gradients on multi-zone devices.
Control LIFX smart lights via natural language. Toggle, set colors/brightness, activate scenes, create gradients on multi-zone devices.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Control LIFX smart lights via the LIFX HTTP API through natural language.
lifx-api.sh β Bash wrapper for all LIFX API calls scene-status.py β Scene matching and active detection setup.sh β Device discovery and skill configuration
Set your LIFX API token (get one at https://cloud.lifx.com/settings): bash setup.sh <your-token> This discovers your lights, groups, and scenes, then generates a personalized SKILL.md with your device context.
Run bash setup.sh <your-token> to populate this section with your lights, rooms, and scenes. The setup script queries the LIFX API and rewrites this file with your personal device context. Location: (not configured)
(populated by setup.sh)
(populated by setup.sh)
(populated by setup.sh)
bash lifx-api.sh discover Shows all lights organized by room with power state, color, and brightness.
bash lifx-api.sh toggle <selector> Selectors: Individual light: id:<light_id> Group/room: group_id:<group_id> All lights: all
bash lifx-api.sh state <selector> '{"power":"on","color":"blue","brightness":0.75,"duration":1.0}' Color formats: Named: red, blue, green, white, warm white, purple, orange Hex: #ff6b35 Kelvin: kelvin:2700 (warm) to kelvin:6500 (cool daylight) HSB: hue:240 saturation:1.0 Always include "power":"on" and a brightness value when setting colors, or lights with brightness 0 will stay invisible.
bash lifx-api.sh scene <scene_uuid>
bash lifx-api.sh group-toggle <group_id>
Multi-zone devices support individually addressable zones. Create gradients by setting different zone ranges: bash lifx-api.sh state 'id:<light_id>|0-4' '{"power":"on","color":"purple","brightness":1.0,"duration":1.0}' bash lifx-api.sh state 'id:<light_id>|5-9' '{"power":"on","color":"red","brightness":1.0,"duration":1.0}' The pipe character in zone selectors is automatically URL-encoded by the script.
python3 scene-status.py all # Show all active scenes python3 scene-status.py check <uuid> # Check specific scene
bash lifx-api.sh list # Full JSON bash lifx-api.sh groups # Summary by room
When user says a room name, match it to the group IDs in the device context above. Default brightness to 1.0 (100%) when setting colors unless user specifies otherwise. Default duration to 1.0 seconds for smooth transitions. For "turn off" commands, use {"power":"off"} β don't toggle (toggling is ambiguous). For "turn on" commands, use {"power":"on","brightness":1.0} to ensure visibility. When asked about what's on/what scene is active, use the scene-status tool or discover command. Be conversational about results: "Done, bedroom is now blue at 75%" not "API returned 207".
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.