New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Emulator Check

by timusus in timusus/Shuttle2

Verify an S2 change on the WSL desktop emulator in minutes — build once, lease a lane, install, run the scripted playback checks (debug receivers) and Maestro UI flows, add a new check, stop the lane.

Apache-2.0Auto-check passedMobile

Install Emulator Check

skills CLI
$ npx skills add timusus/Shuttle2 --skill emulator-check -a claude-code

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

GitHub CLI
$ gh skill install timusus/Shuttle2 emulator-check --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/emulator-check .claude/skills/emulator-check && 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/

Facts

Skill name
emulator-check
GitHub stars
229
Token cost
~1.7k tokens
SKILL.md length
757 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
Apache-2.0

At a glance

Verify an S2 change on the WSL desktop emulator in minutes — build once, lease a lane, install, run the scripted playback checks (debug receivers) and Maestro UI flows, add a new check, stop the lane.

  • Works in 5 steps: A new support/scripts/checks/.sh,… → Only if taps are the subject: add… → Pause playback (s2-debug.sh PAUSE)… → …
  • Tasks that involve Mobile testing and debugging
  • SKILL.md covers Run it, Pieces, Adding a check and Screenshot tour, plus 1 more section
  • Calls adb and brew

What it does

Emulator Check is an agent skill from timusus/Shuttle2. Verify an S2 change on the WSL desktop emulator in minutes — build once, lease a lane, install, run the scripted playback checks (debug receivers) and Maestro UI flows, add a new check, stop the lane. Use before landing any user-visible change, when briefing an emulator-verification worker, or when writing a new Maestro flow or check script.

Its SKILL.md is about 1.7k 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 Mobile, covering Mobile testing and debugging. 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 Mobile testing and debugging

Example prompts

  • “/emulator-check”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. A new support/scripts/checks/.sh, sourcing _lib.sh: set up state with s2, wait with
  2. Only if taps are the subject: add support/maestro/.yaml, reusing support/maestro/nav/
  3. Pause playback (s2-debug.sh PAUSE) before any uiautomator or Maestro step. While music plays the UI
  4. Prefer adding a check that proves the fix over one-off manual steps, so the next change is covered too.
  5. A check whose subject is Compose navigation or state, not the device, belongs in a Robolectric test in

What it can do on your machine

Read from SKILL.md and the folder at commit 9cef5dd. 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:

    • adb
    • brew

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Emulator Check loads about 1.7k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 757 words of instructions outside code blocks.

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

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 9cef5dd, republished under its Apache-2.0 licence (© timusus). 757 words, ~1,660 tokens.

