agent-browser-verify Skill
Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass/fail before continuing. Published by openai in plugins.
Decision snapshot
Is this a fit?
Browser automation, Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
18 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is agent-browser-verify Skill?
Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass/fail before continuing. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Design and media
- Browser automation use cases
- Design and media use cases
Declared skill metadata
- Source file: plugins/vercel/skills/agent-browser-verify/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use agent-browser-verify Skill
- Use it for browser automation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/vercel/skills/agent-browser-verify/SKILL.md
What it does
Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass/fail before continuing.
Skill instructions
Dev Server Verification with agent-browser You MUST verify the dev server with agent-browser after starting it. Do not assume the page works just because the dev server process started. Many issues (blank pages, hydration errors, missing env vars, broken imports) are only visible in the browser. Run this verification before continuing with any other work: Quick Verification Flow bash 1. Open the dev server agent-browser open http://localhost:3000 agent-browser wait --load networkidle 2. Screenshot for visual check agent-browser screenshot --annotate 3. Check for errors agent-browser eval 'JSON.stringify(window.consoleErrors || [])' 4. Snapshot interactive elements agent-browser snapshot -i Verification Checklist Run each check and report results: 1. Page loads — agent-browser open succeeds without timeout 2. No blank page — snapshot shows meaningful content (not empty body) 3. No error overlay — no Next.js/Vite error overlay detected 4. Console errors — evaluate document.querySelectorA
Verified compatibility and discovery
Frequently asked questions
What is agent-browser-verify?
agent-browser-verify is a open-source AI agent skill with Copy skill directory. Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI.
Who is agent-browser-verify best for?
agent-browser-verify is best for reusing agent instructions, scripts, and references, browser automation workflows, design and media workflows.
How do I install agent-browser-verify?
Install or run agent-browser-verify using Copy skill directory. Check agent-browser-verify for the latest setup command.
Is agent-browser-verify actively maintained?
agent-browser-verify may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.