browser-testing

Automate IntelliFill browser tests by controlling a Chrome instance via Puppeteer.

1|Updated Aug 8, 2025
One-click install
npx skills add https://github.com/Intellifill/IntelliFill --skill browser-testing-intellifill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-testing
Source: https://github.com/Intellifill/IntelliFill/tree/main/.claude/skills/browser-testing
Command: npx skills add https://github.com/Intellifill/IntelliFill --skill browser-testing-intellifill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides on-demand browser automation to streamline IntelliFill testing, replacing manual, repetitive browser interactions and enabling token-efficient control of a Chrome instance for test scenarios.

Core Features & Use Cases

  • Lazy-loads browser automation on demand, avoiding upfront resource consumption.
  • Connects to a running Chrome instance via remote debugging to execute scripted interactions.
  • Supports navigating pages, form interactions, screenshots, and file uploads to verify UI flows and create docs.
  • Use Case: Quickly validate login, dashboard navigation, and document upload workflows during test iterations.

Quick Start

Start Chrome with remote debugging on port 9222 and use a dedicated user-data-dir for the IntelliFill test session: start chrome --remote-debugging-port=9222 --user-data-dir="N:/IntelliFill/quikadmin/chrome-debug-profile"

Frequently Asked Questions about browser-testing

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

FAQPage Schema
How do I automate Chrome browser testing with Puppeteer using remote debugging?

Browser testing with Puppeteer automates a running Chrome instance by connecting via remote debugging. You must start Chrome with the remote-debugging-port flag to enable scripted interactions for GUI form testing and visual debugging.

What is the best way to take screenshots during automated browser testing?

Taking screenshots during browser testing is handled through on-demand Puppeteer automation. By connecting to a running Chrome instance, the skill navigates pages and captures visual debugging screenshots to verify UI flows and create documentation.

Do I need a specific Chrome profile to run Puppeteer automated login and file upload tests?

Yes, automated login and file upload testing requires starting Chrome with a dedicated user-data-dir. This isolates the browser session, ensuring clean state management for IntelliFill test workflows executed through the Puppeteer interface.

Can I use this browser automation skill for validating dashboard navigation and form interactions?

Yes, browser automation supports navigating pages and form interactions to validate dashboard navigation. It controls a running Chrome instance via remote debugging to execute scripted interactions and verify UI workflows on demand.

Why does on-demand browser automation avoid upfront resource consumption?

On-demand browser automation avoids upfront resource consumption by lazy-loading the Puppeteer interface only when needed. This approach connects to an already running Chrome instance, preventing idle background processes until a testing action is triggered.

Are there limitations when controlling a running Chrome instance for visual debugging?

Limitations include requiring a locally available Chrome installation with remote debugging explicitly enabled. The skill depends on this specific environment setup and a Puppeteer-compatible interface to execute browser testing workflows successfully.