# Browser Automation

> Browser Automation Capability

- Skill: `lensetek/browser-automation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lensetek/browser-automation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lensetek/browser-automation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lensetek (https://skillmd.com/u/lensetek)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lensetek/browser-automation

---

# Browser Automation Capability

## When to Use

Use this capability for opening pages, navigating web apps, clicking UI, filling forms, taking screenshots, testing landing pages, checking responsive behavior, and verifying served frontend behavior.

## Preferred Implementation

- **Chrome DevTools MCP (`chrome-devtools-mcp`):** Use the `chrome-devtools` MCP server tools (e.g., `chrome-devtools/navigate_page`, `chrome-devtools/click`, `chrome-devtools/take_screenshot`) as the primary method for browser automation.
  - **Responsive Testing:** Always use `chrome-devtools/emulate` or `chrome-devtools/resize_page` to verify page layouts using a **mobile-view first** approach.
  - **Performance & QA:** Use performance tracing or Lighthouse audits to verify loading speed.
  - **Credential Safety:** Ensure that browser sessions do not cache sensitive credentials (e.g., run the server with `--isolated` or avoid saving cookies/auth headers in public scopes) to prevent credential leaks.
- Use programmatic scripts (e.g., Puppeteer, Playwright) or in-app connectors when repeatable, custom QA flows are required.
- Use OS-level Computer Use only as a last resort if standard API/protocol-based automation fails.

## Inputs

- URL or local file path.
- Objective.
- Viewport/device targets.
- Allowed actions.
- Credentials policy and login state.
- Expected evidence: screenshot, notes, or test result.

## Outputs

- Browser QA Report.
- Screenshots or visual findings.
- Interaction log.
- Broken links, console errors, layout issues, or accessibility concerns.
- Recommendation and next action.

## Security and Ethics

- Do not enter secrets unless the user explicitly approves a secure login flow.
- Do not expose cookies, tokens, private URLs, or account details in reports.
- Treat public frontend, browser JavaScript, and public assets as non-secret surfaces.