plugins/home-assistant-dev/skills/ha-documentation/SKILL.md
Generate documentation for Home Assistant integrations. Creates README.md, Home Assistant docs pages, and HACS info pages. Use when asked about documentation, README, docs, or making documentation for an integration.
npx skillsauth add l3digital-net/claude-code-plugins ha-documentationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guide for creating comprehensive documentation for custom integrations.
| File | Purpose | Location | |------|---------|----------| | README.md | GitHub landing page | Repository root | | info.md | HACS description | Repository root | | docs/*.md | Extended docs | Optional |
# {Integration Name}
[](https://github.com/hacs/integration)
[](https://github.com/{username}/{repo}/releases)
{Brief description of what the integration does.}
## Features
- Feature 1
- Feature 2
- Feature 3
## Installation
### HACS (Recommended)
1. Open HACS in Home Assistant
2. Click "Integrations"
3. Click ⋮ → "Custom repositories"
4. Add `https://github.com/{username}/{repo}` as category "Integration"
5. Click "{Integration Name}" → "Download"
6. Restart Home Assistant
### Manual
1. Download the latest release
2. Copy `custom_components/{domain}` to your `custom_components` folder
3. Restart Home Assistant
## Configuration
1. Go to **Settings** → **Devices & Services**
2. Click **+ Add Integration**
3. Search for "{Integration Name}"
4. Follow the setup wizard
### Configuration Options
| Option | Default | Description |
|--------|---------|-------------|
| Host | Required | Device IP or hostname |
| Username | Required | Login username |
| Password | Required | Login password |
### Advanced Options
| Option | Default | Description |
|--------|---------|-------------|
| Scan Interval | 30 | Update frequency in seconds |
## Entities
### Sensors
| Entity | Description |
|--------|-------------|
| sensor.{domain}_temperature | Current temperature |
| sensor.{domain}_humidity | Current humidity |
### Switches
| Entity | Description |
|--------|-------------|
| switch.{domain}_power | Main power switch |
## Automation Examples
### Turn on when temperature drops
```yaml
automation:
- alias: "Low Temperature Alert"
trigger:
- platform: numeric_state
entity_id: sensor.{domain}_temperature
below: 18
action:
- service: notify.mobile_app
data:
message: "Temperature dropped below 18°C"
MIT
## HACS info.md Template
```markdown
# {Integration Name}
{Detailed description for HACS store page.}
## What it does
{Explain the integration's purpose and capabilities.}
## Requirements
- Home Assistant 2024.1.0 or later
- {Device/Service name} with firmware X.X or later
## Features
- ✅ Config flow setup
- ✅ Options flow for settings
- ✅ Diagnostics support
- ✅ Automatic reconnection
[](https://github.com/hacs/integration)
[](https://github.com/user/repo/releases)
[](https://github.com/user/repo/releases)
[](LICENSE)
docs-high-level-description: What the integration doesdocs-installation-instructions: How to installdocs-removal-instructions: How to removedocs-actions: Service action documentationdocs-installation-parameters: All setup fields explaineddocs-configuration-parameters: All options explaineddocs-data-update: How/when data updatesdocs-examples: Automation examplesdocs-known-limitations: What doesn't workdocs-supported-devices: Compatible devicesdocs-supported-functions: Feature listdocs-troubleshooting: Common issuesdocs-use-cases: Real-world examplesha-integration-scaffoldha-hacsha-quality-reviewdevelopment
Use when you're stuck or missing current information mid-task - the same command/API/approach failed twice, an error looks like a changed or deprecated API, or you need the current version of something, a fact from after your training cutoff, or to verify something you cannot confirm from the code in context. Starts with a cheap inline lookup and only escalates to a full research sweep if that fails. Do not use for routine pre-emptive checks before ordinary library work - for deliberate research, use /qdev:research.
documentation
Update Outline wiki documentation with implementation-level details from the current session by dispatching the up-docs-propagate-wiki sub-agent. This skill should be used when the user runs /up-docs:wiki.
documentation
Update repository documentation (README.md, docs/, CLAUDE.md) based on session changes by dispatching the up-docs-propagate-repo sub-agent. This skill should be used when the user runs /up-docs:repo.
documentation
Update Notion pages with strategic and organizational context from the current session by dispatching the up-docs-propagate-notion sub-agent. This skill should be used when the user runs /up-docs:notion.