login-flow

Automate website sign-ins using environment variables or a Playwright persistent context.

8|Updated May 13, 2026
One-click install
npx skills add https://github.com/bettyguo/browser-skills --skill login-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: login-flow
Source: https://github.com/bettyguo/browser-skills/tree/main/skills/login-flow
Command: npx skills add https://github.com/bettyguo/browser-skills --skill login-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates sign-in to websites by using credentials provided from environment variables or a pre-saved Playwright persistent context, without harvesting or storing credentials.

Core Features & Use Cases

  • Automated login where credentials are supplied by the agent or loaded from a saved browser context.
  • Secure handling: credentials are never harvested or stored by the agent; password fields are redacted in traces.
  • Use cases include automated testing, onboarding flows, and any repetitive login tasks across sites.

Quick Start

Provide credentials via vars (username and password) or use a pre-saved context, then run the login-flow to sign in and establish a session.

Frequently Asked Questions about login-flow

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

FAQPage Schema
How do I automate website login with Playwright using environment variables?

Automate website login with Playwright by supplying credentials via environment variables; the flow locates fields, fills inputs, submits the form, and verifies the session while redacting sensitive data in traces.

Can I use a pre-saved browser context for automated sign-in flows?

Yes, you can use a pre-saved Playwright persistent context for automated sign-in flows. The agent loads the saved context to establish a session directly, bypassing manual credential entry for repetitive login tasks.

How are credentials protected during automated browser testing and login?

Credentials are protected during automated browser testing because the agent never harvests or stores them. Password fields are automatically redacted in execution traces, keeping sensitive data hidden throughout the login automation process.

Does this automated login approach support SSO and non-standard credential forms?

This automated login approach supports standard credential fields and non-SSO forms. It is designed for routine login flows across multiple sites but does not handle Single Sign-On (SSO) authentication flows.

What is the best way to handle repetitive login tasks across multiple sites?

The best way to handle repetitive login tasks across multiple sites is to automate the process by supplying credentials from environment variables or a saved persistent context, letting the agent wait for the page, fill fields, and verify login success.