agent-device

Automate iOS and Android device interactions for UI navigation and snapshots.

28|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/bidah/react-native-hifi --skill agent-device-bidah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-device
Source: https://github.com/bidah/react-native-hifi/tree/main/skills/agent-device
Command: npx skills add https://github.com/bidah/react-native-hifi --skill agent-device-bidah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Navigating and automating interactions on iOS simulators/devices and Android emulators/devices is complex, and this skill provides the deterministic flows, guardrails, and session rules needed to reliably tap, type, snapshot, and debug with minimal context switching.

Core Features & Use Cases

  • Canonical Flows: Normal interaction, debug/crash, replay maintenance, session-bound automation, and remote tenant lease flows cover common QA and troubleshooting work.
  • Target and Session Control: Select or scope devices, bind sessions, enforce lock policies, and pin serials/UDIDs so commands run deterministically across simulators, physical devices, and remote daemons.
  • Command Reference & Guardrails: Snapshot/diff guidance, batching, logging, performance metrics, permissions, and remote tenancy references describe how to capture state, replay selectors, and monitor crash or tenant telemetry.

Quick Start

Request the agent-device skill to open the desired mobile app on the target simulator, capture a snapshot, and perform the necessary tap or fill action.

Frequently Asked Questions about agent-device

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

FAQPage Schema
How do I automate mobile QA flows for iOS and Android devices?▼

Automating mobile device interactions requires deterministic flows and session guardrails. This approach lets you reliably tap, type, snapshot, and debug iOS simulators or Android emulators with minimal context switching.

Can I bind a QA session to a specific iOS simulator or Android emulator?▼

Yes, session binding lets you select or scope specific devices, pin serials or UDIDs, and enforce lock policies. This ensures commands run deterministically across your chosen iOS or Android targets.

How do I capture and verify UI state during mobile debugging?▼

Capture UI state by taking snapshots and applying snapshot diff verification. This is guided by structured logging and performance metrics to monitor crashes and verify selector replays during debugging.

What is the best way to handle remote tenant orchestration for mobile devices?▼

Remote tenant orchestration uses session-isolated leases and remote tenant telemetry to manage devices. Canonical flows provide the structured guardrails needed to coordinate remote daemons and troubleshoot multi-tenant scenarios.

Does mobile device automation support replay maintenance for selectors?▼

Yes, replay maintenance is a canonical flow that updates selectors and maintains automation scripts. It works alongside snapshot guidance and batching to keep UI interactions stable across app updates.

When should I avoid using automated device control for QA?▼

Avoid automated device control when you lack session-isolated leases or when remote daemon targets are unavailable. Without structured guardrails and session binding, deterministic command execution across devices cannot be guaranteed.