What is maestro-analyze?

A troubleshooting guide for failed Maestro tests on an iOS Simulator. Maestro is a tool that runs mobile app tests from written step-by-step flow files.

Reading the latest test result, reconstructing the failed sequence, comparing it with the app code, checking element selectors, and explaining why a mobile test stopped.

It helps identify whether a failure came from the test steps, the app's current screen, or selectors that no longer match visible controls.

maestro-analyze — Skill for Claude Code by parisgroup-ai

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add parisgroup-ai/imersao-ia-setup --skill maestro-analyze

Clone the repo

git clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setup

Made for: Claude Code.

Or install imersao, the plugin that ships this one along with the rest of its 51 skills, 7 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/maestro-analyze/github.svg)](https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/maestro-analyze)

Your own site

<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/maestro-analyze"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/maestro-analyze/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/maestro-analyze"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/maestro-analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,556 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00068	$0.01556
Opus 5	$0.00034	$0.00778
Sonnet 5	$0.00014	$0.00311
Haiku 4.5	$0.00007	$0.00156

Measured 12d ago against content hash 6e8016dfd9df, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

maestro-analyze scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/imersao/skills/maestro-analyze/SKILL.md · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

maestro-analyze - Maestro Failure Analysis

Analyze Maestro flow failures with step reconstruction, code correlation, selector validation, and pattern matching.

Usage

/maestro-analyze                # Analyze last run (from maestro-run-result.yaml)
/maestro-analyze <flow>         # Analyze specific flow

Analysis Steps

Step 1: Load Last Run

cat apps/mobile/maestro-run-result.yaml

If no result file exists, prompt user to run /maestro-run first.

Step 2: For Each Failure, Reconstruct Flow Steps

Read the failing YAML flow and the Maestro output to reconstruct what happened:

failure_timeline:
  flow: "auth/login.yaml"
  steps:
    - step: "launchApp (clearState: true)"
      status: "ok"
    - step: "waitForAnimationToEnd"
      status: "ok"
    - step: "tapOn: 'Email'"
      status: "ok"
    - step: "inputText: ${TEST_EMAIL}"
      status: "ok"
    - step: "tapOn: 'Sign In'"
      status: "timeout"
      error: "Element 'Sign In' not found after 5000ms"

  app_state:
    screen: "login"
    visible_elements: ["Email field", "Password field", "Log In button"]

Step 3: Code Correlation

For each failure, correlate with app source code:

code_correlation:
  failing_selector: "Sign In"
  selector_type: "text"

  search_results:
    - query: "grep -r 'Sign In' apps/mobile/app/"
      found: false
    - query: "grep -r 'Log In' apps/mobile/app/"
      found: true
      file: "apps/mobile/app/(auth)/login.tsx"
      line: 42

  suggestion:
    action: "flow-update"
    description: "Button text is 'Log In', not 'Sign In'. Update flow selector."
    confidence: 0.95

Correlation checks (in order):

Text selectors — grep for the exact text in app source (*.tsx files)
testID selectors — grep for the testID prop in components
Sub-flow references — verify shared flow paths are correct
Environment variables — check if ${TEST_EMAIL} etc. are set
mockNetwork paths — verify API path regex matches actual tRPC endpoints
Tab names — verify tab labels match i18n keys in apps/mobile/i18n/en.json

Read the full file on GitHub · 205 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 205 lines · 68 tokens per session scan A 6e8016dfd9df

Subscribe to this mod's changes

maestro-analyze is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,556 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code E2E testing Mobile Testing ai-skills bootcamp claude-code-plugin pg-tooling

test-native-extension

Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…

microsoft/power-platform-skills · 211 tokens

asc-shots-pipeline

Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…

rorkai/app-store-connect-cli-skills · 79 tokens

maestro-analyze