playwright-google-flow-ops

Automate Google Flow login and task generation with Playwright workers.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Yusufkotavom/AiToEarn --skill playwright-google-flow-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-google-flow-ops
Source: https://github.com/Yusufkotavom/AiToEarn/tree/main/skills/playwright-google-flow-ops
Command: npx skills add https://github.com/Yusufkotavom/AiToEarn --skill playwright-google-flow-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates login, troubleshooting, and task generation for Google Flow integration using Playwright workers and remote browser/noVNC.

Core Features & Use Cases

  • Automates login workflow verification across google-flow-playwright-worker and google-flow-remote-browser.
  • Generates tasks and monitors until terminal state, with debugging data for failures.
  • Provides debugging artifacts (snapshots, logs) and guidance to fix selectors/flows during investigations.

Quick Start

Stand up the Google Flow Playwright setup, verify worker health, and run a test task to validate login, generation, and end-to-end flow.

Frequently Asked Questions about playwright-google-flow-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Google Flow login and troubleshooting with Playwright?

Automating Google Flow login with Playwright involves using dedicated workers and a remote browser to verify workflows, generate tasks, and handle login challenges. It monitors tasks until terminal state and collects debug artifacts like snapshots and logs during investigations.

What is the best way to handle login challenges in a Playwright remote browser setup?

Handling login challenges in a Playwright remote browser setup requires avoiding hardcoded credentials and applying guardrails to rebuild affected services on failure. The automation collects debug snapshots and logs while guiding selector fixes during troubleshooting.

How do I monitor Playwright tasks until a terminal state and collect debugging data?

Monitoring Playwright tasks to terminal state involves generating tasks via endpoints like /v1/tasks/* and tracking progress. When failures occur, the system collects debugging data including snapshots and logs to guide fixes for broken selectors or flows.

Does the Google Flow Playwright worker support noVNC for remote browser automation?

Yes, the Google Flow Playwright worker supports noVNC for remote browser automation. This integration allows you to verify login workflows, manage status resume operations, and handle timeout handling across both worker and remote browser components.

Why does my Playwright login workflow fail and how do I resume its status?

Playwright login workflows fail due to selector issues or timeouts, requiring status resume operations via endpoints like /v1/profiles/*. To resolve failures, the system collects debug artifacts, applies guardrails against hardcoded credentials, and rebuilds affected services.