stealth-manager

Coordinate multi-account browser automation with proxy rotation and human-like delays.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nguynbon03/API-XuongMedia-Backup --skill stealth-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stealth-manager
Source: https://github.com/nguynbon03/API-XuongMedia-Backup/tree/main/.claude/skills/stealth-manager
Command: npx skills add https://github.com/nguynbon03/API-XuongMedia-Backup --skill stealth-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automation tasks across multiple browser profiles while avoiding bot detection during web interactions.

Core Features & Use Cases

  • Independent per-account browser profiles to isolate sessions
  • Anti-detect techniques via Playwright stealth and undetected-chromedriver
  • Proxy rotation with per-account proxies to avoid blocks
  • Randomized delays and user-agent rotation to mimic human behavior
  • Suitable for multi-account automation for activities like social media, data collection, and testing

Quick Start

Launch the stealth manager, create profiles for your accounts, and start rotating proxies to begin multi-account automation.

Frequently Asked Questions about stealth-manager

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

FAQPage Schema
How do I automate multi-account browser sessions without triggering bot detection?

To avoid bot detection during multi-account automation, you need to isolate sessions using per-account browser profiles and apply anti-detect techniques like randomized delays and user-agent rotation.

What is the best way to prevent bot detection when running web automation with Playwright?

The best way to prevent bot detection in Playwright is to use stealth techniques, which involve rotating proxies and randomizing user-agent strings and delays to mimic human behavior.

Does multi-account automation require separate proxies for each browser profile?

Yes, multi-account automation requires per-account proxy rotation to avoid blocks. Assigning a dedicated proxy to each independent browser profile ensures that sessions remain isolated and undetected.

Can I use Selenium for stealthy multi-account automation instead of Playwright?

Yes, stealthy multi-account automation supports integration with Selenium through undetected-chromedriver, providing the same anti-detect capabilities and per-account profile isolation as Playwright.

What is needed to set up scalable multi-account browser automation for data collection?

Scalable multi-account browser automation requires a proxy infrastructure, per-account storage states, and integration with Playwright or Selenium to coordinate sessions and prevent detection safely.