[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AB1M3SEA8CQPQGSHR61M53":3,"skill-same:01M7AB1M3SEA8CQPQGSHR61M53":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7AB1M3SEA8CQPQGSHR61M53","ha-config-flow",null,"Work on the Home Assistant config flow of this custom integration — the setup UI, options flow, reauthentication, reconfigure, discovery (zeroconf, dhcp, ssdp, bluetooth, usb, mqtt, homekit), subentries, unique IDs, and config entry version migration. Use when asked to \"add a config option\", \"add a setting\", \"ask the user for X during setup\", \"add an options flow\", \"support reauth\", \"add discovery\", \"make the host configurable\", \"migrate the config entry\", or when editing config_flow_handler\u002F, its schemas\u002F and validators\u002F, or manifest discovery matchers. Covers reserved step names, acceptable unique IDs, abort reasons, validation, and the migration contract. SYMPTOMS — load this if you are about to: use a host or IP as the unique ID; create a config entry without validating the connection; store a credential in `entry.options`; read `entry.data[key]` for a key old entries will not have; or change entry data without bumping VERSION\u002FMINOR_VERSION.","amg0\u002Fha_ksenia","amg0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16444411?v=4","01M7AAZDRNF8BXHM6GAN9QWJ41","01M7AAZDSEHKPEWK6PKK22S2NN",0,"MIT","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-config-flow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ha-config-flow\ndescription: >-\n  Work on the Home Assistant config flow of this custom integration — the setup UI, options flow,\n  reauthentication, reconfigure, discovery (zeroconf, dhcp, ssdp, bluetooth, usb, mqtt, homekit), subentries,\n  unique IDs, and config entry version migration. Use when asked to \"add a config option\", \"add a setting\", \"ask\n  the user for X during setup\", \"add an options flow\", \"support reauth\", \"add discovery\", \"make the host\n  configurable\", \"migrate the config entry\", or when editing config_flow_handler\u002F, its schemas\u002F and validators\u002F,\n  or manifest discovery matchers. Covers reserved step names, acceptable unique IDs, abort reasons, validation,\n  and the migration contract. SYMPTOMS — load this if you are about to: use a host or IP as the unique ID; create\n  a config entry without validating the connection; store a credential in `entry.options`; read `entry.data[key]`\n  for a key old entries will not have; or change entry data without bumping VERSION\u002FMINOR_VERSION.\n---\n\n# Work on the config flow\n\nThe config flow is the only supported way to configure a device or service integration (ADR-0010). Everything the user\ncan change lives here, and mistakes here are expensive: `unique_id` and the shape of `entry.data` are effectively\npermanent.\n\n**Read [`blueprint.config_flow.instructions.md`](..\u002F..\u002Finstructions\u002Fblueprint.config_flow.instructions.md)\nfirst.** It is the authoritative rule set: data-vs-options, reserved step names, acceptable unique IDs and their\nnormalisation, schema hygiene, title placeholders, and the migration contract. Copilot injects it automatically when\nyou edit a config flow file; other agents must open it. This skill is the order of operations and the decisions; the\nMUST\u002FNEVER list for each individual flow is in the first reference below.\n\n| File                                                                   | When to read                                                                    |\n| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------- |\n| [`references\u002Fflow-types.md`](references\u002Fflow-types.md)                 | Implementing one flow — user, discovery, reauth, reconfigure, options, subentry |\n| [`references\u002Fdiscovery-matchers.md`](references\u002Fdiscovery-matchers.md) | Writing a `manifest.json` discovery matcher, or using a discovery helper API    |\n| [`references\u002Foauth2.md`](references\u002Foauth2.md)                         | The service authenticates with OAuth2 rather than an API key or a password      |\n| [`references\u002Fmigration.md`](references\u002Fmigration.md)                   | A config entry migration can fail, and the user needs a way to retry it         |\n\n## Package layout\n\nWhere each piece goes. The example ships `__init__.py`, `config_flow.py`, `schemas\u002Fconfig.py` and\n`validators\u002Fcredentials.py`; create the rest when something needs them, rather than leaving empty scaffolding behind.\n\n```text\nconfig_flow_handler\u002F\n├── __init__.py          # exports\n├── config_flow.py       # user, reauth, reauth_confirm, reconfigure, discovery steps\n├── options_flow.py      # post-setup options, only when there is something to tune\n├── handler.py           # logic shared between the flows above\n├── subentry_flow.py     # multi-device \u002F multi-account subentries\n├── schemas\u002F\n│   ├── config.py        # probatio schemas for setup steps\n│   └── options.py       # probatio schemas for the options flow\n└── validators\u002F\n    ├── credentials.py   # \"can we actually talk to it\" checks\n    └── sanitizers.py    # input normalisation (strip, lowercase host, …)\n```\n\nThe top-level `config_flow.py` is a thin shim Home Assistant discovers — leave it alone.\n\n## Adding a config option\n\n1. **Decide data or options** using the table in the instructions file. This is the one irreversible choice here.\n   A polling interval is neither — it is not a field at all. In an integration without options yet, the first real\n   option is when `options_flow.py` and `schemas\u002Foptions.py` get created.\n2. Add the `CONF_*` key to `const.py`.\n3. Add the field to `schemas\u002Fconfig.py` or `schemas\u002Foptions.py` with a selector and a default.\n4. Consume it: coordinator reads `entry.options`, client reads `entry.data`.\n5. Add the `data` and `data_description` translation keys ([`ha-translations`](..\u002Fha-translations\u002FSKILL.md)).\n6. **Handle existing entries** that predate the key — a default at read time, or a `MINOR_VERSION` bump plus migration.\n   This is the step that gets forgotten and breaks upgrades.\n\n## Adding discovery\n\n1. Add the matcher to `manifest.json` — read\n   [`references\u002Fdiscovery-matchers.md`](references\u002Fdiscovery-matchers.md) first, because each protocol has a rule\n   that fails silently when you guess (lowercase-only zeroconf properties, DHCP MACs arriving without separators,\n   VID\u002FPID pairs shared by hundreds of devices):\n\n   ```json\n   \"zeroconf\": [{ \"type\": \"_myservice._tcp.local.\", \"name\": \"blueprint*\" }]\n   ```\n\n2. Implement the matching `async_step_\u003Cmethod>()` following the discovery MUST\u002FNEVER list in\n   [`references\u002Fflow-types.md`](references\u002Fflow-types.md).\n3. Decide what the discovery payload gives you as a stable unique ID. If it offers nothing stable, stop and discuss it\n   — do not fall back to the IP address.\n4. Confirm the flow end-to-end in the UI: the card shows a useful name, a second discovery of the same device aborts,\n   and a device that changed IP updates the existing entry rather than creating a second one.\n\n## Config entry migration\n\nBump `MINOR_VERSION` for additive changes, `VERSION` for restructuring. Read\n[`ha-breaking-changes`](..\u002Fha-breaking-changes\u002FSKILL.md) first — changing entry data affects every existing install.\n\nImplement `async_migrate_entry()` in `custom_components\u002F\u003Cdomain>\u002F__init__.py`:\n\n```python\nasync def async_migrate_entry(hass: HomeAssistant, entry: {ClassPrefix}ConfigEntry) -> bool:\n    \"\"\"Migrate an old config entry.\"\"\"\n    if entry.version == 1 and entry.minor_version \u003C 2:\n        data = {**entry.data, CONF_PORT: DEFAULT_PORT}\n        hass.config_entries.async_update_entry(entry, data=data, minor_version=2)\n    return True\n```\n\nNo downgrade branch and no `return False` — the contract is under\n[Version and Migration](..\u002F..\u002Finstructions\u002Fblueprint.config_flow.instructions.md#version-and-migration); a migration\nthat can fail needs [`references\u002Fmigration.md`](references\u002Fmigration.md).\n\nMigrations must be idempotent and must never delete a key they do not understand. Cover every migration with a test\n([`ha-testing`](..\u002Fha-testing\u002FSKILL.md)).\n\n## Validate\n\n```bash\nscript\u002Flint && script\u002Ftype-check\nscript\u002Fhassfest          # cross-checks every step\u002Ferror\u002Fabort key against translations\nscript\u002Ftest\n```\n\nThen restart Home Assistant and **walk every flow you touched** — add, reconfigure, options, and, by invalidating the\ncredential, reauth. hassfest proves the translation keys exist; only walking the flow proves it is usable. A flow that\npasses CI and dead-ends on the second step is the normal failure here.\n\nWalk it from the terminal first — it is faster, it is repeatable, and it shows the serialised schema Home Assistant\nactually built, which is where defaults and selectors go wrong:\n\n```bash\nscript\u002Fha flow start                              # or --reconfigure\nscript\u002Fha flow step \u003Cflow_id> host=192.0.2.10 username=admin password=secret\nscript\u002Fha flow options                            # then step through it the same way\nscript\u002Fha entries                                 # the entry exists and loaded\n```\n\nEach step prints its `step_id`, any `errors`, and every field with its type and default. Full reference:\n[`references\u002Fha-cli.md`](..\u002Fblueprint-tooling\u002Freferences\u002Fha-cli.md).\n\nTwo things only the browser can confirm, so finish there: that the translated labels and `data_description` hints read\ncorrectly, and that the form renders the way the selectors promise.\n\n## Do not\n\n- Do not do blocking I\u002FO or long retries inside a flow step; validate with a short timeout.\n- Do not call the flow done before walking it end to end.\n- Do not give an optional free-text field `default=None` — probatio injects that default when the field is left\n  empty and the selector then rejects it, making the form unsubmittable. Carry the current value in\n  `description={\"suggested_value\": ...}` instead.\n","# Work on the config flow\n\nThe config flow is the only supported way to configure a device or service integration (ADR-0010). Everything the user\ncan change lives here, and mistakes here are expensive: `unique_id` and the shape of `entry.data` are effectively\npermanent.\n\n**Read [`blueprint.config_flow.instructions.md`](..\u002F..\u002Finstructions\u002Fblueprint.config_flow.instructions.md)\nfirst.** It is the authoritative rule set: data-vs-options, reserved step names, acceptable unique IDs and their\nnormalisation, schema hygiene, title placeholders, and the migration contract. Copilot injects it automatically when\nyou edit a config flow file; other agents must open it. This skill is the order of operations and the decisions; the\nMUST\u002FNEVER list for each individual flow is in the first reference below.\n\n| File                                                                   | When to read                                                                    |\n| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------- |\n| [`references\u002Fflow-types.md`](references\u002Fflow-types.md)                 | Implementing one flow — user, discovery, reauth, reconfigure, options, subentry |\n| [`references\u002Fdiscovery-matchers.md`](references\u002Fdiscovery-matchers.md) | Writing a `manifest.json` discovery matcher, or using a discovery helper API    |\n| [`references\u002Foauth2.md`](references\u002Foauth2.md)                         | The service authenticates with OAuth2 rather than an API key or a password      |\n| [`references\u002Fmigration.md`](references\u002Fmigration.md)                   | A config entry migration can fail, and the user needs a way to retry it         |\n\n## Package layout\n\nWhere each piece goes. The example ships `__init__.py`, `config_flow.py`, `schemas\u002Fconfig.py` and\n`validators\u002Fcredentials.py`; create the rest when something needs them, rather than leaving empty scaffolding behind.\n\n```text\nconfig_flow_handler\u002F\n├── __init__.py          # exports\n├── config_flow.py       # user, reauth, reauth_confirm, reconfigure, discovery steps\n├── options_flow.py      # post-setup options, only when there is something to tune\n├── handler.py           # logic shared between the flows above\n├── subentry_flow.py     # multi-device \u002F multi-account subentries\n├── schemas\u002F\n│   ├── config.py        # probatio schemas for setup steps\n│   └── options.py       # probatio schemas for the options flow\n└── validators\u002F\n    ├── credentials.py   # \"can we actually talk to it\" checks\n    └── sanitizers.py    # input normalisation (strip, lowercase host, …)\n```\n\nThe top-level `config_flow.py` is a thin shim Home Assistant discovers — leave it alone.\n\n## Adding a config option\n\n1. **Decide data or options** using the table in the instructions file. This is the one irreversible choice here.\n   A polling interval is neither — it is not a field at all. In an integration without options yet, the first real\n   option is when `options_flow.py` and `schemas\u002Foptions.py` get created.\n2. Add the `CONF_*` key to `const.py`.\n3. Add the field to `schemas\u002Fconfig.py` or `schemas\u002Foptions.py` with a selector and a default.\n4. Consume it: coordinator reads `entry.options`, client reads `entry.data`.\n5. Add the `data` and `data_description` translation keys ([`ha-translations`](..\u002Fha-translations\u002FSKILL.md)).\n6. **Handle existing entries** that predate the key — a default at read time, or a `MINOR_VERSION` bump plus migration.\n   This is the step that gets forgotten and breaks upgrades.\n\n## Adding discovery\n\n1. Add the matcher to `manifest.json` — read\n   [`references\u002Fdiscovery-matchers.md`](references\u002Fdiscovery-matchers.md) first, because each protocol has a rule\n   that fails silently when you guess (lowercase-only zeroconf properties, DHCP MACs arriving without separators,\n   VID\u002FPID pairs shared by hundreds of devices):\n\n   ```json\n   \"zeroconf\": [{ \"type\": \"_myservice._tcp.local.\", \"name\": \"blueprint*\" }]\n   ```\n\n2. Implement the matching `async_step_\u003Cmethod>()` following the discovery MUST\u002FNEVER list in\n   [`references\u002Fflow-types.md`](references\u002Fflow-types.md).\n3. Decide what the discovery payload gives you as a stable unique ID. If it offers nothing stable, stop and discuss it\n   — do not fall back to the IP address.\n4. Confirm the flow end-to-end in the UI: the card shows a useful name, a second discovery of the same device aborts,\n   and a device that changed IP updates the existing entry rather than creating a second one.\n\n## Config entry migration\n\nBump `MINOR_VERSION` for additive changes, `VERSION` for restructuring. Read\n[`ha-breaking-changes`](..\u002Fha-breaking-changes\u002FSKILL.md) first — changing entry data affects every existing install.\n\nImplement `async_migrate_entry()` in `custom_components\u002F\u003Cdomain>\u002F__init__.py`:\n\n```python\nasync def async_migrate_entry(hass: HomeAssistant, entry: {ClassPrefix}ConfigEntry) -> bool:\n    \"\"\"Migrate an old config entry.\"\"\"\n    if entry.version == 1 and entry.minor_version \u003C 2:\n        data = {**entry.data, CONF_PORT: DEFAULT_PORT}\n        hass.config_entries.async_update_entry(entry, data=data, minor_version=2)\n    return True\n```\n\nNo downgrade branch and no `return False` — the contract is under\n[Version and Migration](..\u002F..\u002Finstructions\u002Fblueprint.config_flow.instructions.md#version-and-migration); a migration\nthat can fail needs [`references\u002Fmigration.md`](references\u002Fmigration.md).\n\nMigrations must be idempotent and must never delete a key they do not understand. Cover every migration with a test\n([`ha-testing`](..\u002Fha-testing\u002FSKILL.md)).\n\n## Validate\n\n```bash\nscript\u002Flint && script\u002Ftype-check\nscript\u002Fhassfest          # cross-checks every step\u002Ferror\u002Fabort key against translations\nscript\u002Ftest\n```\n\nThen restart Home Assistant and **walk every flow you touched** — add, reconfigure, options, and, by invalidating the\ncredential, reauth. hassfest proves the translation keys exist; only walking the flow proves it is usable. A flow that\npasses CI and dead-ends on the second step is the normal failure here.\n\nWalk it from the terminal first — it is faster, it is repeatable, and it shows the serialised schema Home Assistant\nactually built, which is where defaults and selectors go wrong:\n\n```bash\nscript\u002Fha flow start                              # or --reconfigure\nscript\u002Fha flow step \u003Cflow_id> host=192.0.2.10 username=admin password=secret\nscript\u002Fha flow options                            # then step through it the same way\nscript\u002Fha entries                                 # the entry exists and loaded\n```\n\nEach step prints its `step_id`, any `errors`, and every field with its type and default. Full reference:\n[`references\u002Fha-cli.md`](..\u002Fblueprint-tooling\u002Freferences\u002Fha-cli.md).\n\nTwo things only the browser can confirm, so finish there: that the translated labels and `data_description` hints read\ncorrectly, and that the form renders the way the selectors promise.\n\n## Do not\n\n- Do not do blocking I\u002FO or long retries inside a flow step; validate with a short timeout.\n- Do not call the flow done before walking it end to end.\n- Do not give an optional free-text field `default=None` — probatio injects that default when the field is left\n  empty and the selector then rejects it, making the form unsubmittable. Carry the current value in\n  `description={\"suggested_value\": ...}` instead.\n",{"name":5,"description":7},"main","3a408474735fec0ac5d62b86fc842420a899e090",".agents\u002Fskills\u002Fha-config-flow","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia","https:\u002F\u002Fgithub.com\u002Famg0","2026-11-15 01:01:02",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add amg0\u002Fha_ksenia --skill ha-config-flow",{"tool":35,"command":36},"bunx","bunx skills add amg0\u002Fha_ksenia --skill ha-config-flow",{"tool":38,"command":39},"pnpm","pnpm dlx skills add amg0\u002Fha_ksenia --skill ha-config-flow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-config-flow\u002FSKILL.md",true,[43,49,53,57],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fdiscovery-matchers.md","REFERENCE","参考文档",4107,"https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-config-flow\u002Freferences\u002Fdiscovery-matchers.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fflow-types.md",6345,"https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-config-flow\u002Freferences\u002Fflow-types.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fmigration.md",1602,"https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-config-flow\u002Freferences\u002Fmigration.md",{"path":58,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Foauth2.md",5865,"https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-config-flow\u002Freferences\u002Foauth2.md",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7AB5RYA92GRR64CP6VMWV6Z","issues","Triage\u002Ffix the GitHub issue backlog via branch + PR, with auto-merge on green CI for this session.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fissues\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7AB5G6DR1KGAPRT7JHDCD2Y","ha-translations","Add or fix user-facing strings for this Home Assistant custom integration — translations\u002Fen.json and other languages, icons.json, entity names and states, config flow labels and errors, service action descriptions, exception messages, and repair issue text. Use when asked to \"update translations\", \"add a translation key\", \"translate\", \"fix the entity name\", \"add strings for the new sensor\u002Faction\u002Foption\", \"add icons\", or when hassfest reports a missing or unused translation key. Covers the key structure, which keys each feature needs, placeholders, the icons.json contract, and the project's strict rule about only touching en.json. SYMPTOMS — load this if you are about to: write user-facing English into Python; edit a language file other than `en.json`; add an entity without its `entity.\u003Cplatform>.\u003Ckey>.name` key; skip `data_description` on a config flow field; or set `icon=` instead of using `icons.json`.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-translations\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7AB56JBRMF19W4N2NG9Y5GW","ha-testing","Write, fix, or extend automated tests for this Home Assistant custom integration using pytest and pytest-homeassistant-custom-component. Use when asked to \"add tests\", \"write a test\", \"the tests fail\", \"improve coverage\", \"add a regression test\", \"test the config flow\", \"update snapshots\", or when a behavioural change needs verification before it can be called done. Covers the tests\u002F layout, the conftest.py fixtures this project needs, mocking the API client, config flow and entity test patterns, registry assertions, syrupy snapshots, freezing time, and the script\u002Ftest commands. SYMPTOMS — load this if you are about to: instantiate an entity class directly instead of asserting on `hass.states`; write a test without `enable_custom_integrations`; use `time.sleep` instead of `async_fire_time_changed`; silence a DeprecationWarning to make the suite pass; or commit a snapshot you have not read.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-testing\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7AB4V9XKDYRDCRHEA68GRZ5","ha-service-action","Add, change, or remove a Home Assistant service action (also called a \"service\" or \"action\") in this custom integration. Use when asked to \"add a service\", \"add an action\", \"expose X as a service call\", \"add a service that returns data\", \"make this callable from an automation\", or when editing services.yaml, the service_actions\u002F package, service schemas, service response data, or the async_setup() registration. Covers the services.yaml contract, probatio schemas, selectors, entity\u002Fdevice targeting, response data, translated error messages, and the Bronze quality-scale rule that actions must be registered in async_setup(). SYMPTOMS — load this if you are about to: register an action in `async_setup_entry()`; add a `services.yaml` field without a selector; add an `entity_id` field where `target:` belongs; raise a plain English `HomeAssistantError`; or swallow an action failure into a log line.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-service-action\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7AB4J65REZ9T9VS9MQH73CC","ha-release","Cut a release of this Home Assistant custom integration, or prepare the commits that feed it. Use when asked to \"release\", \"cut a version\", \"bump the version\", \"prepare release notes\", \"what will the next version be\", \"write a commit message\", \"why didn't release-please pick this up\", or when reviewing whether a change is user-facing. Covers the Conventional Commits rules commitlint enforces here, how release-please derives the version and changelog, the pre-1.0 bump rules, script\u002Fversion and script\u002Frelease-notes, skipping a commit from the notes, and the commit rules this project enforces for agents. SYMPTOMS — load this if you are about to: commit without an explicit request; offer to `git push`; label a user-facing fix as `chore` (chore, like every hidden type, never reaches the changelog and never triggers a release); write a commit subject over 100 characters or in sentence case; or edit the version in `manifest.json` by hand.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-release\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M7AB48WMPGDK2REBC3WS8T32","ha-quality-review","Perform a structured quality review of this Home Assistant custom integration, either as a full audit or scoped to a diff. Use when asked to \"review the integration\", \"audit the code\", \"check quality scale\", \"are we bronze\u002Fsilver\u002Fgold\", \"is this ready to release\", \"review my changes\", \"what's missing before publishing\", or before opening a pull request that touches integration code. Covers running the automated gates first, then auditing architecture, the Integration Quality Scale rules, error handling, security, performance, user experience, and documentation — and reporting findings ranked by severity with concrete fixes. SYMPTOMS — load this if you are about to: report a review that only restates linter output; claim real-device testing that did not happen; give a finding without a file path and a fix; or judge quality without running `script\u002Fhassfest` and the test suite first.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-quality-review\u002FSKILL.md",[],[]]