login-flows

Common login automation patterns for web apps using Playwright

Quality

56%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./content/playwright-community/skills/login-flows/SKILL.md

Quality

Content

79%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, practical skill that provides clear, executable patterns for common login automation scenarios with Playwright. Its main strengths are conciseness and actionability—every section delivers copy-paste-ready code. The main weakness is the lack of error handling/validation guidance, particularly for the storageState workflow where login failures during global setup could silently break all tests.

Suggestions

Add a validation step to the storageState workflow, e.g., checking that auth.json was created and contains valid cookies before proceeding

Include brief error handling guidance for login failures (e.g., what to check when waitForURL times out)

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. Each section presents a distinct pattern with minimal prose and executable code. The brief introductory sentences before code blocks add context without being verbose, and there's no explanation of concepts Claude already knows (like what Playwright is or how login works).	3 / 3
Actionability	Every pattern includes fully executable TypeScript code with specific selectors, real API calls, and copy-paste-ready examples. The storageState section even shows both the setup file and the config file needed, making it immediately usable.	3 / 3
Workflow Clarity	The patterns are presented as independent recipes rather than a sequenced workflow, which is appropriate for a patterns skill. However, the storageState section involves a multi-step setup (global-setup.ts + config) without explicit validation—e.g., no guidance on verifying auth.json was created correctly or handling login failures during setup.	2 / 3
Progressive Disclosure	The content is well-organized with clear section headers, but everything is inline in a single file. The OAuth and MFA sections could benefit from being referenced as separate files, and the Tips section mixes concerns. For a skill of this length (~80 lines of content), the structure is adequate but not optimal.	2 / 3
	Total	10 / 12 Passed

Description

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is too terse and lacks both specific concrete actions and an explicit 'Use when...' clause. While it identifies the domain (login automation with Playwright), it reads more like a topic label than a skill description that would help Claude reliably select it from a large pool of skills.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'Use when the user needs to automate login flows, handle authentication, sign-in pages, or session management in Playwright tests.'

List specific concrete actions such as 'Fills login forms, handles OAuth redirects, manages cookies/sessions, bypasses MFA in test environments.'

Include natural keyword variations users might say: 'sign in', 'authentication', 'credentials', 'auth flow', 'login page'.

Dimension	Reasoning	Score
Specificity	Names the domain (login automation) and the tool (Playwright), but does not list specific concrete actions like 'fill credentials', 'handle MFA', 'manage sessions', etc.	2 / 3
Completeness	Provides a partial 'what' (login automation patterns) but completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'login', 'automation', 'Playwright', and 'web apps', but misses common variations users might say such as 'sign in', 'authentication', 'credentials', 'session', or 'e2e testing'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'login automation' and 'Playwright' narrows the scope somewhat, but 'common patterns for web apps' is still broad enough to overlap with general Playwright testing or web automation skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: andrewyng/context-hub
Commit: 67dcbeb

Reviewed: 20 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.