Revyl MCP Dev Loop Skill

Use this skill for the full flow:

1. Start dev loop equivalent.
2. Execute screenshot-observe-action cycles.

Default Operating Mode

Always prefer dev-loop flow before plain device-only flows:

1. Call start_dev_loop.
2. On success, share viewer_url as a clickable link and confirm the session is active. When the inline Revyl app exposes Open live device, the user may use it to hand the URL to the host browser; the link remains the portable fallback.
3. On a setup failure, follow the single structured remediation action and retry start_dev_loop once.
4. Call screenshot() and begin interaction.

Fallback to plain device session only when dev loop is unavailable.

Execution Guardrails