Agent skill

Verify UI

After Compose UI changes, assess test coverage and write/amend Robolectric characterisation tests using the Robot pattern.

Apache-2.0Auto-check passedTesting & QA

Install Verify UI

skills CLI

$ npx skills add timusus/Shuttle2 --skill verify-ui -a claude-code

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

GitHub CLI

$ gh skill install timusus/Shuttle2 verify-ui --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/timusus/Shuttle2.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/verify-ui .claude/skills/verify-ui && 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 "verify-ui" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/verify-ui into .claude/skills/verify-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-ui", 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/timusus/Shuttle2/tree/main/.claude/skills/verify-ui

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 timusus/Shuttle2 --skill verify-ui -a codex

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

GitHub CLI

$ gh skill install timusus/Shuttle2 verify-ui --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/verify-ui .agents/skills/verify-ui && 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 "verify-ui" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/verify-ui into .agents/skills/verify-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-ui", 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 timusus/Shuttle2 --skill verify-ui -a cursor

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

GitHub CLI

$ gh skill install timusus/Shuttle2 verify-ui --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/verify-ui .cursor/skills/verify-ui && 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 "verify-ui" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/verify-ui into .cursor/skills/verify-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-ui", 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/timusus/Shuttle2.git --path .claude/skills/verify-ui

--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 timusus/Shuttle2 --skill verify-ui -a gemini-cli

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

GitHub CLI

$ gh skill install timusus/Shuttle2 verify-ui --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/timusus/Shuttle2.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/verify-ui .gemini/skills/verify-ui && 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 "verify-ui" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/verify-ui into .gemini/skills/verify-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-ui", 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 timusus/Shuttle2 verify-ui

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 timusus/Shuttle2 --skill verify-ui -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/verify-ui .github/skills/verify-ui && 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 "verify-ui" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/verify-ui into .github/skills/verify-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-ui", 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 timusus/Shuttle2 --skill verify-ui -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 timusus/Shuttle2 verify-ui --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/verify-ui .opencode/skills/verify-ui && 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 "verify-ui" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/verify-ui into .opencode/skills/verify-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-ui", 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: verify-ui
GitHub stars: 229
Token cost: ~1.1k tokens
SKILL.md length: 421 words
Files: 1
Skills in repo: 13
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

After Compose UI changes, assess test coverage and write/amend Robolectric characterisation tests using the Robot pattern.

Works in 4 steps: Identify What Changed → Find Existing Coverage → Write the Test → …
Tasks that involve Test coverage
SKILL.md covers Step 1: Identify What Changed, Step 2: Find Existing Coverage, Step 3: Write the Test and Step 4: Run and Verify, plus 1 more section
Calls git

What it does

Verify UI is an agent skill from timusus/Shuttle2. After Compose UI changes, assess test coverage and write/amend Robolectric characterisation tests using the Robot pattern.

Its SKILL.md is about 1.1k 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 Test coverage and Android development. It works with Android. The repository describes itself as: Shuttle Music: a music player for Android and iOS. Plays local files and streams from Jellyfin, Emby, Plex and Navidrome/Subsonic, with Chromecast, Android Auto, EQ and replay… The licence is Apache-2.0.

When your agent uses it

Tasks that involve Test coverage
Tasks that involve Android development

Example prompts

“/verify-ui”

Workflow steps

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

Identify What Changed
Find Existing Coverage
Write the Test
Run and Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 116c579. 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
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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

Verify UI loads about 1.1k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 421 words of instructions outside code blocks.

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

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 timusus/Shuttle2 at commit 116c579, republished under its Apache-2.0 licence (© timusus). 421 words, ~1,122 tokens.

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

name: verify-ui
description: After Compose UI changes, assess test coverage and write/amend Robolectric characterisation tests using the Robot pattern.
user_invocable: true

Verify UI Changes

Assess uncommitted UI changes, determine if characterisation tests are needed, and write them using this repo's Robot pattern. Prefer tests that exercise the real composable and assert on user-visible text/nodes, faking only the ViewState/callbacks at the edges.

Step 1: Identify What Changed

bash

git diff --name-only HEAD

Classify each changed file:

