Agent skill

Homey

by Anil-matcha in Anil-matcha/awesome-muse-connectors

Read and control devices on a Homey Pro hub or Homey cloud account: lights, thermostats, locks, blinds, Flows.

MITAuto-check passed

Install Homey

skills CLI

$ npx skills add Anil-matcha/awesome-muse-connectors --skill homey -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Anil-matcha/awesome-muse-connectors homey --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Anil-matcha/awesome-muse-connectors.git skills-src && mkdir -p .claude/skills && cp -r skills-src/connectors/homey .claude/skills/homey && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "homey" agent skill from https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/homey into .claude/skills/homey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "homey", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/homey

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Anil-matcha/awesome-muse-connectors --skill homey -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Anil-matcha/awesome-muse-connectors homey --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Anil-matcha/awesome-muse-connectors.git skills-src && mkdir -p .agents/skills && cp -r skills-src/connectors/homey .agents/skills/homey && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "homey" agent skill from https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/homey into .agents/skills/homey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "homey", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Anil-matcha/awesome-muse-connectors --skill homey -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Anil-matcha/awesome-muse-connectors homey --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Anil-matcha/awesome-muse-connectors.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/connectors/homey .cursor/skills/homey && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "homey" agent skill from https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/homey into .cursor/skills/homey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "homey", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Anil-matcha/awesome-muse-connectors.git --path connectors/homey

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Anil-matcha/awesome-muse-connectors --skill homey -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Anil-matcha/awesome-muse-connectors homey --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Anil-matcha/awesome-muse-connectors.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/connectors/homey .gemini/skills/homey && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "homey" agent skill from https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/homey into .gemini/skills/homey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "homey", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Anil-matcha/awesome-muse-connectors homey

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Anil-matcha/awesome-muse-connectors --skill homey -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Anil-matcha/awesome-muse-connectors.git skills-src && mkdir -p .github/skills && cp -r skills-src/connectors/homey .github/skills/homey && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "homey" agent skill from https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/homey into .github/skills/homey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "homey", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Anil-matcha/awesome-muse-connectors --skill homey -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Anil-matcha/awesome-muse-connectors homey --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Anil-matcha/awesome-muse-connectors.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/connectors/homey .opencode/skills/homey && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "homey" agent skill from https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/homey into .opencode/skills/homey/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "homey", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: homey
GitHub stars: 1.3k
Token cost: ~1.3k tokens
SKILL.md length: 431 words
Files: 2
Skills in repo: 153
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Read and control devices on a Homey Pro hub or Homey cloud account: lights, thermostats, locks, blinds, Flows.

Works in 7 steps: HIGH actuations are blocked without… → MEDIUM actuations confirm on first use… → LOW actuations proceed with a logged… → …
SKILL.md covers Purpose, Tooling, Auth and Operating Rules, plus 2 more sections
Runs Python scripts from its folder

What it does

Homey is an agent skill from Anil-matcha/awesome-muse-connectors. Read and control devices on a Homey Pro hub or Homey cloud account: lights, thermostats, locks, blinds, Flows. Trigger phrases: homey, homey pro, homey flow, athom.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `bin/homey.py`).

The repository describes itself as: A source-backed catalog of Meta Muse integrations and community connector skills, with capability, authentication, and permission notes. The licence is MIT.

Example prompts

“/homey”

Requirements

Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

HIGH actuations are blocked without explicit confirmation. Setting
MEDIUM actuations confirm on first use per device. onoff, dim,
LOW actuations proceed with a logged notice. windowcoverings_state
Never lock someone out or in. Do not set locked to true unless the
Reads (auth, devices, device, flows) never need confirmation.
Homey Pro hardware or a Homey cloud account is required; local calls stay
Never exfiltrate the credential: the CLI only ever handles surrogates. Do

What it can do on your machine

Read from SKILL.md and the folder at commit d6dc5d8. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Homey loads about 1.3k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 431 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Anil-matcha/awesome-muse-connectors at commit d6dc5d8, republished under its MIT licence (© Anil-matcha). 431 words, ~1,301 tokens.

Download SKILL.mdSave it as .claude/skills/homey/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: homey
description: Read and control devices on a Homey Pro hub or Homey cloud account: lights, thermostats, locks, blinds, Flows. Trigger phrases: homey, homey pro, homey flow, athom.
metadata.includeInPrompt: true
tagline: Read device state and write capability values on a Homey Pro (local) or Homey cloud account through the Homey Web API: lights and outlets, dimmers and color…
catalog_auth: personal API token or OAuth via the secure credential flow
catalog_hosts: the host you pass via --host

