geo-doctor
GEO 医生:一句话装进 AI 助手,查清豆包、DeepSeek、ChatGPT、Claude 为什么不推荐你,改资料、写内容、再复查。开源中英双语 GEO(生成式引擎优化)skill。
Translation pending
Home Assistant skills for agents
Translation pending
SkillsPythonGitHub @homeassistant-aiSelf-installOwner unconfirmed
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Installable projects can be verified without a deployment domain. Use GitHub sign-in for a personal repository, or the repository verification file above for an organization repository.
Ask about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗An Agent Skill is a portable Markdown knowledge pack that teaches AI coding agents best practices for a specific technology. This repository provides one for Home Assistant, following the open Agent Skills standard. Install it and your agent applies Home Assistant best practices in every session.
home-assistant-best-practices — a decision workflow and anti-pattern table in SKILL.md, backed by reference files the agent loads on demand. It covers:
Agents make a predictable set of mistakes with Home Assistant config — Jinja templates where a native trigger, condition, or helper exists, device_id where entity_id belongs, mode: single on a motion light, renames that silently break dashboards and scripts — and the anti-pattern table names each one with its fix. A typical entry:
# Without the skill: a template condition. HA checks only the Jinja syntax when the automation loads
condition: template
value_template: "{{ states('sensor.living_room_temperature') | float > 25 }}"
# With the skill: a native condition. HA checks every key, the entity ID format and the threshold when it loads
condition: numeric_state
entity_id: sensor.living_room_temperature
above: 25
See Skill Contents for the file-by-file map.
Requires Node.js 22.20+.
npx skills add homeassistant-ai/skills
Works with AI coding agents that support the Agent Skills standard: Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and 70+ others. It installs into the current project; add -g to install it for all projects. To update: npx skills update
Claude Code also accepts the installer above, which places the skill files in your .claude/skills/ directory. The commands below install it as a plugin instead, kept in Claude Code's own plugin cache.
Run each command separately inside Claude Code:
/plugin marketplace add homeassistant-ai/skills
/plugin install home-assistant-skills@home-assistant-skills
Run /reload-plugins or restart Claude Code for the skill to take effect.
Auto-update is off by default for third-party marketplaces. To turn it on, run /plugin, open Marketplaces, choose home-assistant-skills, and select Enable auto-update. To update by hand instead, run /plugin, open Marketplaces, choose home-assistant-skills, and select Update marketplace, then run /reload-plugins. From a shell, run these, then /reload-plugins or restart Claude Code:
claude plugin marketplace update home-assistant-skills
claude plugin update home-assistant-skills@home-assistant-skills
Both apps share the same Customize UI, reached via the left sidebar (Claude Desktop) or claude.ai/customize (browser).
homeassistant-ai/skills (or the full URL, https://github.com/homeassistant-ai/skills) → SyncThis installs the skill as a plugin synced from this repo — no download or zip needed. Sync automatically is on by default, so later updates arrive on their own. To pull an update at once, open Add → Manage marketplaces, then the marketplace's menu → Check for updates.
cd skills && zip -r home-assistant-best-practices.zip home-assistant-best-practices/Once installed, the skill loads on its own whenever the agent works on automations, scripts, scenes, helpers, dashboards, blueprints, or backups — it needs no explicit invocation. Try:
Create an automation that turns on the hallway light when motion is detected and turns it off five minutes after the motion stops.
The home-assistant-best-practices skill includes:
| File | Purpose |
|---|---|
SKILL.md | Decision workflow, anti-pattern table, and pointers to the reference files below |
references/safe-refactoring.md | Safe workflow for renaming entities and their display names, replacing helpers, restructuring automations; display-name override, config-entry, and storage-dashboard blind spots |
references/triggers-and-conditions.md | Purpose-specific and native triggers/conditions, for: durations, trigger IDs |
references/automation-actions.md | Waits, variables, automation modes, control flow (choose, repeat, parallel), error handling (continue_on_error, admin-only actions), disabling automations, measuring elapsed time via last_triggered, Mobile App notify action vs entity, trace retention |
references/helper-selection.md | Built-in helpers vs template sensors (with decision matrix) |
references/template-guidelines.md | When to use templates, when to avoid them, template sensor best practices, reusable custom_templates macros |
See CONTRIBUTING.md for guidelines on writing and submitting skills.
Skill misled your agent? Open an issue with the Report Bad Skill Advice template and let the agent fill it in — it holds the context to trace the failure to its source in the skill.
MIT
references/yaml-only-integrations.md| YAML-only integration types, post-edit actions (reload vs restart) |
references/device-control.md | Actions and targeting, entity_id vs device_id, buttons and remotes, domain-specific patterns |
references/scenes.md | Scene authoring: config shape, snapshot/restore, snapshot-vs-script distinction |
references/dashboard-guide.md | Dashboard layout, view types, strategies, sections, cards, badges, custom cards, CSS styling, HACS / Marketplace |
references/dashboard-cards.md | Built-in card type lookup (core, energy, legacy), where to read a card's fields, entities-card attribute rows |
references/domain-docs.md | Integration and domain documentation (actions, entity attributes); doc pages for specific triggers, conditions, and actions |
references/examples.yaml | Compound examples combining multiple best practices |
references/appdaemon.md | AppDaemon apps: when to use vs. native HA, app structure, actions, scheduling, error handling, safe refactoring impact |
references/blueprint-guide.md | Blueprint authoring: metadata & source_url, inputs & selectors, target vs entity, defaults, !input templating, versioning |
references/backups.md | Full instance backups vs rolling one object back, when to offer a backup before an operation, what an archive contains, encryption keys, restore verification, backup deletion, why a git config repo does not replace a full backup |