// MCP dev-first mobile loop for reliable screenshot-observe-action execution, grounded interactions, and conversion of successful exploratory paths into tests.
| name | revyl-mcp-dev-loop |
| description | MCP dev-first mobile loop for reliable screenshot-observe-action execution, grounded interactions, and conversion of successful exploratory paths into tests. |
Use this skill for the full flow:
Always prefer dev-loop flow before plain device-only flows:
start_dev_loop.screenshot() and begin interaction.Fallback to plain device session only when dev loop is unavailable.
start_dev_loop.next_steps as advisory only.screenshot() before state-dependent actions.target with natural language descriptions (for example target="Sign In button"); use raw x,y only as fallback.For each iteration:
screenshot()target.screenshot() to verify.Short deterministic burst allowance:
When a flow succeeds:
create_test(name="...", platform="ios", yaml_content="...")run_test(test_name="...")get_test_status(task_id="...")Create robust Revyl E2E tests using CLI commands from app source analysis or exploratory sessions.
Create and maintain Revyl tests through MCP tools using create/update operations and execution feedback loops.
Analyze failed Revyl test, workflow, and device-session reports via CLI to classify real bugs, flaky tests, infra issues, setup failures, or test-design improvements.
Native Android leaf recipe for test-only auth bypass deep links using Revyl launch intent extras.
Expo and Expo Router leaf recipe for test-only auth bypass deep links using Revyl launch variables.
Flutter leaf recipe for test-only auth bypass deep links using Revyl launch variables.