TypingMindTypingMindThe best frontend for AI
Argent Android Emulator Setup logo

Argent Android Emulator Setup

OrganizationPopular
software-mansion
argent-android-emulator-setup

Set up and connect to an Android emulator using argent MCP tools. Use when starting a new session on Android, booting an emulator, getting a device serial, or before any UI interaction task.

Overview

Publishersoftware-mansion
Repositoryargent
Skill nameargent-android-emulator-setup
Stars
2.9K
Forks
124
Bundled files
Instructions only
LicenseApache-2.0
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by software-mansion on GitHub. Read the source before you install it.

Installation

Install the Argent Android Emulator Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/software-mansion/argent/tree/main/packages/skills/skills/argent-android-emulator-setup
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/software-mansion/argent.git /tmp/argent
mkdir -p .claude/skills
cp -r /tmp/argent/packages/skills/skills/argent-android-emulator-setup .claude/skills/argent-android-emulator-setup
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Argent Android Emulator Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Argent Android Emulator Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Argent Android Emulator Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

1. Prerequisites

  • Android SDK Platform Tools on PATH — provides adb.
  • Android Emulator on PATH — needed to boot AVDs. If you will only use an already-running emulator or a physical device, adb alone is sufficient.
  • An AVD created via Android Studio or avdmanager create avd.

Verify with adb version and emulator -list-avds.

2. Setup

  1. Find a ready device — call list-devices. Filter for entries with platform: "android". Ready devices (state: "device") come first. Pick the first serial (e.g. emulator-5554) unless the user specified one.
  2. Boot if needed — if nothing Android is ready, call boot-device with avdName: <name> from the same call's avds list. The tool transparently picks hot vs cold boot: it probes the AVD's default_boot snapshot, restores it under a tight deadline when usable, and falls back to a full cold boot otherwise. Hot path is typically ~30s; cold path takes 2–10 min. On any stage failure the tool kills the emulator process it started so your next call starts from a clean state.
  3. Metro (for React Native) — once a device is up, run adb -s <serial> reverse tcp:8081 tcp:8081 so the device can reach Metro on your host. Repeat if the device restarts.

3. Using the device

Pass the Android serial as udid to the unified interaction tools — gesture-tap, gesture-swipe, describe, screenshot, launch-app, keyboard, etc. Dispatch is automatic based on the id shape. See argent-device-interact for platform-neutral interaction tooling and the Android-specific gotchas section at the bottom of that skill.

4. Notes

  • Android TV / leanback AVDs boot through this exact flow (same boot-device + avdName), but they are focus-driven, not touch-driven — do not use gesture-tap/gesture-swipe on them. list-devices tags a leanback device with runtimeKind: "tv" (detected via the system feature list, not the serial — a TV AVD's serial looks just like a phone's). When you see runtimeKind: "tv", drive it with the focus-driven tools (describe / tv-remote / keyboard) and the argent-tv-interact skill (it covers Android TV as well as Apple TV, including the full TV setup flow).
  • Serials are the adb device id. iOS UDIDs and Android serials are not interchangeable, but you do NOT need to tell the tools which platform — dispatch is automatic.
  • describe on Android returns a shallower tree than iOS (no accessibility-service equivalent), but covers most tap-target discovery.
  • reinstall-app on Android always installs with -g so first-launch runtime permissions are pre-granted.
  • To stop the emulator, run adb -s <serial> emu kill from a shell (clean shutdown). Never pkill -9/kill -9 qemu — a hard kill leaves the userdata image dirty, after which cold boots can hang for many minutes doing recovery (runaway writes, boot_completed never flips). If an image gets into that state, boot once with -wipe-data to reset it.

Frequently asked questions

What does the Argent Android Emulator Setup AI skill do?

Set up and connect to an Android emulator using argent MCP tools. Use when starting a new session on Android, booting an emulator, getting a device serial, or before any UI interaction task.

Why use Argent Android Emulator Setup on TypingMind?

Because you install it once and use it with any model. Argent Android Emulator Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Argent Android Emulator Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/software-mansion/argent/tree/main/packages/skills/skills/argent-android-emulator-setup. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Argent Android Emulator Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Argent Android Emulator Setup?

As many as you like. As long as a model supports skills, you can use Argent Android Emulator Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Argent Android Emulator Setup AI skill free?

Yes. It is published on GitHub by software-mansion under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Release Openclaw Maintainer

openclaw
OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

82.2K
391K
11 files
View
openclaw logo

Release Openclaw Plugin Testing

openclaw
OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

82.2K
391K
1 files
View
openclaw logo

Solid

openclaw
OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

82.4K
391.7K
9 files
View
openclaw logo

Auto Qa

openclaw
OrganizationPopular

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

82.2K
391K
5 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