Browser Control Skill

Goal

Finish the user’s real task reliably.
Prioritize successful completion and correct results over aggressive call minimization.

Operating Rules

1. Start with the intended action directly (navigate/open/act/evaluate). Do not run status as a pre-check.
2. Use snapshot only when refs are required for interaction (click/type/select/drag/scrollIntoView).
3. Prefer evaluate for extraction. Return structured data in one comprehensive call when possible.
4. Use condition waits by default (loadState/url → selector/text/textGone → fn). Avoid timeMs unless explicitly needed.
5. Before clicking potentially off-screen elements, run act.scrollIntoView on the ref first.
6. Keep context stable: once targetId is known, pass it in follow-up calls when supported.
7. Avoid blind loops: every extra call must have a clear purpose.

Reliability and Recovery