Control a persistent headless browser to navigate pages, interact with UI, and capture evidence.
npx skills add https://github.com/westn/gstack-pi-port --skill gstack-westn
Please help me install this Agent Skill. Skill: gstack Source: https://github.com/westn/gstack-pi-port/tree/main/port/gstack Command: npx skills add https://github.com/westn/gstack-pi-port --skill gstack-westn
Navigate pages, interact with UI, capture evidence, and diff results to accelerate QA and bug reporting without manual browser scripting. This skill streamlines QA workflows by giving you a persistent, scriptable browser for testing deployments and dogfooding user flows.
Start a QA session on a site by saying “/skill:browse” and begin testing with “/skill:qa”.
High-intent search queries and answers about installing and using this skill.
Automate headless browser QA workflows by controlling a persistent browser to navigate pages, interact with UI, and capture evidence. This skill handles clicking, filling forms, and reading content to test deployments and dogfood user flows without manual browser scripting.
Yes, you can capture diffs and annotated screenshots during automated browser testing. The skill collects visual evidence by capturing differences and annotating screenshots, accelerating QA and bug reporting across pages, forms, and dialogs.
Testing responsive layouts across devices in a headless browser is best handled by automating navigation and interaction within a persistent session. The skill captures diffs and annotated screenshots to verify responsive designs across various device layouts.
Yes, the headless browser automation stores session state locally for repeatable QA pipelines. This allows you to maintain persistent browser contexts across multiple testing runs, ensuring consistent pre-release verification and bug reproduction.
Start a QA session by initiating a browsing command to open the target site, then use the QA command to begin navigating pages and interacting with the UI. The skill automates bug reproduction and collects clear evidence.
The limitations of using a headless browser for pre-release verification include the inability to visually perceive rendered animations in real-time and potential discrepancies with browser-specific rendering engines not covered by the local session state.
smarmen86Automate headless Chromium browser interactions for QA and site testing.
lyfe2025Run verification commands and inspect outputs before declaring completion.
andrew-t-jamesImport browser cookies into a headless session for authenticated testing.
ScivorAutomate browser QA tasks with a persistent headless browser.
