Ha Integration Patterns
v1.0.0Home Assistant custom integration patterns and architectural decisions. Use when building HACS integrations, custom components, or API bridges for Home Assistant. Covers service response data, HTTP views, storage APIs, and integration architecture.
⭐ 0· 983·1 current·1 all-time
by@usimic
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (HA integration patterns) matches the SKILL.md content: service responses, HTTP views, storage, manifest structure, and testing guidance. There are no unrelated requirements (no binaries, env vars, or installs) that conflict with the stated purpose.
Instruction Scope
The instructions stay on-topic: describe HA APIs, code examples, and testing checks. The doc does not ask the agent to read unrelated system files, exfiltrate data, or call unexpected external endpoints. Minor note: examples reference an environment variable ($HA_URL) and mention using auth tokens, but these are illustrative examples relevant to testing and expected for integration development.
Install Mechanism
No install spec and no code files — instruction-only content. This minimizes on-disk execution risk; nothing is downloaded or installed by the skill itself.
Credentials
The skill declares no required environment variables or credentials, which is proportional for documentation/guidance. Example snippets reference an HA_URL and auth tokens for testing, which is expected for Home Assistant integrations but are not requested by the skill itself.
Persistence & Privilege
always is false and the skill is not asking for any elevated or persistent platform privileges. Autonomous model invocation is allowed (platform default) but the skill is instruction-only so it cannot execute code or persist artifacts on its own.
Assessment
This appears to be a straightforward, coherent guide for writing Home Assistant integrations. Before using it in a production project: (1) cross-check examples and breaking-change notes against the official Home Assistant developer docs (the skill provides links); (2) be aware example commands reference an HA_URL and auth token — keep tokens secret and test in a dev instance; (3) the skill has no source/homepage listed — if you plan to copy templates or manifest content into a published integration (HACS), confirm licensing and origin; (4) always review any code you paste into an integration (the guidance is safe, but mistakes in your implementation can introduce vulnerabilities).Like a lobster shell, security has layers — review code before you run it.
latestvk977t8y9xeb6mbbtx90y63g2th80yd2g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.