MAUI UI Test Writer
dotnet/maui
Writes UI tests that reproduce a GitHub issue in .NET MAUI and keeps iterating until the tests actually fail, proving they catch the bug.
Home Assistant Android end-to-end (Maestro) failure triage. An agent skill from home-assistant/android.
Install Ha Android E2E Debugging
$ npx skills add home-assistant/android --skill ha-android-e2e-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install home-assistant/android ha-android-e2e-debugging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/home-assistant/android.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ha-android-e2e-debugging .claude/skills/ha-android-e2e-debugging && rm -rf skills-srcUse ~/.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/
Install the "ha-android-e2e-debugging" agent skill from https://github.com/home-assistant/android/tree/main/.agents/skills/ha-android-e2e-debugging into .claude/skills/ha-android-e2e-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ha-android-e2e-debugging", 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 install https://github.com/home-assistant/android/tree/main/.agents/skills/ha-android-e2e-debuggingType 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.
$ npx skills add home-assistant/android --skill ha-android-e2e-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install home-assistant/android ha-android-e2e-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/home-assistant/android.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/ha-android-e2e-debugging .agents/skills/ha-android-e2e-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ha-android-e2e-debugging" agent skill from https://github.com/home-assistant/android/tree/main/.agents/skills/ha-android-e2e-debugging into .agents/skills/ha-android-e2e-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ha-android-e2e-debugging", 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.
$ npx skills add home-assistant/android --skill ha-android-e2e-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install home-assistant/android ha-android-e2e-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/home-assistant/android.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/ha-android-e2e-debugging .cursor/skills/ha-android-e2e-debugging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ha-android-e2e-debugging" agent skill from https://github.com/home-assistant/android/tree/main/.agents/skills/ha-android-e2e-debugging into .cursor/skills/ha-android-e2e-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ha-android-e2e-debugging", 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 https://github.com/home-assistant/android.git --path .agents/skills/ha-android-e2e-debugging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add home-assistant/android --skill ha-android-e2e-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install home-assistant/android ha-android-e2e-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/home-assistant/android.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/ha-android-e2e-debugging .gemini/skills/ha-android-e2e-debugging && rm -rf skills-srcUse ~/.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/
Install the "ha-android-e2e-debugging" agent skill from https://github.com/home-assistant/android/tree/main/.agents/skills/ha-android-e2e-debugging into .gemini/skills/ha-android-e2e-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ha-android-e2e-debugging", 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.
$ gh skill install home-assistant/android ha-android-e2e-debuggingInstalls 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).
$ npx skills add home-assistant/android --skill ha-android-e2e-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/home-assistant/android.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/ha-android-e2e-debugging .github/skills/ha-android-e2e-debugging && rm -rf skills-srcUse ~/.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/
Install the "ha-android-e2e-debugging" agent skill from https://github.com/home-assistant/android/tree/main/.agents/skills/ha-android-e2e-debugging into .github/skills/ha-android-e2e-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ha-android-e2e-debugging", 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.
$ npx skills add home-assistant/android --skill ha-android-e2e-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install home-assistant/android ha-android-e2e-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/home-assistant/android.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/ha-android-e2e-debugging .opencode/skills/ha-android-e2e-debugging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ha-android-e2e-debugging" agent skill from https://github.com/home-assistant/android/tree/main/.agents/skills/ha-android-e2e-debugging into .opencode/skills/ha-android-e2e-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ha-android-e2e-debugging", 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
ha-android-e2e-debugging- GitHub stars
- 4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 706 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Home Assistant Android end-to-end (Maestro) failure triage. An agent skill from home-assistant/android.
- Works in 3 steps: Collect the artifacts → Sources → Report
- The E2E workflow fails
- SKILL.md covers 1. Collect the artifacts, 2. Sources and 3. Report
- Calls gh, jq and docker
What it does
Ha Android E2E Debugging is an agent skill from home-assistant/android. Home Assistant Android end-to-end (Maestro) failure triage. Use when the E2E workflow fails, when reading its artifacts (Maestro report, logcat, Home Assistant logs), or when deciding whether a failure comes from the app, from Home Assistant, or from flakiness.
Its SKILL.md is about 1.5k 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 Testing & QA, covering Mobile testing and debugging and End-to-end testing. It works with Home Assistant and Android. The repository describes itself as: Home Assistant Companion for Android. The licence is Apache-2.0.
When your agent uses it
- The E2E workflow fails
- Reading its artifacts (Maestro report
- Home Assistant logs)
- Deciding whether a failure comes from the app
Example prompts
- “/ha-android-e2e-debugging”
Requirements
- Docker
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit eaa2122. 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:
ghjqdocker
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
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
Ha Android E2E Debugging loads about 1.5k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 706 words of instructions outside code blocks.
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 home-assistant/android at commit eaa2122, republished under its Apache-2.0 licence (© home-assistant). 706 words, ~1,528 tokens.
Download SKILL.mdSave it as
.claude/skills/ha-android-e2e-debugging/SKILL.md (or your agent's skills folder).- name
- ha-android-e2e-debugging
- description
- Home Assistant Android end-to-end (Maestro) failure triage. Use when the E2E workflow fails, when reading its artifacts (Maestro report, logcat, Home Assistant logs), or when deciding whether a failure comes from the app, from Home Assistant, or from flakiness.
HA Android E2E Debugging
The E2E workflow (.github/workflows/e2e.yml) runs the .maestro/onboarding.yaml flow every night at 05:00 UTC. It starts a Home Assistant container (the dev image unless the run overrides it), boots one emulator per API level from 29 up to androidSdk-target, installs app-full-debug.apk on each, and shards the same flow across all of them. Every shard talks to that one container.
Read the sources in section 2 in order and stop at the first one that explains the failure, then always write the report in section 3. Once a source explains it, skip the rest.
1. Collect the artifacts
gh run download <run-id> --name e2e-artifacts --dir e2e-artifacts| Path | Content |
|---|---|
maestro-results/<timestamp>/onboarding-shard-<N>/ | One directory per shard: commands.json trace, logs/maestro.log, logs/device-logcat.txt, and screenshots/step-*.png with screen-hierarchy/step-*.json captured at each tap and at the failure |
logcat-api<N>-<serial>.txt | Full device logcat, one file per emulator, named by API level |
homeassistant.log | Timestamped container log |
homeassistant-config.json | /api/config response: Home Assistant version, loaded components |
homeassistant-container.json | docker inspect of the container: image digest and labels |
2. Sources
2.1 Maestro report
Find the failed command and its shard in one pass:
jq -c 'to_entries[] | select(.value.metadata.status == "FAILED") | {shard: input_filename, step: (.key + 1), command: .value.command, error: .value.metadata.error.message}' \
e2e-artifacts/maestro-results/*/onboarding-shard-*/commands.jsonstep is the zero-padded number in that shard's screenshots/step-<step>-*.png and screen-hierarchy/step-<step>-*.json; open both. An element visible in the screenshot but absent from the hierarchy never reached the accessibility tree; a broken screen shows in the screenshot itself.
2.2 logcat
Only when 2.1 explains nothing. Shard numbers are not API levels. The shard's logs/device-logcat.txt is the same device as one logcat-api<N>-*.txt in another format, so match them on a message: take an early line of the shard's logcat, strip everything up to the first ): , and grep -l -F the rest across logcat-api*.txt. Useful filters on the matched file:
grep -nE 'AndroidRuntime|FATAL' e2e-artifacts/logcat-api<N>-*.txt | tail -40
grep -nE 'io\.homeassistant|chromium|WebSocket|okhttp' e2e-artifacts/logcat-api<N>-*.txt | tail -40Look for a crash or ANR at the failure timestamp, TLS or DNS errors reaching homeassistant.internal, WebSocket disconnects, and chromium renderer errors.
2.3 Home Assistant logs
Only when 2.1 and 2.2 explain nothing.
grep -nE ' (ERROR|WARNING) ' e2e-artifacts/homeassistant.log | tail -40
jq -c '{version, mobile_app: (.components | index("mobile_app") != null)}' e2e-artifacts/homeassistant-config.json
jq -r '.[0].Config.Image' e2e-artifacts/homeassistant-container.jsonRead the errors around the failure time, and confirm mobile_app is loaded: the workflow verifies it at startup, but a later integration failure can still break onboarding. An error that the same grep also finds in e2e-artifacts-last-green/homeassistant.log did not break this run. The frontend.js.* logger name carries the frontend build date, useful for the next step.
2.4 Upstream: core and frontend
Only when 2.1 to 2.3 explain nothing. A typical upstream symptom is a clean split by API level: every shard below some API level fails at the same step while every shard above it passes. The frontend ships one bundle to all WebViews, so a change that relies on a newer web feature breaks the older WebViews together.
The dev image moves every night, so the useful comparison is against the last run that passed. The triage workflow downloads it into e2e-artifacts-last-green/ before the agent starts; only when working locally, fetch it yourself:
gh run list --workflow=e2e.yml --status success --limit 1 --json databaseId,createdAt
gh run download <green-run-id> --name e2e-artifacts --dir e2e-artifacts-last-greenDiff the two homeassistant-config.json files to get the Home Assistant versions on either side of the break, then look at what landed between those dates:
Show full SKILL.md (223 more words)Show less
3. Report
Everything lands in the e2e-failure issue in this repository: a comment when one is already open, a new issue otherwise. Never open anything on another repository; an upstream finding goes in the same comment for a maintainer to carry over.
Write:
- Verdict — Say how confident you are and what would confirm it.
- Evidence — the failing Maestro command, the logcat and Home Assistant log lines the verdict rests on, and the Home Assistant versions of the failed and the last green run, read from the two
homeassistant-config.jsonfiles. Quote the lines, don't paraphrase them. - Culprit commit — only when you went through 2.4. Give it as
owner/repo@shawith its title and date, and say what in it explains the failure. When you only narrowed it to a range, give the range and say it is a range. When you stopped before 2.4, say so in one line. - Proposed fix — a concrete patch: name the file and the change, whether here, in core, or in the frontend, so a maintainer can apply or forward it. When the right answer is to adapt the Maestro flow to an intentional upstream change, say that.
- A link to the failed run.
Say plainly when the evidence supports no verdict, and list what you checked. A short honest report beats a confident guess.
© home-assistant, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/ha-android-e2e-debugging of home-assistant/android.
Open the folder on GitHubat commit eaa2122
Compare with similar skills
Ha Android E2E Debugging 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ha Android E2E Debugging this skillhome-assistant/android | 4k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| MAUI UI Test Writerdotnet/maui | 23k | — | ~3k | Automated safety check: Pass | MIT | |
| Android E2E Testerbrim-borium/spotify_sdk | 166 | — | ~284 | Automated safety check: Notes | Apache-2.0 | |
| Simulator Audio E2Ehyochan/react-native-nitro-sound | 961 | — | ~1.1k | Automated safety check: Pass | MIT | |
| SoloPi AI Controlalipay/SoloPi | 6.3k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| E2Egronxb/hot-updater | 1.8k | — | ~1.6k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Android E2E Tester
brim-borium/spotify_sdk
Run autonomous Android E2E tests on example app via ADB MCP with Logcat verification.
Simulator Audio E2E
hyochan/react-native-nitro-sound
Build and run repeatable react-native-nitro-sound recorder/player regression tests on an iOS Simulator or Android emulator, with explicit virtual-device selection, microphone permission, Maestro…
SoloPi AI Control
alipay/SoloPi
Drives Android devices through SoloPi's typed command line to record, replay and verify app behavior, with device pools and signed on-device decision models.
E2E
gronxb/hot-updater
Run end-to-end OTA verification for examples/v0.85.0 with agent-device.
Mesh Lab
permissionlesstech/bitchat-android
Run, diagnose, and extend bitchat Android Mesh Lab physical-device tests.
More from home-assistant/android
All 10 skills in this repoHa Android Architecture
home-assistant/android
Home Assistant Android module and layer architecture. An agent skill from home-assistant/android.
Ha Android Concurrency
home-assistant/android
Home Assistant Android coroutine and threading guidance. An agent skill from home-assistant/android.
Ha Android Kotlin Style
home-assistant/android
Home Assistant Android Kotlin style. An agent skill from home-assistant/android.
Ha Android Logging Errors
home-assistant/android
Home Assistant Android logging and error handling. An agent skill from home-assistant/android.
Ha Android Testing
home-assistant/android
Home Assistant Android testing guidance. An agent skill from home-assistant/android.
Ha Android UI
home-assistant/android
Home Assistant Android UI guidance. An agent skill from home-assistant/android.
Related
Works with
Categories
Questions about Ha Android E2E Debugging
What does Ha Android E2E Debugging do?
Home Assistant Android end-to-end (Maestro) failure triage. An agent skill from home-assistant/android. Ha Android E2E Debugging is an agent skill from home-assistant/android. Home Assistant Android end-to-end (Maestro) failure triage.
When should I use Ha Android E2E Debugging?
Ha Android E2E Debugging fits situations like: the E2E workflow fails; reading its artifacts (Maestro report; home Assistant logs); deciding whether a failure comes from the app.
How do I install Ha Android E2E Debugging in Claude Code?
Run `npx skills add home-assistant/android --skill ha-android-e2e-debugging -a claude-code`. Or copy the skill folder (.agents/skills/ha-android-e2e-debugging in home-assistant/android) into .claude/skills/ha-android-e2e-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Ha Android E2E Debugging in Codex?
Run `npx skills add home-assistant/android --skill ha-android-e2e-debugging -a codex`. Or copy the skill folder (.agents/skills/ha-android-e2e-debugging in home-assistant/android) into .agents/skills/ha-android-e2e-debugging in your project. Codex loads it when a task matches its description.
Can I use Ha Android E2E Debugging 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 home-assistant/android --skill ha-android-e2e-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ha-android-e2e-debugging, .gemini/skills/ha-android-e2e-debugging, .github/skills/ha-android-e2e-debugging and .opencode/skills/ha-android-e2e-debugging in your project.
What does Ha Android E2E Debugging need to run?
Going by SKILL.md and its folder, Ha Android E2E Debugging needs the command-line tools its instructions call (gh, jq and docker). Our summary lists: Docker.
Does Ha Android E2E Debugging access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Ha Android E2E Debugging 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 Ha Android E2E Debugging use?
Ha Android E2E Debugging is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ha Android E2E Debugging use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Ha Android E2E Debugging?
Skills that share tags, products or a category with Ha Android E2E Debugging: MAUI UI Test Writer (dotnet/maui, 23k stars), Android E2E Tester (brim-borium/spotify_sdk, 166 stars), Simulator Audio E2E (hyochan/react-native-nitro-sound, 961 stars) and SoloPi AI Control (alipay/SoloPi, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ha Android E2E Debugging?
home-assistant (a GitHub organization) maintains it in home-assistant/android, which has 3,951 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.
Source: home-assistant/android on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.