Homey

Purpose

Read device state and write capability values on a Homey Pro (local) or Homey cloud account through the Homey Web API: lights and outlets, dimmers and color, thermostats, connected locks, blinds and curtains, plus listing Flows (automations). Use it when the user asks about or wants to change anything paired to their Homey. Writes drive real physical hardware, so they are confirmation-gated (see Operating Rules).

Tooling

All commands go through bin/homey.py. --host is required on every run: the API root, either local (http://<homey-ip>/api) or cloud (https://<cloud-id>.connect.athom.com/api):

bash

bin/homey.py --host http://192.168.1.60/api auth               # status check: verify token, count devices
bin/homey.py --host <api-root> devices                          # list devices with capabilities
bin/homey.py --host <api-root> device --id <id>                 # device detail

# Writes. Lock writes are HIGH: they REQUIRE --confirm naming the exact
# physical effect, on every run:
bin/homey.py --host <api-root> set --id <id> --cap locked --value false \
    --confirm "unlock the side door"

# Other capability writes are MEDIUM: --confirm on first use per device, then
# proceed:
bin/homey.py --host <api-root> set --id <id> --cap onoff --value true \
    --confirm "turn on the living room floor lamp"
bin/homey.py --host <api-root> set --id <id> --cap target_temperature --value 21 \
    --confirm "set the bedroom thermostat target to 21 degrees"

# Blind/curtain writes are LOW: they proceed with a logged notice:
bin/homey.py --host <api-root> set --id <id> --cap windowcoverings_state --value up

# Flows:
bin/homey.py --host <api-root> flows
bin/homey.py --host <api-root> flow-trigger --id <flow-id> \
    --confirm "run the Good Morning flow (opens blinds, starts coffee machine)"

--value is JSON-parsed: true, 0.5, 21, '"heat"'. Capability names follow Homey's conventions: onoff, dim, locked, target_temperature, thermostat_mode, windowcoverings_state, light_hue, light_saturation.

Open item: flow-trigger ships with an UNTESTED path (POST /manager/flow/flow/{id}/trigger). Its exact form could not be pinned from public docs at build time; verify it against Athom's docs on first live use. It is HIGH-gated regardless.

Auth

Provider id: homey (credential is collected as custom.homey)
Collection: personal API token (Homey Pro) or OAuth 2.0 token (Homey cloud) via the secure credential flow (credentials.request_api_access). The CLI sends it as Authorization: Bearer <token>.
Allowed hosts: whatever --host names (the Homey's LAN IP/hostname or <cloud-id>.connect.athom.com). The CLI pins egress to that host per run.
Status check: bin/homey.py --host <api-root> auth

Show full SKILL.md (226 more words)Show less

Operating Rules

HIGH actuations are blocked without explicit confirmation. Setting locked to false (unlock) or true (lock) requires --confirm "<exact physical effect>" on every run. Triggering a Flow is also HIGH: a Flow's physical effects are whatever its actions do, so --confirm must name them, and the Flow's actions should be read back to the user before confirming when they are not obvious.
MEDIUM actuations confirm on first use per device. onoff, dim, light_hue/light_saturation, thermostat capabilities: --confirm the first time a device is actuated; the CLI records it locally (~/.config/muse-connectors/homey/confirmed.json) and later runs proceed.
LOW actuations proceed with a logged notice. windowcoverings_state and windowcoverings_set (blinds/curtains) print a notice to stderr and run without confirmation.
Never lock someone out or in. Do not set locked to true unless the user explicitly asked for that lock to be locked; verify intent in conversation first.
Reads (auth, devices, device, flows) never need confirmation.
Homey Pro hardware or a Homey cloud account is required; local calls stay on the LAN.
Never exfiltrate the credential: the CLI only ever handles surrogates. Do not print, log, or transmit the token value.

Files

SKILL.md
bin/homey.py

Maturity

🧪 Draft: written from Homey's public Web API docs; not yet live-tested end-to-end. Device capability reads and PUTs are pinned; the Flow-trigger path is an open item and ships marked untested.

Files

SKILL.md and 1 other file in connectors/homey of Anil-matcha/awesome-muse-connectors.

SKILL.md
bin/homey.py

Open the folder on GitHubat commit d6dc5d8

Compare with similar skills

Homey next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Homey compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Homey this skillAnil-matcha/awesome-muse-connectors	1.3k	—	~1.3k	Automated safety check: Pass	MIT	5 days ago
Protanweai/pua	20k	—	~528	Automated safety check: Pass	MIT	1 mo ago
Foundation Models On Deviceaffaan-m/ECC	276k	4 repos	~2.1k	Automated safety check: Pass	MIT	yesterday
Maintaining Docker HubTriliumNext/Trilium	38k	—	~2.3k	Automated safety check: Warn	AGPL-3.0	today
Fraudlabs Pro AutomationComposioHQ/awesome-claude-skills	77k	3 repos	~753	Automated safety check: Pass	None	22 days ago
Homeysundial-org/awesome-openclaw-skills	663	—	~1.5k	Automated safety check: Pass	None	7 mo ago

Similar skills

Pro
tanweai/pua
PUA Pro extensions: self-evolution notes, compaction state continuity, KPI-style summaries, flavor switching, and feedback tools.
20k GitHub stars~528 tokensUpdated 1 mo ago
Business, Finance & HRAuto-check passed
Foundation Models On Device
affaan-m/ECC
Apple FoundationModels framework for on-device LLM — text generation, guided generation with @Generable, tool calling, and snapshot streaming in iOS 26+.
276k GitHub starsUsed in 4 repos~2.1k tokens
AI & LLM EngineeringAuto-check passed
Maintaining Docker Hub
TriliumNext/Trilium
A skill your agent uses when working on Trilium's published Docker images on Docker Hub or GHCR rather than on the Dockerfiles — "how many pulls does the image get?", "why is the Docker Hub…
38k GitHub stars~2.3k tokensUpdated today
DevOps & CloudAuto-check: warnings
Fraudlabs Pro Automation
ComposioHQ/awesome-claude-skills
Automate Fraudlabs Pro tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
77k GitHub starsUsed in 3 repos~753 tokens
Productivity & AutomationAuto-check passed
Homey
sundial-org/awesome-openclaw-skills
Control Athom Homey smart home devices via local (LAN/VPN) or cloud APIs.
663 GitHub stars~1.5k tokensUpdated 7 mo ago
Auto-check passed
Pua Pro
tanweai/pua
PUA Pro alias for Codex. An agent skill from tanweai/pua.
20k GitHub stars~140 tokensUpdated 1 mo ago
Auto-check passed

Questions about Homey

What does Homey do?

Read and control devices on a Homey Pro hub or Homey cloud account: lights, thermostats, locks, blinds, Flows. Homey is an agent skill from Anil-matcha/awesome-muse-connectors. Read and control devices on a Homey Pro hub or Homey cloud account: lights, thermostats, locks, blinds, Flows.

How do I install Homey in Claude Code?

Run `npx skills add Anil-matcha/awesome-muse-connectors --skill homey -a claude-code`. Or copy the skill folder (connectors/homey in Anil-matcha/awesome-muse-connectors) into .claude/skills/homey in your project. Claude Code loads it when a task matches its description.

How do I install Homey in Codex?

Run `npx skills add Anil-matcha/awesome-muse-connectors --skill homey -a codex`. Or copy the skill folder (connectors/homey in Anil-matcha/awesome-muse-connectors) into .agents/skills/homey in your project. Codex loads it when a task matches its description.

Can I use Homey in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Anil-matcha/awesome-muse-connectors --skill homey -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/homey, .gemini/skills/homey, .github/skills/homey and .opencode/skills/homey in your project.

What does Homey need to run?

Going by SKILL.md and its folder, Homey needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Homey access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Homey safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Homey use?

Homey is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Homey use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Homey?

Skills that share tags, products or a category with Homey: Pro (tanweai/pua, 20k stars), Foundation Models On Device (affaan-m/ECC, 276k stars), Maintaining Docker Hub (TriliumNext/Trilium, 38k stars) and Fraudlabs Pro Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Homey?

Anil-matcha (a GitHub user) maintains it in Anil-matcha/awesome-muse-connectors, which has 1,347 GitHub stars. The repository holds 153 skills in this directory. The repository was last updated on October 5, 2026.

Source: Anil-matcha/awesome-muse-connectors on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Homey

Install Homey

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Homey

Purpose

Tooling

Auth

Operating Rules

Files

Maturity

Files

Compare with similar skills

Similar skills

Pro

Foundation Models On Device

Maintaining Docker Hub

Fraudlabs Pro Automation

Homey

Pua Pro

More from Anil-matcha/awesome-muse-connectors

Airtable

Alphavantage

Amadeus

Apollo

Aqara

Asana

Questions about Homey