openhue
Control Philips Hue lights, rooms, and scenes via the OpenHue CLI. Turn lights on/off, adjust brightness, color, color temperature, and activate scenes.
Best use case
openhue is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Control Philips Hue lights, rooms, and scenes via the OpenHue CLI. Turn lights on/off, adjust brightness, color, color temperature, and activate scenes.
Teams using openhue should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/openhue/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How openhue Compares
| Feature / Agent | openhue | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Control Philips Hue lights, rooms, and scenes via the OpenHue CLI. Turn lights on/off, adjust brightness, color, color temperature, and activate scenes.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# OpenHue CLI Control Philips Hue lights and scenes via a Hue Bridge from the terminal. ## Prerequisites ```bash # Linux (pre-built binary) curl -sL https://github.com/openhue/openhue-cli/releases/latest/download/openhue-linux-amd64 -o ~/.local/bin/openhue && chmod +x ~/.local/bin/openhue # macOS brew install openhue/cli/openhue-cli ``` First run requires pressing the button on your Hue Bridge to pair. The bridge must be on the same local network. ## When to Use - "Turn on/off the lights" - "Dim the living room lights" - "Set a scene" or "movie mode" - Controlling specific Hue rooms, zones, or individual bulbs - Adjusting brightness, color, or color temperature ## Common Commands ### List Resources ```bash openhue get light # List all lights openhue get room # List all rooms openhue get scene # List all scenes ``` ### Control Lights ```bash # Turn on/off openhue set light "Bedroom Lamp" --on openhue set light "Bedroom Lamp" --off # Brightness (0-100) openhue set light "Bedroom Lamp" --on --brightness 50 # Color temperature (warm to cool: 153-500 mirek) openhue set light "Bedroom Lamp" --on --temperature 300 # Color (by name or hex) openhue set light "Bedroom Lamp" --on --color red openhue set light "Bedroom Lamp" --on --rgb "#FF5500" ``` ### Control Rooms ```bash # Turn off entire room openhue set room "Bedroom" --off # Set room brightness openhue set room "Bedroom" --on --brightness 30 ``` ### Scenes ```bash openhue set scene "Relax" --room "Bedroom" openhue set scene "Concentrate" --room "Office" ``` ## Quick Presets ```bash # Bedtime (dim warm) openhue set room "Bedroom" --on --brightness 20 --temperature 450 # Work mode (bright cool) openhue set room "Office" --on --brightness 100 --temperature 250 # Movie mode (dim) openhue set room "Living Room" --on --brightness 10 # Everything off openhue set room "Bedroom" --off openhue set room "Office" --off openhue set room "Living Room" --off ``` ## Notes - Bridge must be on the same local network as the machine running Hermes - First run requires physically pressing the button on the Hue Bridge to authorize - Colors only work on color-capable bulbs (not white-only models) - Light and room names are case-sensitive — use `openhue get light` to check exact names - Works great with cron jobs for scheduled lighting (e.g. dim at bedtime, bright at wake)
Related Skills
test-oversized-skill
A test fixture skill that exceeds 200 lines with multiple H2/H3 sections for split testing.
interactive-report-generator
Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
agent-os-framework
Generate standardized .agent-os directory structure with product documentation, mission, tech-stack, roadmap, and decision records. Enables AI-native workflows.
OrcaFlex Specialist Skill
```yaml
repo-ecosystem-hygiene
Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.
domain-knowledge-sweep
Systematic multi-source research of an engineering domain. Spawns parent issue → 6 research subissues (Standards, Academic, Industry, LinkedIn-marketing, Code-audit, Synthesis) → gap implementation subissues. Replaces LinkedIn-only extraction with defensible comprehensive sourcing.
subagent-write-verification
Independently verify subagent-claimed file writes with filesystem and git checks before treating the artifact as real, before committing it, and before referencing the path in downstream prompts.
git-operation-serialization-preflight
Before any commit, stash, merge, reset, rebase, or checkout in a multi-agent or shared-checkout environment, run a bounded preflight to detect active git writers and stale index/config locks, then serialize the mutating step under a single-writer guarantee.
public-knowledge-graph-governance
Maintain public-safe knowledge graph artifacts for llm-wiki and similar markdown knowledge bases. Use when changing graph generators, validators, schema docs, weekly freshness checks, or public/private source-scope boundaries.
llm-wiki-weekly-freshness
Class-level governance workflow for keeping llm-wiki-style markdown knowledge bases current, public-safe, graph/index-valid, and useful for code development. Use when reviewing llm-wiki architecture/content, scanning new LLM concepts, maintaining public knowledge graphs, producing an issue roadmap, or running recurring freshness cadence.
llm-wiki-source-extraction-coverage
Doc-type-aware extraction contract for llm-wiki source ingestion with measurable coverage and source-anchored traceability. Use when (1) ingesting a PDF, DOCX, XLSX, PPTX, HTML, or scanned-image source into a wiki `sources/` page, (2) computing the pre-extraction estimate (what fraction of the source we expect to recover) and post-extraction yield (what fraction we actually recovered), (3) anchoring wiki claims back to specific page / paragraph / cell / slide positions in the source so a reviewer can re-verify or revise against the actual document, (4) deciding whether OCR fallback or manual transcription is needed. Codifies workspace-hub's existing OCR fallback chain and python-docx / openpyxl / trafilatura patterns into a format-specific routing table. Companion to research/llm-wiki-page-shape-contract (Rule 7 input-layer pages) and research/llm-wiki — this skill is the defense against silent extraction failure.