browser-control

Automate browser interactions for authenticated web applications via Chrome DevTools Protocol.

2|3|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/psd401/psd-claude-plugins --skill browser-control-psd401
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-control
Source: https://github.com/psd401/psd-claude-plugins/tree/main/plugins/psd-productivity/skills/browser-control
Command: npx skills add https://github.com/psd401/psd-claude-plugins --skill browser-control-psd401

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates interactions with authenticated web applications, streamlining tasks like form filling, report downloading, and general browser navigation that require user logins.

Core Features & Use Cases

  • Browser Automation: Control a running browser instance using Chrome DevTools Protocol.
  • Form Interaction: Fill forms, type text, and click elements within web pages.
  • Use Case: Automate the process of logging into PowerSchool, navigating to a specific report section, and downloading a generated student roster.

Quick Start

Launch the browser automation script to ensure the browser is ready for interaction.

Frequently Asked Questions about browser-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate form filling and web scraping for authenticated web applications?

Browser automation for authenticated sites is handled by connecting to a running Brave Browser Nightly instance with a persistent debug profile. This setup uses the Chrome DevTools Protocol to directly navigate, fill forms, and extract data from login-protected pages.

Can I automate downloading reports from PowerSchool using Chrome DevTools?

Yes, you can automate downloading reports from PowerSchool by using Chrome DevTools Protocol to navigate the interface. The Skill controls a running browser instance to log in, locate specific report sections, and download generated student rosters automatically.

Do I need a specific browser setup to control web pages via the DevTools Protocol?

Yes, browser control requires a running Brave Browser Nightly instance configured with a persistent debug profile. This specific environment is necessary for the MCP tools to establish a connection and execute direct browser interactions securely.

What is the best way to extract data from web pages that require user login?

The best way to extract data from login-protected web pages is using a persistent browser debug profile. By maintaining an authenticated session in Brave Browser Nightly, the automation script can bypass login barriers and directly scrape the needed data.

Why does browser automation fail to interact with elements on authenticated pages?

Browser automation fails when the browser lacks a properly configured persistent debug profile. Without an active authenticated session in the running Brave Browser Nightly instance, the Chrome DevTools Protocol cannot access or manipulate the protected page elements.