Menu
Create and maintain Revyl tests through MCP tools using create/update operations and execution feedback loops.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Keep a repo's Revyl remote build mirrored with its CI pipeline - update both in the same PR and debug drift between them.
Revyl conventions for Cursor Cloud/background agents - headless VM rules, remote builds, artifact evidence, session cleanup, and PR flow.
MCP dev-first mobile loop for reliable screenshot-observe-action execution and grounded interactions.
Set up test-only auth bypass for Revyl runs across Expo, React Native, native iOS, native Android, and Flutter apps.
Generic CLI-first Revyl dev loop for hot reload, rebuild-loop, and device exploration.
Create robust Revyl E2E tests using CLI commands from app source analysis or exploratory sessions.
| name | revyl-mcp-create |
| description | Create and maintain Revyl tests through MCP tools using create/update operations and execution feedback loops. |
Use this skill when tests should be authored and managed through MCP tools.
create_test(name="...", platform="ios", yaml_content="...")update_test(test_name_or_id="...", yaml_content="...", force=true)run_test(test_name="...")get_test_status(task_id="...")Use the backend YAML contract returned by get_schema().
- type: instructions
step_description: "Tap Log in."
- type: validation
step_description: "The dashboard is visible."
- type: code_execution
script: "seed-user"
variable_name: seeded_user_id
- type: module_import
module: "login-flow"
- type: if
condition: "Is a cookie banner visible?"
then:
- type: instructions
step_description: "Tap Accept."
else:
- type: instructions
step_description: "Continue."
- type: while
condition: "Is there a Load More button visible?"
body:
- type: instructions
step_description: "Tap Load More."
For new authored YAML, use script for code execution and module for module imports. Legacy UUID forms may still parse for compatibility, but do not generate them.
If shared steps appear in 3+ tests:
list_modules()insert_module_block(module_name_or_id="...")