Loading...
Loading...
Found 3 Skills
Desktop & Tauri app testing for AI agents — Tauri v2 + WebKitGTK in Docker (AppImage extraction, Gemini Computer Use, virtual display, DOCX export verification) plus Electron app automation (VS Code, Slack, Discord, Figma) via `agent-browser skills get electron`. Use when testing a Tauri desktop app (Cicero), Electron app, or any non-browser desktop UI. For web browser testing, see `browser-test-agent`.
Background knowledge for droid-control workflows -- not invoked directly. Agent-browser driver mechanics for web page and Electron desktop app automation.
Your EYES into the user's live Chrome browser and Electron apps. This skill lets you SEE and INTERACT with the user's actual browser or Electron app — their open tabs, logged-in sessions, and live page state. You MUST use this whenever the user's request involves browser content or Electron app inspection in ANY way. TRIGGER THIS SKILL when the user: - References pages they have open: 'I have X open', 'my tabs', 'open tabs' - Asks to look at, compare, or analyze anything in their browser: 'compare these pages', 'which looks better', 'check this page' - Mentions UI/visual analysis of live pages: 'dashboard', 'UI', 'layout', 'design quality' - Asks for screenshots or page inspection: screenshot, inspect, debug, check the page - Refers to 'the page', 'the browser', 'my tab' in any context - Mentions console errors, page state, or anything requiring browser access - Mentions Electron apps or CDP connections: 'Electron', 'electron app', 'CDP', 'CDP_PORT', 'DevTools Protocol', 'desktop app', 'remote-debugging-port' CRITICAL: NEVER say you cannot see the user's browser or ask users to paste screenshots. You CAN see their browser through this skill. Use `list` to discover open tabs, then `perceive` or `shot` to see page content. Do NOT use Playwright — it launches an isolated browser without the user's login state, cookies, or open tabs.