Template

Skill t3chnaztea/home-assistant-skills/template

Agent skills for Home Assistant: connection doctrine, instance mapping, verified automations, and price/LLM-driven triggers. Claude Code plugin marketplace included.

Install

npx -y skills add t3chnaztea/home-assistant-skills --skill template

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when [the specific situations, symptoms, and phrases that should trigger this skill]. Pack the words someone would actually type or think when they hit this problem. Describe ONLY when to use it, never summarize the workflow inside. Keep the whole frontmatter under 1024 characters. End by naming what this skill is NOT for, pointing at the sibling skill that covers it.

SKILL.md

2.4 KB, 441 tokens by cl100k_base, as published. Nobody here has run it

HA Yourskill

One or two sentences: what this skill covers and that it assumes the connection lanes, env pattern, and doctrine from ha-connect. Cross-reference sibling skills by name (ha-context-map, ha-automations, ha-external-triggers) rather than repeating their content.

Guidelines for a good HA skill

Delete this section in your real skill; it's guidance for authoring.

Name: ha-<area>, lowercase and hyphens only. The directory name MUST equal the frontmatter name.
Description: starts with "Use when…", lists concrete triggers and keywords, ends with a "not for X, use Y" pointer. No workflow summary (an agent will follow the description instead of reading the body).
Markdown only. This collection ships doctrine and fenced curl/ssh/YAML recipes, not scripts. The agent writes throwaway code per task; recipes stay honest and adaptable where scripts rot.
Original prose only. Don't paste from the Home Assistant docs; write the lesson the docs don't teach, and link the docs as the canonical manual.
Parameterize everything instance-specific. <HA_HOST> or homeassistant.local, never a real IP; $HA_TOKEN from env, never a literal; generic entity ids (light.living_room, media_player.tv, climate.thermostat), never your actual house.
Verify against ground truth. Every write ends with reading the entity or config back and showing before/after. Show the reader how to confirm the change, not just make it.
Keep SKILL.md under ~500 lines; push heavy detail into references/*.md.

Overview

What this is and the core principle in 1–2 sentences.

When to use

Symptoms and situations (bullets). When NOT to use.

[Your sections]

Quick-reference recipes, one worked example, the specific traps you learned. One excellent example beats five generic ones.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.