home-assistant-local
Skill11 starsChanged 51 days agoMITView on GitHub
Query or control Zhen's Home Assistant devices, including air conditioners, lights, presence, doors, media players, temperatures, and device status. Prefer the local LAN HA API/MCP.
- Reads credentials
In this repository2 other files it gives its agents.
- ego-browserSkill
- media-librarySkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for smart home status or control requests: air conditioners, lights, door sensor, presence, room temperature, media players, …
- Distinctive: line 12
Prefer Codex MCP tools if available:
- Very specific: line 18
Use --noproxy 192.168.1.100 with curl.
- Very specific: line 19
Do not use https://your-ha-domain.example.com or ha_run.sh for normal status/control while this Mac is at home.
- Very specific: line 23
Use human-friendly names from config.json and memory/devices.md.
- Distinctive: line 35
After controlling a device, verify the final state before replying.
- Distinctive: line 36
Ask for confirmation before high-impact or sensitive actions.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Home Assistant Local
Use this skill for smart home status or control requests: air conditioners, lights, door sensor, presence, room temperature, media players, curtains, and HA automations.
Routing
- Prefer Codex MCP tools if available:
ha_get_stateha_list_entitiesha_call_service
- Otherwise use
.env:HA_URLshould point to local LAN HA, normallyhttp://192.168.1.100:8123/api.- Use
--noproxy 192.168.1.100with curl.
- Do not use
https://your-ha-domain.example.comorha_run.shfor normal status/control while this Mac is at home. Use those only as explicit fallback if the local LAN API fails.
Device Names
Use human-friendly names from config.json and memory/devices.md.
Common climate entities:
climate.gree— 客厅空调climate.gree_e6d9— 主卧空调climate.studioroom— 书房空调
Control Rules
- For AC on + set temperature, call
climate.turn_onfirst, thenclimate.set_temperature. - For AC off, prefer
climate.set_hvac_modewith{"hvac_mode":"off"}. - After controlling a device, verify the final state before replying.
- Ask for confirmation before high-impact or sensitive actions.
Reply Style
Reply briefly in Chinese. Do not mention curl, API URLs, tokens, scripts, MCP, retries, or internal files unless the user asks how it works.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

