Automated summary
Automates browser actions such as navigation, screenshots, form filling, data extraction, and UI verification with persistent page state.
Strengths
- Uses ARIA snapshots to interact with elements without complex CSS selectors.
- Persists page state across scripts, enabling multi-step workflows.
- Provides screenshot feedback for visual verification.
Limitations
- Requires a separate browser server to be running.
- Code inside page.evaluate() must be plain JavaScript, not TypeScript.
- Tied to the custom Otto client library, not a standard tool.
When you need to visually inspect a UI, automate user interactions, or extract data from a frontend with persistent state across steps.
For simple static scraping or when the UI changes frequently enough that ARIA selectors become unreliable.
Security analysis
CautionThe skill provides a browser automation toolkit that requires node process execution and directory creation. These tools are used legitimately for starting a server, running scripts, and managing screenshots. No destructive or exfiltrating commands are instructed, but the allowed tools are powerful and could be misused if combined with malicious instructions. Rating as 'caution' reflects the legitimate but potent capabilities.
- •Uses Bash(node *) to execute arbitrary Node.js scripts, which can perform filesystem access and network requests.
- •Includes Bash(mkdir *) for directory creation, which is powerful but necessary for the skill's workflow.
Examples
Navigate to http://localhost:3000, take a screenshot, and describe the page structure using an ARIA snapshot.Fill the email field with 'test@example.com' and password with 'secret', then click the login button and verify the dashboard page loads.Extract all rows from the pricing table on the page and save them as a JSON file.name: browser description: Browser automation with persistent page state for navigation, screenshots, forms, data extraction, and testing. Use when inspecting UI, taking screenshots, filling forms, extracting page data, verifying frontend behavior, or automating browser workflows. argument-hint: [url | explore | verify | extract] model: opus allowed-tools: Read, Bash(node *), Bash(mkdir *)
Argument: $ARGUMENTS
| Command | Behavior |
|---------|----------|
| {url} | Navigate to URL, capture screenshot and ARIA snapshot |
| explore | Interactive exploration - navigate, inspect, understand UI |
| verify {description} | Verify specific UI behavior or state |
| extract {description} | Extract specific data from the frontend |
Choosing Your Approach
- Local/source-available sites: Read source code first to write selectors directly
- Unknown layouts: Use
getAISnapshot()for element discovery andselectSnapshotRef()for interactions - Visual feedback: Take screenshots to observe results
Setup
Start the browser server before running scripts:
node skills/otto/lib/browser/server.js &
Wait for "Ready" message, then connect:
import { connect, waitForPageLoad } from 'skills/otto/lib/browser/client.js'
const client = await connect({ headless: true })
Writing Scripts
Run scripts using npx tsx with heredocs for inline execution.
Key Principles:
- Small scripts doing one action each
- Evaluate state at completion
- Use descriptive page names
- Call
await client.disconnect()to exit (pages persist) - Use plain JavaScript in
page.evaluate()(no TypeScript syntax)
Workflow Loop
- Write script performing one action
- Run and observe output
- Evaluate results and current state
- Decide: complete or need another script?
- Repeat until task complete
Navigate & Capture
Determine the dev server URL from package.json scripts, running processes, or project config.
const page = await client.page('main')
await page.goto(url) // e.g., http://localhost:5173
await waitForPageLoad(page)
// Screenshot
await page.screenshot({ path: '.otto/screenshots/page.png' })
// ARIA snapshot
const snapshot = await client.getAISnapshot('main')
console.log(snapshot)
Interact
// Click by ref
const btn = await client.selectSnapshotRef('main', 'e3')
await btn.click()
// Fill input by ref
const input = await client.selectSnapshotRef('main', 'e5')
await input.fill('user@example.com')
// Re-capture after interaction
await waitForPageLoad(page)
const newSnapshot = await client.getAISnapshot('main')
Waiting
await waitForPageLoad(page)
await page.waitForSelector('.results')
await page.waitForURL('**/success')
No TypeScript in Browser Context
Code in page.evaluate() runs in browser context without TypeScript support. Use plain JavaScript only—type annotations break at runtime.
// ✓ Correct
await page.evaluate(() => {
const items = document.querySelectorAll('.item')
return items.length
})
// ✗ Wrong - TypeScript syntax fails
await page.evaluate(() => {
const items: NodeListOf<Element> = document.querySelectorAll('.item')
return items.length
})
Cleanup
await client.disconnect()
After completing the workflow, remove screenshots:
rm -rf .otto/screenshots
ARIA Snapshot Format
- banner:
- link "Home" [ref=e1]
- main:
- heading "Welcome" [ref=e2]
- form:
- textbox "Email" [ref=e3]
- button "Submit" [disabled] [ref=e4]
Use [ref=eN] values with selectSnapshotRef() to interact.
Error Recovery
Page state persists after failures. Debug using screenshots and state inspection to evaluate current conditions before next action.
// After an error, reconnect and inspect
const client = await connect({ headless: true })
const snapshot = await client.getAISnapshot('main')
await client.page('main').then(p => p.screenshot({ path: '.otto/screenshots/debug.png' }))
Scraping Data
For large datasets, intercept and replay network requests rather than scrolling the DOM. See references/scraping.md for the complete guide covering request capture, schema discovery, and paginated API replay.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/browser-automation-with-persistent-state-mm78nn3h/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/browser-automation-with-persistent-state-mm78nn3h' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/browser-automation-with-persistent-state-mm78nn3h/download' --output '.skill-downloads/browser-automation-with-persistent-state-mm78nn3h/SKILL.md.part' && mv '.skill-downloads/browser-automation-with-persistent-state-mm78nn3h/SKILL.md.part' '.skill-downloads/browser-automation-with-persistent-state-mm78nn3h/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Bash(node *), Bash(mkdir *)
Original excerpt: Setup
Start the browser server before running scripts:
node skills/otto/lib/browser/server.js &
Wait for "Ready" message, then connect:
import { connect, waitForPageLoad } from 'skills/otto/lib/browser/client.js'
const client = await connect({ headless: true })
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/browser-automation-with-persistent-state-mm78nn3h/SKILL.md' && test -s '.skill-downloads/browser-automation-with-persistent-state-mm78nn3h/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/browser' && cp -R '.skill-downloads/browser-automation-with-persistent-state-mm78nn3h' '.claude/skills/browser'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/browser-automation-with-persistent-state-mm78nn3h'openskills read 'browser-automation-with-persistent-state-mm78nn3h'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/browser-automation-with-persistent-state-mm78nn3h/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.