Automate browser QA workflows with a persistent Chromium daemon via Playwright.
npx skills add https://github.com/caraseli02/MoldovaDirect --skill gstack-caraseli02
Please help me install this Agent Skill. Skill: gstack Source: https://github.com/caraseli02/MoldovaDirect/tree/main/.claude/skills/gstack Command: npx skills add https://github.com/caraseli02/MoldovaDirect --skill gstack-caraseli02
Fast headless browser for QA testing & 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.
Launch a browse session and perform a simple test flow by navigating to a URL, taking a snapshot, and verifying content.
High-intent search queries and answers about installing and using this skill.
Headless browser QA testing is automated using a persistent Chromium daemon running Playwright via Bun, enabling navigation, interaction, content verification, and visual evidence collection across web apps with roughly 100ms per command.
Capture annotated screenshots during Playwright automation using a stateful Chromium daemon that exposes screenshot, diff, and annotate commands, enabling visual evidence collection for bug filing and deployment verification.
Headless browser automation supports deployment verification and internal tool dogfooding through repeatable navigation and interaction flows, targeting developers and QA engineers needing production dogfooding across web apps with stateful sessions.
Diff before and after states during headless browser testing by executing sequential snapshot and diff commands within a persistent Chromium session, verifying page state changes after interactions like clicks, form fills, and hovers.
Headless QA testing works without restarting the browser by maintaining a persistent Chromium daemon that preserves state across commands, minimizing warm-up time and maximizing reliability for sequential interactions.
A persistent Chromium daemon is used for browser automation to maintain state across commands and minimize warm-up time, achieving roughly 100ms per command unlike launching new browser instances for each test.
a29paulAutomate website testing and deployment verification with persistent headless browser control.
clawpod-appAggregate CI/CD deployment status and post-deploy health metrics into deterministic reports.
sehoon787Automate Playwright end-to-end test creation with Page Object Model patterns.
Chang-Shih-YungRun a persistent headless Chromium daemon with Playwright under Bun via HTTP.
