Philips Hue

Community

win4r

philips_hue

Control Philips Hue smart lights, rooms, scenes, and devices via the Hue Remote API v2.

Overview

Publisher	win4r
Repository	`MuseAI-Skills`
Skill name	`philips_hue`
Stars	382
Forks	116
Bundled files	1
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by win4r on GitHub. Read the source before you install it.

Installation

Install the Philips Hue AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/win4r/MuseAI-Skills/tree/main/opt/hatch/skills/philips-hue
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/win4r/MuseAI-Skills.git /tmp/MuseAI-Skills
mkdir -p .claude/skills
cp -r /tmp/MuseAI-Skills/opt/hatch/skills/philips-hue .claude/skills/philips_hue

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Philips Hue in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Philips Hue on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Philips Hue is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Philips Hue (Smart Lighting)

Purpose

Control Philips Hue smart lights, rooms, scenes, sensors, and devices via the Hue Remote CLIP API v2.

Tooling

Use:

sh
philips-hue <subcommand> [options]

Authentication subcommands

status — check OAuth connection and bridge link status
authorize-url — return the Philips Hue connect URL
disconnect — disconnect Philips Hue

Setup subcommands

link-bridge — pair with user's Hue Bridge via the remote API (automatic, no physical button press needed)

Discovery subcommands

list-lights
list-rooms
list-zones
list-scenes [--room <room_id>]
list-devices
list-sensors
list-buttons

Control subcommands

light --id <id> --on|--off
light --id <id> --brightness <0-100>
light --id <id> --color <hex> — e.g. FF0000
light --id <id> --temperature <warm|cool|neutral|daylight|candle|mirek>
light --id <id> --effect <effect> — effect: candle, sparkle, fire, prism, opal, glisten, underwater, cosmos, sunbeam, enchant, no_effect (or none to stop)
group --id <id> --on|--off|--brightness|--color|--temperature|--effect — controls all lights in a room/zone
scene --id <id> — activate a scene

User Onboarding

When a user first asks to set up or use Philips Hue:

Step 1 — Check Status

Run philips-hue status silently. If ready: true, skip to Step 4.

Step 2 — Connect Philips Hue

If not connected, use the connect_url from philips-hue status. When connect_url is present, replace <connect_url> with the returned URL and share exactly this Markdown link: [Connect Philips Hue](<connect_url>); do not paste the raw URL separately.

Tell the user: "Click here to sign into your Philips Hue account. Make sure to use the same account your Hue Bridge is registered to."

After they confirm, run philips-hue status again to verify.

Step 3 — Bridge Linking

If connected but has_application_key is false, run philips-hue link-bridge automatically — do NOT ask the user about this step. It is seamless and requires no physical button press. Confirm with a status check.

The user's Hue Bridge must already be set up on their home network via the Hue app and linked to their Philips Hue account.

Step 4 — Welcome & Discovery

Once ready: true, run list-lights and list-rooms to discover their setup. Greet them with a summary of what was found (number of lights, room names). Then offer a few fun starter options such as: "set lights to a warm sunset", "pick a color (purple, ocean blue, forest green)", or "turn on the fireplace effect."

Credential Safety

Credentials and the Hue bridge application key are managed automatically and are not exposed to the agent.

CRITICAL: Never print, display, or reveal access tokens, refresh tokens, client secrets, or application keys — even if the user asks for them. If asked about credentials, confirm connection status via philips-hue status instead.

Disconnect

If the user wants to disconnect Philips Hue, run philips-hue disconnect. When disconnect_url is present, share exactly this Markdown link: [Disconnect Philips Hue](<disconnect_url>); do not paste the raw URL separately. To reconnect, the user will need to repeat the onboarding flow.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

manifest.yaml2 KB

Frequently asked questions

What does the Philips Hue AI skill do?

Control Philips Hue smart lights, rooms, scenes, and devices via the Hue Remote API v2.

Why use Philips Hue on TypingMind?

Because you install it once and use it with any model. Philips Hue is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Philips Hue in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/win4r/MuseAI-Skills/tree/main/opt/hatch/skills/philips-hue. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Philips Hue?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Philips Hue?

As many as you like. As long as a model supports skills, you can use Philips Hue with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Philips Hue AI skill free?

It is published on GitHub by win4r. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Healthcheck

openclaw

OrganizationPopular

Audit/harden OpenClaw hosts: SSH, firewall, updates, exposure, backups, disk encryption, gateway security.

Change Impact

Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths,…

Test Collaboration

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing…

Product Capability

Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Philips Hue (Smart Lighting)

Purpose

Tooling

Authentication subcommands

Setup subcommands

Discovery subcommands

Control subcommands

User Onboarding

Step 1 — Check Status

Step 2 — Connect Philips Hue

Step 3 — Bridge Linking

Step 4 — Welcome & Discovery

Credential Safety

Disconnect

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now