Skip to content
Back to skills

Android Emulator

ASecurity

Android emulator or AVD work. Use before launching, scripting or briefing an agent to use the Android emulator (device passes, screenshots, gfxinfo, adb on an emulator). Loading it is a required step before the first launch. Headless launches are banned.

  • 7 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added October 16, 2026
ai-agentsdebugging

Security analysis

A100/100

Scanned November 11, 2026

npx -y skills add Aquaticats/Monochromatic --skill android-emulator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Android Emulator?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Android Emulator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aquaticats-android-emulator/badge)](https://www.skillsdirectory.com/skills/aquaticats-android-emulator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: android-emulator
description: >-
  Android emulator or AVD work. Use before launching, scripting or briefing an agent
  to use the Android emulator (device passes, screenshots, gfxinfo, adb on an emulator).
  Loading it is a required step before the first launch. Headless launches are banned.
---

# Android emulator

## Launch

EMW:
 Android emulators run headful on the host GPU as their own systemd user unit;
 never `-no-window`,
 `xvfb-run`,
 or a container (headless launches crashed and hung for hours).
Launch fails:
 stop and report the error.

EMB:
 Briefs for agents that use an emulator repeat the headful rule and name the launch form in
 `doc/troubleshooting/android-emulator-37-software-renderer-sigsegv.md`;
 a brief never permits `-no-window`.

The launch form is the section "Working agent launch:
headful,
host GPU,
no container" of that document:
`systemd-run --user --unit=<name> --collect --property=MemoryMax=12G` with the display environment set,
`-gpu host`,
a private reflink copy of the owned AVD,
and its own adb port.
Read the section before writing the command;
it lists the `HOME`,
`ANDROID_USER_HOME` and `ANDROID_AVD_HOME` the copy needs.

## Use and shutdown

EMA:
 Always allow USB debugging on an emulator:
 accept the authorization dialog with always allow from this computer ticked,
 and never ask the user to approve it.

EMS:
 Never run `wm density` or `wm size` on an emulator;
 change display size through Settings,
 record settings before the pass,
 and restore them after.

EMD:
 Shut an emulator down gracefully:
 `sync`,
 wait 8 seconds,
 `sync`,
 then `adb emu kill`;
 never kill the unit while the guest writes.

EMP:
 Drive a private copy of the owned AVD,
 never the owned AVD itself,
 with captures of invented libraries only (no private names or status bars).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.