File location	Classification
Compose screens/composables under `android/app/src/main/.../ui/screens/`	UI change — likely needs a characterisation test
ViewModel, ViewState for a Compose screen	Behavior change — needs a characterisation test
`mediaprovider/`, `data/`, use cases	Logic change — unit test, not this skill
DI modules, navigation wiring	Wiring change — verify manually or via a Maestro flow

If no Compose UI files changed, stop — say "No UI changes detected, characterisation tests not needed."

Step 2: Find Existing Coverage

For each affected screen, look for its existing test trio next to the screen's ViewModel:

bash

find android/app/src/test -iname "*ScreenName*Test.kt" -o -iname "*ScreenName*Robot.kt"

Read the matching *Test.kt and *Robot.kt. Ask:

Does an existing test already exercise the changed behavior?
Would the existing test catch a regression if this change broke something?
Does the robot need updating (new test tag, changed content description, new interaction)?

If existing tests cover the change: Update them to match new behavior. Don't add redundant tests.

If no existing test covers the change: Write a new trio (Step 3).

Step 3: Write the Test

Each screen's tests live in three files alongside each other, e.g. android/app/src/test/java/com/simplecityapps/shuttle/ui/screens/library/songs/:

SongListTest.kt        # test cases
SongListRobot.kt       # selector/interaction encapsulation
SongListScenarios.kt   # ViewState factories

Robot responsibilities — keep it thin

setContent(viewState) — renders the composable with callback captures
assertTextDisplayed(text) / assertTextNotDisplayed(text) — hides node selectors
openContextMenu() — hides content description selectors
clickText(text) / clickMenuItem(text) — interaction primitives
Callback capture fields (lastAddedToQueue, lastDeleted, etc.) — avoid verbose lambda setup in tests
The robot hides selectors, not behaviour — tests compose primitives to describe what they verify. No screen-specific compound assertions.

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

Scenario factories

Top-level functions that construct ViewState with sensible defaults:

kotlin

readySongList(songs = listOf(createSong(name = "My Song")))
scanningSongList(Progress(50, 200))
emptySongList()
loadingSongList  // val, not a function — Loading has no parameters

Model factories

createSong(), createGenre(), createPlaylist() in android/app/src/test/java/com/simplecityapps/creationFunctions.kt. All parameters have defaults — override only what matters for the test.

Example test

kotlin

@Test
fun `context menu invokes onAddToQueue`() {
    val song = createSong(name = "Queue Me")
    robot.setContent(readySongList(songs = listOf(song)))
    robot.openContextMenu()
    robot.clickMenuItem("Add to Queue")
    robot.lastAddedToQueue shouldBe song
}

Known Robolectric limitation: FastScroller + DropdownMenu

The FastScroller overlay causes DropdownMenu popups to be immediately dismissed under Robolectric. Context menu tests that need dropdowns should render the list item composable directly (e.g. GenreListItem) rather than the full list. The robot encapsulates this — see GenreListRobot.setItemContent().

Step 4: Run and Verify

bash

./gradlew :android:app:testDebugUnitTest --tests "com.simplecityapps.shuttle.ui.screens.library.songs.SongListTest"

If the test fails, fix the test or the implementation — diagnose which is wrong before changing either.

When NOT to Write a Test

The change is a string/copy update and existing tests already assert on other elements of the same screen
The change is a dependency version bump with no behavior change
An existing characterisation test already covers the changed composable and would catch regressions

Files

Just SKILL.md in .claude/skills/verify-ui of timusus/Shuttle2.

Open the folder on GitHubat commit 116c579

Compare with similar skills

Verify UI 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.

Verify UI compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Verify UI this skilltimusus/Shuttle2	229	—	~1.1k	Automated safety check: Pass	Apache-2.0	yesterday
Improve Code Coveragealexvanyo/composelife	267	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Quality Test Pilotnekomangaorg/Neko	2.8k	—	~1.1k	Automated safety check: Pass	Apache-2.0	yesterday
Android Testingrcosteira79/android-skills	150	—	~2.1k	Automated safety check: Pass	MIT	18 days ago
Mocking With Mockitoskydoves/android-testing-skills	333	—	~4.5k	Automated safety check: Pass	Apache-2.0	4 mo ago
Mocking With Mockkskydoves/android-testing-skills	333	—	~4.1k	Automated safety check: Pass	Apache-2.0	4 mo ago

