How do I install the Home Assistant Integration Knowledge skill?

Run npx skillmds@latest add tomevault-io/home-assistant-integration-knowledge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Home Assistant Integration Knowledge safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Home Assistant Integration Knowledge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Home Assistant Integration Knowledge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Home Assistant Integration Knowledge?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Home Assistant Integration Knowledge by tomevault-io

Name: Home Assistant Integration Knowledge
Author: tomevault-io

Home Assistant Integration Knowledge

Everything you need to know to build, test and review Home Assistant Integrations. If you're looking at an integration, you must use this as your primary reference. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

File Locations

Integration code: ./homeassistant/components/<integration_domain>/
Integration tests: ./tests/components/<integration_domain>/

General guidelines

When looking for examples, prefer integrations with the platinum or gold quality scale level first.
Polling intervals are NOT user-configurable. Never add scan_interval, update_interval, or polling frequency options to config flows or config entries.
Do NOT allow users to set config entry names in config flows. Names are automatically generated or can be customized later in UI. Exception: helper integrations may allow custom names.

The following platforms have extra guidelines:

Diagnostics: platform-diagnostics.md for diagnostic data collection
Repairs: platform-repairs.md for user-actionable repair issues

Integration Quality Scale

When validating the quality scale rules, check them at https://developers.home-assistant.io/docs/core/integration-quality-scale/rules
When implementing or reviewing an integration, always consider the quality scale rules, since they promote best practices.

Template scale file: ./script/scaffold/templates/integration/integration/quality_scale.yaml

How Rules Apply

Check manifest.json: Look for "quality_scale" key to determine integration level
Bronze Rules: Always required for any integration with quality scale
Higher Tier Rules: Only apply if integration targets that tier or higher
Rule Status: Check quality_scale.yaml in integration folder for:
- done: Rule implemented
- exempt: Rule doesn't apply (with reason in comment)
- todo: Rule needs implementation

Testing Requirements

Tests should avoid interacting or mocking internal integration details. For more info, see https://developers.home-assistant.io/docs/development_testing/#writing-tests-for-integrations

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: home-assistant-integration-knowledgedescription: Everything you need to know to build, test and review Home Assistant Integrations. If you're looking at an integration, you must use this as your primary reference. Use when this capability is needed.---## File Locations- **Integration code**: `./homeassistant/components/<integration_domain>/`- **Integration tests**: `./tests/components/<integration_domain>/`## General guidelines- When looking for examples, prefer integrations with the platinum or gold quality scale level first.- Polling intervals are NOT user-configurable. Never add scan_interval, update_interval, or polling frequency options to config flows or config entries.- Do NOT allow users to set config entry names in config flows. Names are automatically generated or can be customized later in UI. Exception: helper integrations may allow custom names.The following platforms have extra guidelines:- **Diagnostics**: [`platform-diagnostics.md`](platform-diagnostics.md) for diagnostic data collection- **Repairs**: [`platform-repairs.md`](platform-repairs.md) for user-actionable repair issues## Integration Quality Scale- When validating the quality scale rules, check them at https://developers.home-assistant.io/docs/core/integration-quality-scale/rules- When implementing or reviewing an integration, always consider the quality scale rules, since they promote best practices.Template scale file: `./script/scaffold/templates/integration/integration/quality_scale.yaml`### How Rules Apply1. **Check `manifest.json`**: Look for `"quality_scale"` key to determine integration level2. **Bronze Rules**: Always required for any integration with quality scale3. **Higher Tier Rules**: Only apply if integration targets that tier or higher4. **Rule Status**: Check `quality_scale.yaml` in integration folder for: - `done`: Rule implemented - `exempt`: Rule doesn't apply (with reason in comment) - `todo`: Rule needs implementation## Testing Requirements- Tests should avoid interacting or mocking internal integration details. For more info, see https://developers.home-assistant.io/docs/development_testing/#writing-tests-for-integrations---> Converted and distributed by [TomeVault](https://tomevault.io/claim/home-assistant) — claim your Tome and manage your conversions.

Frequently asked questions