agent-device

Control iOS simulators and Android devices via a unified command-line interface.

7.2k|378|Updated Dec 20, 2021
One-click install
npx skills add https://github.com/Shopify/flash-list --skill agent-device-shopify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-device
Source: https://github.com/Shopify/flash-list/tree/main/.claude/skills/agent-device
Command: npx skills add https://github.com/Shopify/flash-list --skill agent-device-shopify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a unified interface for interacting with iOS simulators and Android emulators/devices, ensuring consistent and reliable automation across platforms.

Core Features & Use Cases

  • Cross-Platform Control: Manage both iOS simulators and Android emulators/devices using a single tool.
  • Snapshot-Based Interaction: Precisely target UI elements using accessibility tree snapshots for reliable automation.
  • Fallback Screenshot Verification: Use screenshots for visual confirmation when accessibility data is insufficient.
  • Use Case: Automate the testing of a mobile application by navigating through its screens, filling out forms, and verifying UI elements on both iOS and Android simulators.

Quick Start

Use agent-device to open the 'FlatListPro' app on the 'iPhone 16' simulator.

Frequently Asked Questions about agent-device

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

FAQPage Schema
How do I automate UI testing on both iOS simulators and Android emulators using a single tool?

Mobile automation across iOS simulators and Android emulators is facilitated through a unified command-line interface, enabling programmatic device control, session management, and cross-platform command execution for deterministic testing.

How does snapshot-based interaction work for mobile automation?

Snapshot-based interaction targets UI elements using accessibility tree snapshots, ensuring precise and reliable automation. It falls back to screenshot verification to visually confirm elements when accessibility data is insufficient.

Can I control physical Android devices or only emulators with this mobile automation approach?

Android device control supports both physical devices and emulators. The unified interface targets specific hardware or virtual instances using session management for deterministic mobile application automation.

What is the best way to target specific UI elements during automated app interaction?

The best way to target UI elements is by utilizing accessibility tree snapshots for precise programmatic manipulation. Screenshot verification serves as a fallback when accessibility data is insufficient.

Does cross-platform device control require separate scripts for iOS and Android?

Cross-platform device control does not require separate scripts. A unified command-line interface manages both iOS simulators and Android emulators, executing commands across platforms for consistent automation.

Why use accessibility tree snapshots instead of just screenshots for UI testing?

Accessibility tree snapshots provide precise, deterministic targeting of UI elements for reliable automation. Screenshots are used only as a visual confirmation fallback when accessibility data is insufficient.