Claude-skill-registry browser-testing
Browser automation for testing IntelliFill. Replaces puppeteer MCP to save ~4.8k tokens.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/browser-testing-intellifill-intellifill" ~/.claude/skills/majiayu000-claude-skill-registry-browser-testing && rm -rf "$T"
manifest:
skills/data/browser-testing-intellifill-intellifill/SKILL.mdsource content
Browser Testing
This skill covers browser automation for IntelliFill testing. It lazy-loads on demand instead of consuming context upfront like MCP servers.
When I Need This
- Testing form filling in Chrome
- Capturing screenshots for docs
- Debugging UI issues visually
- Automating upload/download flows
Quick Setup
Start Chrome with remote debugging first:
start chrome --remote-debugging-port=9222 --user-data-dir="N:/IntelliFill/quikadmin/chrome-debug-profile"
Core Patterns
Connect to Running Chrome
const browser = await puppeteer.connect({ browserURL: 'http://localhost:9222' }); const page = await browser.newPage();
Navigate and Interact
await page.goto('http://localhost:8080/login'); await page.type('[name="email"]', 'test@example.com'); await page.type('[name="password"]', 'password123'); await page.click('[type="submit"]'); await page.waitForNavigation();
Screenshot
await page.screenshot({ path: 'output.png', fullPage: true });
File Upload (IntelliFill document flow)
const [chooser] = await Promise.all([ page.waitForFileChooser(), page.click('#upload-button') ]); await chooser.accept(['./test-files/sample.pdf']); await page.waitForSelector('.upload-complete');
IntelliFill URLs
| Page | URL |
|---|---|
| Login | http://localhost:8080/login |
| Dashboard | http://localhost:8080/dashboard |
| Documents | http://localhost:8080/documents |
| Upload | http://localhost:8080/documents/upload |
Prefer Cypress/Playwright
For proper E2E tests, use the e2e-testing skill instead - it has full test infrastructure. This skill is for quick manual browser automation when you need direct Puppeteer control.