Skills home-assistant-manager
📦
home-assistant-manager
Content revision r1 Medium Risk 🌐 Network access📁 Filesystem access🔑 Env variables⚙️ External commands
Manage Home Assistant Deployments
Home Assistant changes can be risky when deployments, reloads, and dashboards are handled manually. This skill gives Claude, Codex, and Claude Code structured workflows for validation, deployment, testing, and troubleshooting.
Supports: Claude Codex Code(CC)
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "home-assistant-manager" from https://skillstore.io/skills/komal-skynet-home-assistant-manager.md and its manifest at https://skillstore.io/api/skills/komal-skynet-home-assistant-manager/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "home-assistant-manager". User asks to add a front door notification automation.
Expected outcome:
The assistant proposes the automation behavior, identifies required entities, recommends a reload instead of a restart, and lists validation, trigger, log, and notification checks.
Using "home-assistant-manager". User asks why a dashboard does not show in the sidebar.
Expected outcome:
The assistant checks whether the dashboard file exists, whether it is registered, whether a restart is required, and whether the browser cache needs refresh.
Using "home-assistant-manager". User reports a template comparison error.
Expected outcome:
The assistant explains the likely type mismatch, recommends template casting, then outlines how to test the template and confirm logs are clean.
Security Audit
Medium Riskv9 • 7/9/2026 Open versioned report
The skill is not malicious, but it intentionally guides privileged Home Assistant operations through SSH, hass-cli, git, and scp. Confirmed risks center on remote command execution, writing Home Assistant .storage files, persistent token setup, and commands that can affect real devices; many scanner hits were Markdown, template, or screenshot false positives. No prompt injection attempt was found in the reviewed files.
3
Files scanned
1,023
Lines analyzed
33
Review items
0
False positives ignored
Confirmed security concerns (2)
Medium
Long-Lived Home Assistant Token in Shell Profile
The README tells users to add HASS_SERVER and HASS_TOKEN values to shell startup files. A Home Assistant token stored there can be exposed to shells, subprocesses, backups, or accidental sharing.
The setup instructions explicitly name ~/.bashrc or ~/.zshrc and then export HASS_TOKEN on the following line. This is a real secret persistence risk, although it is normal setup guidance rather than malicious behavior.
Medium
Automation Trigger Commands Can Affect Physical Devices
The skill encourages manual Home Assistant automation triggers and service calls during verification. Depending on the target automation, these actions can affect locks, climate, lights, notifications, or other connected devices.
The cited workflow directly invokes automation.trigger and common service-call commands. The impact depends on the user environment, but the physical-device side effect risk is clear.
Capability review items (33)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
Hidden file in home directory
# Set environment variables (add to ~/.bashrc or ~/.zshrc)
The README advises adding Home Assistant environment variables to ~/.bashrc or ~/.zshrc, and the nearby setup includes a long-lived access token. Persisting control tokens in shell startup files increases exposure.
Medium
Hidden file access
# Set environment variables (add to ~/.bashrc or ~/.zshrc)
The README directs users to modify hidden shell startup files for Home Assistant environment variables. This is common setup guidance, but it can persist sensitive access tokens broadly.
Medium
Ruby/shell backtick execution
1. SSH access to Home Assistant instance (`root@homeassistant.local`)
The skill requires SSH access to root@homeassistant.local, enabling privileged remote management of Home Assistant. This is intended functionality, but it can change or restart the user system.
Medium
Ruby/shell backtick execution
2. `hass-cli` installed locally
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
All `hass-cli` commands use environment variables automatically:
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
```bash
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medium
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medium
Ruby/shell backtick execution
Use `scp` for quick testing before committing:
The workflow instructs copying files to the Home Assistant instance with scp. This can overwrite configuration or dashboard files, so it is a real operational risk even though it is not malicious.
Medium
Ruby/shell backtick execution
```bash
The workflow instructs copying files to the Home Assistant instance with scp. This can overwrite configuration or dashboard files, so it is a real operational risk even though it is not malicious.
Medium
Ruby/shell backtick execution
- ✅ Automations: `hass-cli service call automation.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
- ✅ Scripts: `hass-cli service call script.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
- ✅ Scenes: `hass-cli service call scene.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
- ✅ Template entities: `hass-cli service call template.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
- ✅ Groups: `hass-cli service call group.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
- ✅ Themes: `hass-cli service call frontend.reload_themes`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medium
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medium
Ruby/shell backtick execution
```bash
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medium
Ruby/shell backtick execution
```bash
The workflow manually triggers an automation through hass-cli. Triggering automations can send notifications or actuate connected devices, so user confirmation is needed.
Medium
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medium
Ruby/shell backtick execution
```bash
The command reads Home Assistant entity state through authenticated hass-cli access. It is mostly read-only, but it exposes household state data and depends on sensitive credentials.
Medium
Ruby/shell backtick execution
```bash
The command reads Home Assistant entity state through authenticated hass-cli access. It is mostly read-only, but it exposes household state data and depends on sensitive credentials.
Medium
Ruby/shell backtick execution
```bash
The workflow instructs copying files to the Home Assistant instance with scp. This can overwrite configuration or dashboard files, so it is a real operational risk even though it is not malicious.
Medium
Ruby/shell backtick execution
```bash
The workflow instructs copying files to the Home Assistant instance with scp. This can overwrite configuration or dashboard files, so it is a real operational risk even though it is not malicious.
Medium
Ruby/shell backtick execution
```bash
The command reads Home Assistant entity state through authenticated hass-cli access. It is mostly read-only, but it exposes household state data and depends on sensitive credentials.
Medium
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medium
Ruby/shell backtick execution
1. **Always check configuration** before restart: `ha core check`
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medium
Hidden file access
scp .storage/lovelace.control_center root@homeassistant.local:/config/.storage/
This command copies files into Home Assistant .storage over SSH. That can alter dashboard configuration or registry data, so it is sensitive even when used for legitimate dashboard management.
Medium
Hidden file access
scp .storage/lovelace.new_dashboard root@homeassistant.local:/config/.storage/
This command copies files into Home Assistant .storage over SSH. That can alter dashboard configuration or registry data, so it is sensitive even when used for legitimate dashboard management.
Medium
Hidden file access
scp .storage/lovelace_dashboards root@homeassistant.local:/config/.storage/
This command copies files into Home Assistant .storage over SSH. That can alter dashboard configuration or registry data, so it is sensitive even when used for legitimate dashboard management.
Medium
Hidden file access
scp .storage/lovelace.my_dashboard root@homeassistant.local:/config/.storage/
This command copies files into Home Assistant .storage over SSH. That can alter dashboard configuration or registry data, so it is sensitive even when used for legitimate dashboard management.
Low
Hardcoded URL
claude mcp add --transport http context7 https://mcp.context7.com/mcp \
The README configures Claude MCP to use the external Context7 endpoint. This is optional documentation access, but it sends requests and a user API key header to a third-party service.
Risk Factors
🌐 Network access (3)
📁 Filesystem access (8)
🔑 Env variables (1)
⚙️ External commands (88)
SKILL.md:25 SKILL.md:26 SKILL.md:28 SKILL.md:35 SKILL.md:37-47 SKILL.md:47-51 SKILL.md:51-63 SKILL.md:63-71 SKILL.md:71-92 SKILL.md:92-96 SKILL.md:96-98 SKILL.md:98-112 SKILL.md:112-131 SKILL.md:131-132 SKILL.md:132-133 SKILL.md:133-134 SKILL.md:134-135 SKILL.md:135-136 SKILL.md:136-149 SKILL.md:149-152 SKILL.md:152-155 SKILL.md:155-157 SKILL.md:157-160 SKILL.md:160-162 SKILL.md:162-165 SKILL.md:165-167 SKILL.md:167-175 SKILL.md:175-178 SKILL.md:178-181 SKILL.md:181-182 SKILL.md:182-183 SKILL.md:183-187 SKILL.md:187-188 SKILL.md:188-189 SKILL.md:189 SKILL.md:198-200 SKILL.md:200-203 SKILL.md:203-205 SKILL.md:205-219 SKILL.md:219 SKILL.md:224-233 SKILL.md:233-250 SKILL.md:250-261 SKILL.md:261-286 SKILL.md:286-289 SKILL.md:289-296 SKILL.md:296-312 SKILL.md:312-337 SKILL.md:337-342 SKILL.md:342-351 SKILL.md:351-357 SKILL.md:357-365 SKILL.md:365-368 SKILL.md:368-371 SKILL.md:371-380 SKILL.md:380-387 SKILL.md:387-394 SKILL.md:394-397 SKILL.md:397-404 SKILL.md:404-407 SKILL.md:407-413 SKILL.md:413-415 SKILL.md:415 SKILL.md:426-436 SKILL.md:436-442 SKILL.md:442-452 SKILL.md:452-453 SKILL.md:453-454 SKILL.md:454 SKILL.md:455 SKILL.md:462-463 SKILL.md:463-472 SKILL.md:472-474 SKILL.md:474-477 SKILL.md:477-480 SKILL.md:480-483 SKILL.md:483-485 SKILL.md:485-494 SKILL.md:494-516 SKILL.md:516-519 SKILL.md:519-535 SKILL.md:535-538 SKILL.md:538-551 SKILL.md:551-555 SKILL.md:555-584 SKILL.md:584-588 SKILL.md:588-603 SKILL.md:603-623
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/komal-skynet-home-assistant-manager/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/komal-skynet-home-assistant-manager?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/komal-skynet-home-assistant-manager?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/komal-skynet-home-assistant-manager/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/komal-skynet-home-assistant-manager.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
komal-SkyNET. (2026). home-assistant-manager security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/komal-skynet-home-assistant-manager/audits/9BibTeX citation
@techreport{komal-skynet-komal-skynet-home-assistant-manager-2026,
author = {komal-SkyNET},
title = {home-assistant-manager security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/komal-skynet-home-assistant-manager/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "home-assistant-manager security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "komal-SkyNET"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/komal-skynet-home-assistant-manager/audits/9"
identifiers:
- type: other
value: "skillstore:komal-skynet-home-assistant-manager:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 55
Architecture
85
Maintainability
87
Content
71
Community
78
Spec Compliance
What You Can Build
Deploy Home Assistant configuration changes
Plan validation, deployment, reload, restart, and verification steps for YAML, scripts, scenes, and template entities.
Debug automation failures
Use logs, manual triggers, state checks, and template fixes to isolate and resolve automation errors.
Build tablet-friendly Lovelace dashboards
Create dashboard layouts, choose card types, register storage dashboards, and iterate with quick preview workflows.
Try These Prompts
Check my setup
Review my Home Assistant project setup and tell me what SSH, hass-cli, git, and environment prerequisites are missing before I deploy changes.
Deploy an automation safely
Help me create and deploy a Home Assistant automation, then choose the safest reload or restart path and verification steps.
Troubleshoot a dashboard issue
Debug why my Lovelace dashboard is not appearing or has card errors, and guide me through validation, registration, deployment, and browser checks.
Design a full workflow
Create an end-to-end Home Assistant change workflow that covers local edits, validation, rapid testing, git history, deployment, rollback, logs, and user confirmation gates.
Best Practices
- Confirm target host, files, and expected device effects before running SSH, scp, hass-cli, reload, restart, or trigger commands.
- Validate configuration and dashboard syntax before deployment, then review logs and user-visible outcomes after deployment.
- Use scp for temporary iteration, git for stable changes, and backups before editing Home Assistant storage files.
Avoid
- Do not store long-lived Home Assistant tokens in shared shell profiles, repositories, chat logs, or screenshots.
- Do not restart Home Assistant when a targeted reload can safely apply the change.
- Do not overwrite .storage dashboard files or trigger automations without user approval and a rollback plan.
Frequently Asked Questions
What does this skill help with?
It helps plan Home Assistant configuration edits, deployments, automation checks, log review, and Lovelace dashboard workflows.
Does it require access to my Home Assistant server?
Yes. The documented workflows require user-approved SSH access, hass-cli access, and Home Assistant credentials.
Can it create dashboards?
It provides patterns for Lovelace dashboards, storage files, dashboard registration, view selection, and tablet-friendly layouts.
Can it change devices in my home?
It can guide service calls and automation triggers that may affect devices if the user approves those commands.
Is this only for Claude Code?
The skill is written for Claude Code style workflows, and the marketplace metadata also lists Claude and Codex compatibility.
What should I review before using it?
Review credentials, target host, command approvals, backups, generated configuration, and any automation that can affect physical devices.
Developer Details
Author
komal-SkyNETLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
b959ebfd1043a07c0c4378ab94ca4342cb0259f5
Maintenance freshness
7/18/2026
Usage
8 downloads · 236 views
File structure