Download SKILL.mdSave it as .claude/skills/emulator-check/SKILL.md (or your agent's skills folder).
name
emulator-check
description
Verify an S2 change on the WSL desktop emulator in minutes — build once, lease a lane, install, run the scripted playback checks (debug receivers) and Maestro UI flows, add a new check, stop the lane. Use before landing any user-visible change, when briefing an emulator-verification worker, or when writing a new Maestro flow or check script.

Emulator check

Scripted, repeatable verification on a remote-emu.sh lane. Drive state with adb broadcasts; for anything the UI must show or be tapped, write or reuse a Maestro flow — not ad-hoc tap-text, uiautomator dumps or screenshot-and-look loops, which cost many turns and don't survive for the next change. A full run of the existing checks is minutes, not the 40+ a UI-driven worker used to take for the same ground.

Run it

One call, in the foreground, with a generous timeout:

bash
support/scripts/emu-verify.sh                   # builds/reuses the APK, runs the full check suite
support/scripts/emu-verify.sh --check restore-queue --flow support/maestro/nav/open-settings.yaml
support/scripts/emu-verify.sh --apk /tmp/s2-apk/<sha>.apk --no-seed --check rapid-skip

It starts a lane, installs, seeds the playback fixture, runs the named --check/--flow args (repeatable; checks/run-all.sh if neither is given), and always stops the lane on exit (trap), even on failure or Ctrl-C, unless --keep. Full command output goes to the log file it prints, not stdout; stdout stays to one line per setup step plus one PASS/FAIL line per check/flow. --help for the rest of the flags (--apk, --no-seed, --keep).

--remote <jellyfin|emby|plex> signs in and imports from a seeded server (seed-remote-provider.sh) instead of seeding local media, and exports S2_REMOTE=<server> so remote-reporting and remote-playback run instead of SKIPping. With --remote and no --check, only those two remote checks run, not the full local suite:

bash
support/scripts/emu-verify.sh --remote jellyfin
support/scripts/emu-verify.sh --remote plex --check remote-playback
  • Re-running the same flow/check after a small code change, on the lane you already leased and seeded this session? Add --no-reset: skips the ~2-3 min reset+reseed, since seed-test-media.sh --if-needed (always on) is a no-op when the fixture's already there (#412). Never use it for the landing verification -- only the default (reset every time) catches state a prior run left behind.
  • Run the whole script in the foreground. A headless worker that backgrounds it ends its run (#303).
  • Never start a local emulator or hand-roll sleep/getprop sys.boot_completed loops: start (which emu-verify.sh calls) already waits for boot (up to 300 s) and fails loudly. Those loops were the top source of 10-minute Bash timeouts in the Sep 2026 token sweep.
  • Another job building in the same worktree? Pass --apk <path> to skip Gradle there.
  • Lane 1 often belongs to another project; emu-verify.sh (via remote-emu.sh start) picks a free one.
Manual fallback

For a one-off command outside emu-verify.sh (a raw adb call, a different fixture, leaving the lane up to poke at by hand):

bash
support/scripts/remote-emu.sh start && eval "$(support/scripts/remote-emu.sh env)"
support/scripts/remote-emu.sh reset && support/scripts/remote-emu.sh install   # [N] <apk> for a prebuilt one
support/scripts/seed-test-media.sh playback --skip-onboarding
support/scripts/checks/run-all.sh               # PASS/FAIL per check, non-zero on failure
support/scripts/remote-emu.sh stop              # ALWAYS, even on failure

If a command fails with "device offline"/"device not found" mid-run, the tunnel dropped: s2-debug.sh and checks/*.sh already reconnect and retry once on their own; for a raw adb call run support/scripts/remote-emu.sh reconnect yourself first (no reboot, lease kept).

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

Pieces

NeedUse
Play, pause, skip, seek, remove from queue, shuffle/repeat, reimport, read state as JSONsupport/scripts/s2-debug.sh <ACTION> (the debug-receivers skill)
Ready-made checkssupport/scripts/checks/*.sh (queue-remove-current, rapid-skip, restore-position, restore-queue, folder-art)
Taps where the UI is the subjecta Maestro flow in support/maestro/, run by a checks/ wrapper that sets up state first
One-off taps, dumps, screenshotsremote-emu.sh tap-text / dump-texts, or the android-device skill with the env exports
Notification / lock screenadb shell cmd statusbar expand-notifications, remote-emu.sh lockscreen on
Emulator console (incoming call, ...)remote-emu.sh emu gsm call 5551234 / emu gsm cancel 5551234 (runs adb emu on the box; the console port isn't tunnelled)

Maestro: brew install mobile-dev-inc/tap/maestro (plain brew install maestro is an unrelated app). It only talks to the Mac's adb server on 5037, so pass --device "$(support/scripts/remote-emu.sh serial)".

Adding a check

  1. A new support/scripts/checks/<name>.sh, sourcing _lib.sh: set up state with s2, wait with wait_for <secs> "<python expr on s>", then assert with state <field>, and finish with pass or fail "<why>". run-all.sh picks it up automatically.
  2. Only if taps are the subject: add support/maestro/<name>.yaml, reusing support/maestro/nav/ subflows via runFlow for common navigation (see support/maestro/README.md) and selecting by visible text otherwise. Call it from the wrapper (see restore-queue.sh), or run it directly with emu-verify.sh --flow support/maestro/<name>.yaml. Each maestro test costs 10–20 s to start, so use one flow per check.
  3. Pause playback (s2-debug.sh PAUSE) before any uiautomator or Maestro step. While music plays the UI never goes idle and dumps fail.
  4. Prefer adding a check that proves the fix over one-off manual steps, so the next change is covered too.
  5. A check whose subject is Compose navigation or state, not the device, belongs in a Robolectric test in :android:app instead (support/maestro/CLASSIFICATION.md).

Screenshot tour

For design audits, support/scripts/design-shots.sh (via longjob.sh start design-shots -- ...) drives a fixed Maestro flow per screen (support/maestro/design/) across themes, text sizes and form factors and writes shots/<run>/ with a manifest.md; --help has the flags.

Reporting

Report PASS/FAIL per check with its key DUMP_STATE values, and screenshots only where the UI is the evidence: Read the PNG so it renders inline. Also confirm that the lane was stopped.

© timusus, 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 .claude/skills/emulator-check of timusus/Shuttle2.

Open the folder on GitHubat commit 9cef5dd

Compare with similar skills

Emulator Check 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.

Emulator Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Emulator Check this skilltimusus/Shuttle2229—~1.7kAutomated safety check: PassApache-2.0
Phone HarnessShawnPana/phone-harness3.2k—~4.3kAutomated safety check: PassMIT
Mobile QAtloncorp/tlon-apps107—~2.4kAutomated safety check: PassMIT
Androidyang1ming/android-harness176—~259Automated safety check: PassMIT
Debug Bridgegetknit/knit131—~2.2kAutomated safety check: PassGPL-3.0
Capturing Screenshots And Screenrecordskydoves/android-testing-skills333—~3.7kAutomated safety check: PassApache-2.0

Similar skills

  • Phone Harness

    ShawnPana/phone-harness

    Control the user's phone — an iPhone through the Mac's iPhone Mirroring window, an Android over adb, or a rented cloud Android: open apps, tap, type, swipe, read the screen.

    3.2k GitHub stars~4.3k tokensUpdated 10 days ago
    MobileAuto-check passed

  • Mobile QA

    tloncorp/tlon-apps

    Run a mobile QA checklist on a physical Android device over adb for tlon-apps, then triage what fails into fixes.

    107 GitHub stars~2.4k tokensUpdated today
    MobileAuto-check passed

  • Android

    yang1ming/android-harness

    Direct Android device control through ADB. An agent skill from yang1ming/android-harness.

    176 GitHub stars~259 tokensUpdated 2 mo ago
    MobileAuto-check passed

  • Debug Bridge

    getknit/knit

    Drive and verify Knit on a device or emulator through the headless debug bridge (am broadcast to app.getknit.knit.debug.<ACTION, replies as JSON) — send a message on one phone and confirm it landed…

    131 GitHub stars~2.2k tokensUpdated 4 days ago
    MobileAuto-check passed

  • Capturing Screenshots And Screenrecord

    skydoves/android-testing-skills

    A skill your agent uses to capture visual artefacts from a device for test failures, golden image generation, QA repro, and demo videos.

    333 GitHub stars~3.7k tokensUpdated 4 mo ago
    MobileAuto-check passed

  • Android Emulator Skill

    Moustachauve/WLED-Android

    Production-ready scripts for Android app testing, building, and automation.

    169 GitHub starsUsed in 1 repo~911 tokens
    MobileAuto-check passed

More from timusus/Shuttle2

All 13 skills in this repo

  • Android Coroutine Testing

    timusus/Shuttle2

    Comprehensive guidance for writing deterministic tests for Android code using Kotlin coroutines.

    229 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Debug Receivers

    timusus/Shuttle2

    Drive the S2 debug build's playback and queue over ADB broadcasts — play the whole library, play/pause, skip, seek, remove a queue item, toggle shuffle/repeat, dump playback state as JSON, reimport…

    229 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Deploy Android

    timusus/Shuttle2

    Deploy the Android app to the Play Store via GitHub Actions.

    229 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Reply Reviews

    timusus/Shuttle2

    Weekly Play Store review flow for S2: fetch new reviews, draft replies, get owner approval, then post.

    229 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Check

    timusus/Shuttle2

    Run lint + unit tests, investigate and fix failures. An agent skill from timusus/Shuttle2.

    229 GitHub stars~449 tokensUpdated yesterday
    Auto-check passed

  • Commit

    timusus/Shuttle2

    Analyse working tree changes, group them into logical atomic commits, and create well-structured conventional commits with module scopes.

    229 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about Emulator Check

What does Emulator Check do?

Verify an S2 change on the WSL desktop emulator in minutes — build once, lease a lane, install, run the scripted playback checks (debug receivers) and Maestro UI flows, add a new check, stop the lane. Emulator Check is an agent skill from timusus/Shuttle2. Verify an S2 change on the WSL desktop emulator in minutes — build once, lease a lane, install, run the scripted playback checks (debug receivers) and Maestro UI flows, add a new check, stop the lane.

When should I use Emulator Check?

Emulator Check fits situations like: tasks that involve Mobile testing and debugging.

How do I install Emulator Check in Claude Code?

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

How do I install Emulator Check in Codex?

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

Can I use Emulator Check 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 emulator-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/emulator-check, .gemini/skills/emulator-check, .github/skills/emulator-check and .opencode/skills/emulator-check in your project.

What does Emulator Check need to run?

Going by SKILL.md and its folder, Emulator Check needs the command-line tools its instructions call (adb and brew). Our summary lists: Python 3.

Does Emulator Check access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Emulator Check 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 Emulator Check use?

Emulator Check 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 Emulator Check use?

About 1.7k tokens (SKILL.md is roughly 6.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 Emulator Check?

Skills that share tags, products or a category with Emulator Check: Phone Harness (ShawnPana/phone-harness, 3.2k stars), Mobile QA (tloncorp/tlon-apps, 107 stars), Android (yang1ming/android-harness, 176 stars) and Debug Bridge (getknit/knit, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Emulator Check?

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 7, 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.