maestro-explore

Explore mobile app UI hierarchies via Maestro MCP to locate specific screens or components.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/luigiinred/dotfiles --skill maestro-explore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro-explore
Source: https://github.com/luigiinred/dotfiles/tree/main/dot_cursor/skills/maestro-explore
Command: npx skills add https://github.com/luigiinred/dotfiles --skill maestro-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users find specific pages, screens, or components within a mobile application by intelligently navigating and inspecting the live device.

Core Features & Use Cases

  • Guided Exploration: Iteratively inspects the app's UI hierarchy and screenshots to locate targets.
  • Automated Navigation: Executes taps, scrolls, and assertions using Maestro MCP to move through the app.
  • Use Case: When a user asks "How do I find the settings screen?" or "Locate the 'add new user' button", this Skill can systematically explore the app to provide the exact steps.

Quick Start

Use the maestro-explore skill to find the 'payment history' screen on the connected device.

Frequently Asked Questions about maestro-explore

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

FAQPage Schema
How do I navigate to a specific screen in a mobile app when I don't know the path?

You can navigate to a specific screen by iteratively inspecting the app's UI hierarchy and executing taps or scrolls to locate the target. This approach systematically explores the mobile app to find the desired page without needing the exact path.

How does AI guided app exploration work for locating UI elements?

AI guided app exploration works by iteratively inspecting the live device's UI hierarchy and screenshots. It executes taps, scrolls, and assertions to move through the mobile application until it locates the requested user interface elements.

Do I need Maestro MCP to explore and find mobile app components?

Yes, you need Maestro MCP for execution and device interaction. It is a required dependency for inspecting the live device and automating the navigation steps to locate specific components within the application.

What's the best way to automate finding the settings screen on a connected device?

The best way is to use an automated exploration tool that inspects the live UI hierarchy and screenshots. It will systematically tap and scroll through the app on your connected device to locate the settings screen.

Can I use UI automation to locate an add new user button without knowing its exact location?

Yes, UI automation can locate an add new user button by iteratively inspecting the application's interface. The tool automatically navigates through screens and interacts with elements until it finds the target button.

Why does my mobile testing script fail to find dynamically loaded UI components?

Mobile testing scripts may fail if they rely on static paths instead of iteratively inspecting the live UI hierarchy. Systematically exploring the app by evaluating screenshots and executing taps adapts to dynamically loaded components.