Similar skills

Improve Code Coverage
alexvanyo/composelife
Helps increment code coverage in this Kotlin Multiplatform project.
267 GitHub stars~1.1k tokensUpdated today
MobileAuto-check passed
Quality Test Pilot
nekomangaorg/Neko
Writes high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage.
2.8k GitHub stars~1.1k tokensUpdated yesterday
Testing & QAAuto-check passed
Android Testing
rcosteira79/android-skills
A skill your agent uses when writing, fixing, or refactoring Android/KMP code in Kotlin — a test-first (RED-GREEN-REFACTOR) foundation plus the Android/KMP test traps: Compose-test dispatching…
150 GitHub stars~2.1k tokensUpdated 18 days ago
Testing & QAAuto-check passed
Mocking With Mockito
skydoves/android-testing-skills
A skill your agent uses to wire Mockito (the dominant Android mocking framework, exclusively used by androidx itself) into a JVM unit-test suite.
333 GitHub stars~4.5k tokensUpdated 4 mo ago
Testing & QAAuto-check passed
Mocking With Mockk
skydoves/android-testing-skills
A skill your agent uses to wire MockK (the Kotlin-first mocking framework) into a JVM unit-test suite, especially when coroutines, singleton/object mocking, or constructor mocking dominate.
333 GitHub stars~4.1k tokensUpdated 4 mo ago
Testing & QAAuto-check passed
Java Testing
HoangNguyen0403/agent-skills-standard
Testing standards using JUnit 5, AssertJ, Mockito, Cucumber, and Spring Boot integration tests for Java.
570 GitHub stars~1k tokensUpdated yesterday
Testing & QAAuto-check passed

Questions about Verify UI

What does Verify UI do?

After Compose UI changes, assess test coverage and write/amend Robolectric characterisation tests using the Robot pattern. Verify UI is an agent skill from timusus/Shuttle2. After Compose UI changes, assess test coverage and write/amend Robolectric characterisation tests using the Robot pattern.

When should I use Verify UI?

Verify UI fits situations like: tasks that involve Test coverage; tasks that involve Android development.

How do I install Verify UI in Claude Code?

Run `npx skills add timusus/Shuttle2 --skill verify-ui -a claude-code`. Or copy the skill folder (.claude/skills/verify-ui in timusus/Shuttle2) into .claude/skills/verify-ui in your project. Claude Code loads it when a task matches its description.

How do I install Verify UI in Codex?

Run `npx skills add timusus/Shuttle2 --skill verify-ui -a codex`. Or copy the skill folder (.claude/skills/verify-ui in timusus/Shuttle2) into .agents/skills/verify-ui in your project. Codex loads it when a task matches its description.

Can I use Verify UI 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 timusus/Shuttle2 --skill verify-ui -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-ui, .gemini/skills/verify-ui, .github/skills/verify-ui and .opencode/skills/verify-ui in your project.

What does Verify UI need to run?

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

Does Verify UI access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Verify UI 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 Verify UI use?

Verify UI 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 Verify UI use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Verify UI?

Skills that share tags, products or a category with Verify UI: Improve Code Coverage (alexvanyo/composelife, 267 stars), Quality Test Pilot (nekomangaorg/Neko, 2.8k stars), Android Testing (rcosteira79/android-skills, 150 stars) and Mocking With Mockito (skydoves/android-testing-skills, 333 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify UI?

timusus (a GitHub user) maintains it in timusus/Shuttle2, which has 229 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.

Source: timusus/Shuttle2 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Verify UI

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

Verify UI Changes

Step 1: Identify What Changed

Step 2: Find Existing Coverage

Step 3: Write the Test

Robot responsibilities — keep it thin

Scenario factories

Model factories

Example test

Known Robolectric limitation: FastScroller + DropdownMenu

Step 4: Run and Verify

When NOT to Write a Test

Files

Compare with similar skills

Similar skills

More from timusus/Shuttle2

Related

Questions about Verify UI