remote-chromeLaunch, stop, restart, or check the status of a remote Chrome browser service using Xvfb, x11vnc, and noVNC. Use this whenever the user wants to start a head...
Install via ClawdBot CLI:
clawdbot install kelvinschen/remote-chromeGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Accesses system directories or attempts privilege escalation
/proc/Calls external URL not in known-safe list
http://proxy.example.com:8080AI Analysis
The skill's primary function is to manage a local remote browser service, which inherently requires system-level access to /proc for process monitoring and can accept user-specified proxy configurations. There is no evidence of hidden instructions, credential harvesting, data exfiltration, or obfuscation. The external URL mentioned is a user-configurable proxy example, not a hardcoded call to an unauthorized server.
Audited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
Quality assurance teams can use this skill to run Chrome browsers on remote servers, enabling automated or manual testing of web applications across different environments. It provides visual access via VNC for debugging UI issues and integrates with agent-browser for automated script execution, streamlining the testing workflow.
Educational institutions can deploy this skill to offer students remote access to Chrome browsers for web development courses or online exams. It allows instructors to monitor student activities through VNC, while students benefit from a consistent, GUI-based environment without local installations.
Marketing agencies can utilize this skill to run Chrome browsers on cloud servers for tracking ad campaigns, analyzing competitor websites, or testing landing pages. The web-based VNC access enables real-time visual checks, and custom proxy settings support geo-targeted testing.
Support teams can leverage this skill to access Chrome browsers on customer machines or remote servers, helping diagnose web-related issues. It provides a visual interface via noVNC for guided troubleshooting, with status monitoring to track browser performance and tabs.
Data analysts and researchers can use this skill to run headless Chrome browsers for web scraping or monitoring dynamic content. It offers programmatic control through agent-browser integration for automation, while VNC access allows visual verification of data extraction processes.
Offer a subscription-based service where users can launch and manage remote Chrome browsers via a web dashboard. Revenue comes from tiered plans based on usage hours, screen resolutions, and support for custom ports or proxy configurations.
Provide a free version with basic features like standard ports and resolutions, and charge for advanced options such as high-resolution screens, multiple instances, or priority support. Monetize through premium upgrades and enterprise licenses.
Partner with automation tool providers to bundle this skill as a managed service for remote browser control. Revenue is generated through licensing fees per integration, consulting for custom setups, and ongoing maintenance contracts.
💬 Integration Tip
Integrate this skill with agent-browser for programmatic control, using the Chrome debugging port to automate tasks while monitoring visually via VNC for real-time debugging.
Scored Apr 19, 2026
Use when building UI with shadcn/ui components, Tailwind CSS layouts, form patterns with react-hook-form and zod, theming, dark mode, sidebar layouts, mobile navigation, or any shadcn component question.
Tailwind reference tool. Use when working with tailwind in frontend contexts.
A product creation skill based on the "Bee Website Builder" Open API. It is used to create a new product under a specified site language and product group, w...
A product update skill based on the "Bee Website Builder" Open API. It is used to update an existing product under a specified site language and supports upd...
Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".
Use when building Vue 3 applications with Composition API, Nuxt 3, or Quasar. Invoke for Pinia, TypeScript, PWA, Capacitor mobile apps, Vite configuration.