
maestro-e2e
E2E UI testing with Maestro for iOS, Android, Flutter, React Native, and Web
- Installs
- 533
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/raphaelbarbosaqwerty/maestro-dev-skills --skill maestro-e2e- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads maestro-e2e automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
When to use
Use this skill whenever you are:
- Creating E2E, UI, or integration tests
- Testing login, registration, or navigation flows
- Handling permission dialogs (camera, location, notifications)
- Debugging test failures or exploring UI hierarchy
- Working with Maestro test files (.yaml)
Captions
When dealing with native permission dialogs, load the ./rules/permissions.md file for platform-specific information.
When working with Flutter apps, load the ./rules/platforms/flutter.md file for Semantics patterns.
How to use
Read individual rule files for detailed explanations and code examples:
Core
- rules/installation.md - Installing Maestro on macOS, Linux, and Windows
- rules/test-structure.md - YAML test structure, appId, env variables, and flow definition
- rules/commands.md - Complete reference of 40+ Maestro commands
- rules/selectors.md - Element targeting with id, text, index, and matchers
- rules/assertions.md - assertVisible, assertNotVisible, assertTrue, and AI assertions
- rules/interactions.md - tapOn, inputText, scroll, swipe, and gesture commands
- rules/permissions.md - iOS vs Android permission configuration and dialog handling
Platforms
- rules/platforms/android.md - Android-specific: ADB, permission dialogs, emulators
- rules/platforms/ios.md - iOS-specific: auto-dismiss dialogs, simulators, limitations
- rules/platforms/flutter.md - Flutter integration using Semantics and identifier
- rules/platforms/react-native.md - React Native with testID and accessibilityLabel
- rules/platforms/web.md - Desktop browser testing with Chromium
Advanced
- rules/advanced/parameters.md - Environment variables, external params, ${} syntax
- rules/advanced/conditions.md - Conditional execution with when: visible, platform
- rules/advanced/nested-flows.md - Reusable subflows with runFlow command
- rules/advanced/javascript.md - evalScript, runScript, and GraalJS support
- rules/advanced/waiting.md - extendedWaitUntil, waitForAnimationToEnd
- rules/advanced/repeat-retry.md - Repeat and retry patterns for flaky tests
Additional
- rules/debugging.md - Maestro Studio, hierarchy inspection, troubleshooting
- rules/screenshots.md - Screenshots, video recording, and visual evidence
- rules/ci-integration.md - GitHub Actions, GitLab CI, Maestro Cloud
- rules/best-practices.md - Semantic identifiers, atomic tests, project structure
FAQ
What does the maestro-e2e skill do?
E2E UI testing with Maestro for iOS, Android, Flutter, React Native, and Web
How do I install maestro-e2e?
Run npx skills add https://github.com/raphaelbarbosaqwerty/maestro-dev-skills --skill maestro-e2e in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/maestro-e2e/ (personal) or .claude/skills/maestro-e2e/ (project).
Which AI agents can use maestro-e2e?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is maestro-e2e safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains maestro-e2e?
It is published by raphaelbarbosaqwerty in raphaelbarbosaqwerty/maestro-dev-skills. It has 533 recorded installs.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work