Agent skill

Hass Sync

by homeassistant-extras in homeassistant-extras/device-card

Maintains synchronization between src/hass folder and Home Assistant frontend source code.

Install Hass Sync

skills CLI

$ npx skills add homeassistant-extras/device-card --skill hass-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install homeassistant-extras/device-card hass-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/homeassistant-extras/device-card.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/hass-sync .claude/skills/hass-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "hass-sync" agent skill from https://github.com/homeassistant-extras/device-card/tree/main/.claude/skills/hass-sync into .claude/skills/hass-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hass-sync", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/homeassistant-extras/device-card/tree/main/.claude/skills/hass-sync

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add homeassistant-extras/device-card --skill hass-sync -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install homeassistant-extras/device-card hass-sync --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/homeassistant-extras/device-card.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/hass-sync .agents/skills/hass-sync && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "hass-sync" agent skill from https://github.com/homeassistant-extras/device-card/tree/main/.claude/skills/hass-sync into .agents/skills/hass-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hass-sync", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add homeassistant-extras/device-card --skill hass-sync -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install homeassistant-extras/device-card hass-sync --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/homeassistant-extras/device-card.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/hass-sync .cursor/skills/hass-sync && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "hass-sync" agent skill from https://github.com/homeassistant-extras/device-card/tree/main/.claude/skills/hass-sync into .cursor/skills/hass-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hass-sync", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/homeassistant-extras/device-card.git --path .claude/skills/hass-sync

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add homeassistant-extras/device-card --skill hass-sync -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install homeassistant-extras/device-card hass-sync --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/homeassistant-extras/device-card.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/hass-sync .gemini/skills/hass-sync && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "hass-sync" agent skill from https://github.com/homeassistant-extras/device-card/tree/main/.claude/skills/hass-sync into .gemini/skills/hass-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hass-sync", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install homeassistant-extras/device-card hass-sync

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add homeassistant-extras/device-card --skill hass-sync -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/homeassistant-extras/device-card.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/hass-sync .github/skills/hass-sync && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "hass-sync" agent skill from https://github.com/homeassistant-extras/device-card/tree/main/.claude/skills/hass-sync into .github/skills/hass-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hass-sync", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add homeassistant-extras/device-card --skill hass-sync -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install homeassistant-extras/device-card hass-sync --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/homeassistant-extras/device-card.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/hass-sync .opencode/skills/hass-sync && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "hass-sync" agent skill from https://github.com/homeassistant-extras/device-card/tree/main/.claude/skills/hass-sync into .opencode/skills/hass-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hass-sync", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: hass-sync
GitHub stars: 130
Token cost: ~1.4k tokens
SKILL.md length: 487 words
Files: 1
Skills in repo: 2
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Maintains synchronization between src/hass folder and Home Assistant frontend source code.

Works in 3 steps: Verify File Locations → Verify Code Matches Upstream → Identify Unused Code
Working with src/hass files
SKILL.md covers Upstream Source, Core Tasks, Workflow and GitHub URL Pattern, plus 2 more sections
Calls git; reaches github.com

What it does

Hass Sync is an agent skill from homeassistant-extras/device-card. Maintains synchronization between src/hass folder and Home Assistant frontend source code. Verifies file locations, checks code matches upstream, and identifies unused code. Use when working with src/hass files, syncing Home Assistant code, or verifying code synchronization.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design. It works with Home Assistant, GitHub and Git. The repository describes itself as: Device Card to summarize device information in Home Assistant. The licence is MIT.

When your agent uses it

Working with src/hass files
Syncing Home Assistant code
Verifying code synchronization

Example prompts

“Use the hass-sync skill to maintain synchronization between src/hass folder and Home Assistant frontend source code”
“/hass-sync”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Verify File Locations
Verify Code Matches Upstream
Identify Unused Code

What it can do on your machine

Read from SKILL.md and the folder at commit 3424f04. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hass Sync loads about 1.4k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 487 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~71
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from homeassistant-extras/device-card at commit 3424f04, republished under its MIT licence (© homeassistant-extras). 487 words, ~1,391 tokens.

