Menu
Optional browser automation workflow for interactive browser tasks, Playwright-style automation, and stable scraping/testing patterns.
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
| name | browser-automation |
| description | Optional browser automation workflow for interactive browser tasks, Playwright-style automation, and stable scraping/testing patterns. |
| risk | safe |
| source | codex-max |
| origin | Antigravity-adapted |
| date_added | 2026-04-19 |
Use browser-automation for browser-driven tasks that are more interactive or automation-oriented than the normal E2E test workflow.
This includes repeatable browser actions, scraping-style flows, UI automation, popup handling, and resilient selector/wait strategies.
This skill is installed as an optional library skill, not a core routing default.
waitForTimeout-style habitsState clearly:
Prefer:
Avoid defaulting to brittle DOM-shape selectors.
Wait for:
Avoid arbitrary time delays unless no better synchronization point exists.
When needed, retain:
When this skill is used, the result should include:
e2e-testing โ for formal user-journey verificationdocumentation-lookup โ for current browser/tooling API usagesearch-first โ before adding a browser automation dependency or wrapperMANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session recovery after /clear.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Legacy compatibility alias for task-router-lite. Keeps older codex-max references working while using a thin Phase PLAN routing model.
Thin Phase PLAN router for codex-max. Select at most one primary execution skill and one optional secondary skill from the installed local skill surface.
Use when a significant technical decision should be recorded with context, alternatives, and consequences so the reasoning survives beyond the current session.