Results for “headless-chrome”
18 skillsMore results
browsh
A modern text-based browser. Renders web pages in the terminal using headless Firefox.
2 · bundle
gstack
Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
2 · bundle
browse
Fast headless browser for QA testing and site dogfooding. (gstack)
0
browse
Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this". (gstack)
0
jetson-headless-mode
Plan and apply safe, reversible headless-mode changes on Jetson devices to reclaim memory from the GUI and non-essential daemons.
2.2k · bundle
browser
Simple headless Puppeteer browser for rendering JavaScript-heavy pages and extracting clean text content. Use when user needs to read a web page that requires JS rendering. Command: openclaw browser read <url>. Requires: node, puppeteer.
228 · bundle
analyzing-browser-forensics-with-hindsight
Extract and analyze Chromium-based browser artifacts using Hindsight to reconstruct user web activity for forensic investigations.
24.6k · bundle
pokemon-player
Play Pokemon games autonomously via headless emulation. Starts a game server, reads structured game state from RAM, makes strategic decisions, and sends button inputs — all from the terminal.
0 · bundle
pokemon-player
Play Pokemon games autonomously via headless emulation. Starts a game server, reads structured game state from RAM, makes strategic decisions, and sends button inputs — all from the terminal.
3
full-page-screenshot
Capture full-page screenshots of any web page using Chrome DevTools Protocol, handling SPAs, lazy-loaded images, and very tall pages with zero external dependencies.
20.4k · bundle
open-gstack-browser
Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".
0 · bundle
implementing-container-image-minimal-base-with-distroless
Reduce container attack surface by building application images on Google distroless base images that contain only the application runtime with no shell, package manager, or unnecessary OS utilities.
24.6k · bundle
ghidra-reverse
Performs free, open-source reverse engineering with Ghidra using headless or GUI modes, including decompilation, cross-references, and optional MCP workflows when IDA is unavailable.
12.8k · bundle
shopify-expert
Builds and debugs Shopify themes, develops custom Shopify apps, and implements Storefront API integrations for headless storefronts.
10.4k · bundle
browser-use
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
228 · bundle
pokemon-player
Play Pokemon via headless emulator + RAM reads.
0
peekaboo
Trigger: macOS UI, screen recording, simulator UI, desktop app click, capture screen, system dialog, macOS clipboard, menu bar, drag drop. Scope: Automate macOS GUI applications, drive input events, list windows/spaces, and capture visual state via Peekaboo CLI. Boundary: Excludes pure browser-level automation (use chrome-devtools instead) or headless server tasks.
1