ha-oauth2-credentials-augmentlisted

Augments an existing Home Assistant Custom Integration with the OAuth2 / Application Credentials flow, conforming to spec/ha/application-credentials. Creates application_credentials.py with the authorization-server wiring, converts the config flow to an AbstractOAuth2FlowHandler subclass that creates the entry and sets unique_id, adds the application_credentials manifest dependency, runs token refresh through OAuth2Session, implements the reauth path, and adds the matching strings.json entries; exact signatures live in the body and spec. Activate on "add OAuth2 to my integration", "wire up application credentials", "set up the OAuth2 config flow", or equivalent German requests. Do not activate for generic user/password or API-key config flows (ha-config-flow-augment), greenfield scaffolding (ha-integration-scaffold), coordinator wiring (ha-coordinator-add), or deploying to a live HA instance.
nolte/claude-home-assistant · ★ 1 · API & Backend · score 68

Install: claude install-skill nolte/claude-home-assistant

# HA OAuth2 Credentials Augment Spec: `spec/claude/ha-oauth2-credentials-augment/en.md` (EN canonical) / `spec/claude/ha-oauth2-credentials-augment/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user names the OAuth2 provider endpoints and reads back `application_credentials.py`, the OAuth2 config flow, and the conformance report; a skill keeps this on the visible command surface, like the sibling augment skills (`ha-config-flow-augment`, `ha-coordinator-add`, `ha-repairs-add`). - **Mid-flow interactivity** — the OAuth2-vs-non-OAuth2 check, the PKCE decision, and the `unique_id` source are per-run dialogues the user approves before generation. - **Bounded, inline generation** — one platform module plus the config-flow handler, the manifest edit, and the strings fit inline; no isolated agent context is needed. - Counter-dimension considered: the draft→validate loop could be an agent, but the provider-endpoint capture and the OAuth2-fit advice belong in the user's working context; skill wins. ## When this skill activates Use this skill to add the OAuth2 / Application Credentials flow to an existing integration whose provider requires OAuth2 — the user enters their own client id and secret via the Application Credentials UI. ## When NOT to activate - a generic user/password or API-key config flow → `ha-config-flow-augment` / `ha/config-flow-patterns` - greenfield integration scaffolding → `ha-integration-scaffo