genymotion

Manage Genymotion Android virtual devices via gmsaas or gmtool workflows.

5|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Genymobile/genymotion-skills --skill genymotion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: genymotion
Source: https://github.com/Genymobile/genymotion-skills/tree/main
Command: npx skills add https://github.com/Genymobile/genymotion-skills --skill genymotion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures AI assistants orchestrate Genymotion device lifecycles without guesswork, covering cloud and local platforms while preventing misconfigurations, unexpected charges, and security slips.

Core Features & Use Cases

  • Unified platform handling: Detects whether to drive gmsaas for Genymotion SaaS or gmtool for the desktop app and guides the user through the correct workflow.
  • Prerequisite verification: Checks for the required binaries in PATH, prompts for virtualenv paths when needed, validates authentication/licensing, and references setup guides when components are missing.
  • Operational guardrails: Walks through starting/stopping instances, connecting ADB, embedding cloud streams via the device web player, and orchestrating CI/CD pipelines while always verifying state changes before reporting success.

Quick Start

Ask the Genymotion skill to launch a cloud instance, connect ADB, and install your APK.

Frequently Asked Questions about genymotion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Genymotion Android emulator lifecycle management in a CI/CD pipeline?

To automate Genymotion Android emulator lifecycle management via CI/CD, the skill detects whether to drive gmsaas for cloud or gmtool for desktop, verifies binaries in PATH, validates authentication, and orchestrates start, stop, and ADB connection state changes before reporting success.

What is the difference between using gmsaas and gmtool for Genymotion devices?

The difference between gmsaas and gmtool lies in their target environments: gmsaas drives Genymotion SaaS cloud emulators, while gmtool manages local Genymotion Desktop virtual devices, with the skill detecting the correct workflow based on your platform.

How do I connect ADB to a Genymotion cloud emulator from the command line?

To connect ADB to a Genymotion cloud emulator, the skill uses gmsaas to launch the instance, retrieves the connection parameters, and executes the ADB connect command, verifying the state change before confirming a successful link.

Do I need a license or authentication to start Genymotion cloud emulators?

Yes, starting Genymotion cloud emulators requires verified authentication for gmsaas or valid licensing for gmtool, with the skill checking prerequisites and prompting for virtualenv paths or referencing setup guides if components are missing.

Can I embed a Genymotion cloud device stream into a web player?

Yes, you can embed a Genymotion cloud device stream via the device web player, allowing the skill to orchestrate cloud instances through gmsaas while providing the stream interface for integration into your own environment.

Why does my Genymotion device task fail with a missing binary error?

Genymotion device tasks fail with missing binary errors when gmsaas or gmtool are not found in PATH, requiring the skill to prompt for the correct virtualenv path or reference setup guides to install the missing components.