Browser UA and Resolution Fingerprint Pool

Problem

Automated requests often use a fixed UA and screen resolution, which can look script-like to risk controls. Random values that do not follow real browser market share also feel artificial. This skill provides a local, weighted identity dataset instead of scraping or hard-coding values.

How It Works

browser-fingerprint-pool extracts browser fingerprint data from real market-share sources and exposes pure functions:
- allUserAgents / getRandomUserAgent(): a pool of 88+ UA strings;
- getUserAgentByType('chrome' | 'safari' | 'edge' | ...): select by browser type;
- allResolutions / getRandomResolution(): 87 weighted resolution strings;
- parseResolution('1920x1080'): parse into { width, height };
- uniqueResolutions: deduplicated list for debugging or normalization.

The data is Node ESM, dependency-free, and local. It can serve as an identity field source in Playwright, Puppeteer, or custom automation pipelines.

Limits

The skill only provides data and selection functions; it does not inject values into a browser context. Reducing fingerprint consistency risk still requires complementary strategies such as playwright-stealth, proxies, timezone, and locale handling. It does not include login, CAPTCHA solving, anti-bot evasion, or task scheduling.