# 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.

## Install

```bash
npx skillstore add komal-skynet/home-assistant-manager
```

## Metadata

- Status: approved
- Slug: komal-skynet-home-assistant-manager
- Skillstore revision: r1
- Version status: missing
- Tree hash: 1ef82b7b8c7a6ead3abc0222da5d035134e1f708228dd62be220ec15dd8e5e52
- Author: komal-SkyNET
- GitHub username: komal-SkyNET
- License: MIT
- Repository: https://github.com/komal-SkyNET/claude-skill-homeassistant/tree/main/
- Ref: b959ebfd1043a07c0c4378ab94ca4342cb0259f5
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, filesystem, env\_access, external\_commands
- Quality score: 50
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/komal-skynet-home-assistant-manager
- Manifest: https://skillstore.pages.dev/api/skills/komal-skynet-home-assistant-manager/manifest

## Capabilities

- Explains SSH and hass-cli patterns for Home Assistant state checks, service calls, logs, reloads, and restarts.
- Recommends git or scp deployment workflows based on whether changes are final or still being tested.
- Guides automation verification with configuration checks, manual triggers, log review, and outcome confirmation.
- Provides Lovelace dashboard guidance for storage files, dashboard registration, view types, card choices, and tablet layouts.
- Includes Jinja2 template patterns and debugging guidance for common Home Assistant type and card errors.
- Documents quick-reference commands for configuration validation, deployment, dashboard validation, and troubleshooting.

## Use Cases

- 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.

## Prompt Templates

### 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.
```

## Limitations

- Requires an existing Home Assistant instance with SSH access, hass-cli, and valid user-provided credentials.
- Can guide commands that change devices, dashboards, automations, or Home Assistant service state.
- Does not replace backups, least-privilege credential practices, or review of generated configuration before deployment.
- Cannot verify real device behavior unless the assistant has approved access to the user environment.

## 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.

## Anti Patterns

- 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.

## Security Audit

- Audited at: 2026-07-09T16:31:55.131\+00:00
- Summary: 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.

## Stats

- Views: 236
- Downloads: 9
- Favorites: 0
- Popularity score: 0