Download SKILL.mdSave it as .claude/skills/hass-sync/SKILL.md (or your agent's skills folder).

name: hass-sync
description: Maintains synchronization between src/hass folder and Home Assistant frontend source code. Verifies file locations, checks code matches upstream, and identifies unused code. Use when working with src/hass files, syncing Home Assistant code, or verifying code synchronization.

Home Assistant Code Synchronization

Maintains the src/hass folder which contains minimal code copied from Home Assistant frontend (home-assistant/frontend). Each file has a GitHub link comment at the top for reference.

Upstream Source

The upstream Home Assistant frontend is cloned locally at:

Path: ../frontend/ (relative to device-card project root)
Full path: /Users/patrickmasters/Desktop/src.nosync/homeassistant/frontend/

Keeping Upstream Updated

Before comparing, ensure the local frontend clone is up to date:

Check git status:
bash
```
cd ../frontend && git status
```

Check if behind upstream:

bash

cd ../frontend && git fetch && git status

Update if needed:
- Ask user: "Frontend clone may be outdated. Pull latest changes?"
- If yes: cd ../frontend && git pull
- If no: Proceed with current state (user may want to compare against specific version)

The agent can ensure latest or ask for a git pull before comparisons.

Core Tasks

1. Verify File Locations

Check if files are in the correct location relative to upstream:

Extract GitHub URLs from file comments:
typescript
```
/**
 * https://github.com/home-assistant/frontend/blob/dev/src/common/const.ts
 */
```
→ Expected local path: src/hass/common/const.ts → Upstream path: ../frontend/src/common/const.ts
Path mapping rule:
- Upstream: ../frontend/src/[path]
- Local: src/hass/[path]
Check for moved files:
- If GitHub URL path doesn't match current file location → flag as moved
- Verify if upstream file still exists at that path in local clone
- Action: Move the file in this project to match upstream structure (not just update the URL)

2. Verify Code Matches Upstream

Ensure copied code matches upstream as closely as possible:

Read upstream content from local frontend clone:
- Extract path from GitHub URL comment
- Read file from ../frontend/src/[path]
Compare structure:
- Export order (should match)
- Function/class order (should match)
- Import order (can differ if using local paths)
Identify intentional changes:
- Look for comments like // MODIFIED: or // CHANGED:
- Check if imports use @hass/ paths (local) vs original paths
Flag differences:
- Reordered exports/functions
- Missing code from upstream (unless intentional - e.g., partial types)
- Extra code not in upstream
- Code improvements without documentation comments

Show full SKILL.md (186 more words)Show less

3. Identify Unused Code

Ensure unnecessary code isn't copied:

Check imports:
- Search project for usage of imported symbols
- Flag unused imports
Check exports:
- Search project for usage of exported symbols
- Flag unused exports (unless they're re-exported for convenience)
Check internal code:
- Functions/types only used internally in hass folder
- Verify they're actually needed by other hass files

Workflow

When syncing a file:

1. Ensure frontend clone is up to date (ask user or check git status)
2. Extract GitHub URL from comment
3. Map to local upstream path: ../frontend/src/[path]
4. Read upstream content from local clone
5. Compare:
   - [ ] File location matches expected path
   - [ ] Code structure matches (order, exports)
   - [ ] No unintentional changes
   - [ ] All imports/exports are used
6. Report findings

When checking all files:

1. Ensure frontend clone is up to date (ask user or check git status)
2. Scan all files in src/hass/
3. For each file:
   - Extract GitHub URL
   - Map to upstream path: ../frontend/src/[path]
   - Verify location
   - Check if upstream file exists in local clone
   - Read and compare content structure
   - Check usage
4. Generate report:
   - Files in wrong location
   - Files with mismatched content
   - Files with unused code
   - Files that may have moved upstream

GitHub URL Pattern

Files follow this pattern:

typescript

/**
 * https://github.com/home-assistant/frontend/blob/dev/src/[path]
 */

Path mapping:

GitHub URL path: src/[path]
Local file: src/hass/[path]
Upstream file: ../frontend/src/[path]

The GitHub URL is kept for reference, but comparisons use the local frontend clone.

Intentional Modifications

Files may have intentional changes:

Import paths changed to use @hass/ aliases
Comments added with // MODIFIED: or // CHANGED:
Partial code copied (only needed parts)
Code improvements: Intentional improvements (e.g., SonarQube code smell cleanups) should be documented with comments explaining they are intentional
Minimal types: Types/interfaces can be minimal or partial - only include fields that are actually used in this project

Always respect intentional modifications - only flag unintentional differences.

Usage Examples

Check a specific file:

Verify src/hass/data/entity.ts matches upstream

Check all files:

Audit all files in src/hass for sync issues

Find unused code:

Find unused imports/exports in src/hass

Verify file locations:

Check if any files need to be moved due to upstream changes

Files

Just SKILL.md in .claude/skills/hass-sync of homeassistant-extras/device-card.

Open the folder on GitHubat commit 3424f04

Compare with similar skills

Hass Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hass Sync compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Hass Sync this skillhomeassistant-extras/device-card	130	—	~1.4k	Automated safety check: Pass	MIT	2 days ago
Publish AI Sitebubblevv/ai-api-gongyi-nav	100	—	~959	Automated safety check: Pass	None	today
Releasedcb/homeassistant-claude-kit	123	—	~3.1k	Automated safety check: Pass	MIT	7 days ago
Fix GitHub IssueAgnosticUI/agnosticui	827	—	~751	Automated safety check: Pass	Apache-2.0	today
Releaservdbreemen/OTGW-firmware	207	—	~2.5k	Automated safety check: Pass	GPL-3.0	2 days ago
Oss Readyluongnv89/skills	131	—	~2.6k	Automated safety check: Notes	MIT	today

Similar skills

Publish AI Site
bubblevv/ai-api-gongyi-nav
A skill your agent uses when adding or publishing an AI API public-benefit or relay-site listing from promotional copy in this repository, including validating the referral link, regenerating the…
100 GitHub stars~959 tokensUpdated today
Frontend & DesignAuto-check passed
Release
dcb/homeassistant-claude-kit
Cut a new homeassistant-claude-kit version. An agent skill from dcb/homeassistant-claude-kit.
123 GitHub stars~3.1k tokensUpdated 7 days ago
DevelopmentAuto-check passed
Fix GitHub Issue
AgnosticUI/agnosticui
Fix a GitHub issue by number. An agent skill from AgnosticUI/agnosticui.
827 GitHub stars~751 tokensUpdated today
Frontend & DesignAuto-check passed
Release
rvdbreemen/OTGW-firmware
Prepare and execute a full OTGW-firmware release following the documented release process
207 GitHub stars~2.5k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Oss Ready
luongnv89/skills
Transform a project into a professional open-source repository by adding LICENSE, README, CONTRIBUTING, CODEOFCONDUCT, SECURITY, and GitHub issue/PR templates.
131 GitHub stars~2.6k tokensUpdated today
Frontend & DesignAuto-check: notes
Wiki Manager
Community-Access/accessibility-agents
GitHub wikis: create, edit, organize and search pages from the editor.
423 GitHub stars~911 tokensUpdated 16 days ago
Frontend & DesignAuto-check passed

More from homeassistant-extras/device-card

GitHub Issue Solver
homeassistant-extras/device-card
Accept a GitHub issue URL or issue details, create a comprehensive plan (in plan mode - shows plan first), then implement the solution including tests and documentation, create/update release notes…
130 GitHub stars~3.4k tokensUpdated 2 days ago
Auto-check passed

Works with

Questions about Hass Sync

What does Hass Sync do?

Maintains synchronization between src/hass folder and Home Assistant frontend source code. Hass Sync is an agent skill from homeassistant-extras/device-card. Maintains synchronization between src/hass folder and Home Assistant frontend source code.

When should I use Hass Sync?

Hass Sync fits situations like: working with src/hass files; syncing Home Assistant code; verifying code synchronization.

How do I install Hass Sync in Claude Code?

Run `npx skills add homeassistant-extras/device-card --skill hass-sync -a claude-code`. Or copy the skill folder (.claude/skills/hass-sync in homeassistant-extras/device-card) into .claude/skills/hass-sync in your project. Claude Code loads it when a task matches its description.

How do I install Hass Sync in Codex?

Run `npx skills add homeassistant-extras/device-card --skill hass-sync -a codex`. Or copy the skill folder (.claude/skills/hass-sync in homeassistant-extras/device-card) into .agents/skills/hass-sync in your project. Codex loads it when a task matches its description.

Can I use Hass Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add homeassistant-extras/device-card --skill hass-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hass-sync, .gemini/skills/hass-sync, .github/skills/hass-sync and .opencode/skills/hass-sync in your project.

What does Hass Sync need to run?

Going by SKILL.md and its folder, Hass Sync needs the command-line tools its instructions call (git).

Does Hass Sync access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Hass Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Hass Sync use?

Hass Sync is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hass Sync use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Hass Sync?

Skills that share tags, products or a category with Hass Sync: Publish AI Site (bubblevv/ai-api-gongyi-nav, 100 stars), Release (dcb/homeassistant-claude-kit, 123 stars), Fix GitHub Issue (AgnosticUI/agnosticui, 827 stars) and Release (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hass Sync?

homeassistant-extras (a GitHub organization) maintains it in homeassistant-extras/device-card, which has 130 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.

Source: homeassistant-extras/device-card on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Hass Sync

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Home Assistant Code Synchronization

Upstream Source

Keeping Upstream Updated

Core Tasks

1. Verify File Locations

2. Verify Code Matches Upstream

3. Identify Unused Code

Workflow

When syncing a file:

When checking all files:

GitHub URL Pattern

Intentional Modifications

Usage Examples

Files

Compare with similar skills

Similar skills

Publish AI Site

Release

Fix GitHub Issue

Release

Oss Ready

Wiki Manager

More from homeassistant-extras/device-card

GitHub Issue Solver

Related

Questions about Hass Sync