login-flows
Common login automation patterns for web apps using Playwright
48
51%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./content/playwright-community/skills/login-flows/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too terse and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and natural keyword variations. While 'Playwright' and 'login' provide some specificity, the description reads more like a topic label than a functional skill description.
Suggestions
Add specific concrete actions such as 'Fill login forms, handle OAuth/SSO flows, manage session tokens, handle multi-factor authentication prompts'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to automate sign-in, login, or authentication flows in Playwright browser tests.'
Include natural trigger term variations like 'sign in', 'authentication', 'credentials', 'session management', and 'password entry'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'common login automation patterns' which is vague. It doesn't list any concrete actions like 'fill login forms', 'handle OAuth flows', 'manage session cookies', or 'bypass CAPTCHAs'. It names a domain but no specific capabilities. | 1 / 3 |
Completeness | The 'what' is only vaguely described ('common login automation patterns') and there is no 'when' clause at all. There's no explicit trigger guidance like 'Use when...' which should cap completeness at 2, and the weak 'what' brings it down to 1. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'login', 'automation', 'Playwright', and 'web apps' that users might naturally use. However, it's missing common variations like 'sign in', 'authentication', 'credentials', 'session', or 'password'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Playwright' and 'login automation' together provides some distinctiveness, but 'common patterns for web apps' is broad enough to overlap with general Playwright testing skills or web automation skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
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 login automation patterns for Playwright. Its main strengths are conciseness and actionability—every section delivers copy-paste-ready code without unnecessary explanation. The main weakness is the lack of error handling/validation guidance, particularly for the storageState workflow where login failures in global setup could silently break all tests.
Suggestions
Add a brief validation step to the storageState workflow (e.g., check that auth.json exists and contains expected cookies, or handle login failure in global setup gracefully)
Consider adding a brief error recovery note for common failure modes like expired sessions, changed selectors, or OAuth provider timeouts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Each section presents a distinct pattern with minimal preamble—just a brief label and executable code. No unnecessary explanations of what Playwright is or how login works conceptually. | 3 / 3 |
Actionability | Every pattern includes fully executable TypeScript code with specific selectors, real Playwright API calls, and complete function signatures. The storageState section even shows both the setup file and the config integration, making it copy-paste ready. | 3 / 3 |
Workflow Clarity | The patterns are presented as standalone recipes rather than a sequenced workflow, which is appropriate for a pattern library. 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 in global setup. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and progresses from simple to complex patterns. However, for a skill of this length (~80 lines of meaningful content), some patterns like OAuth/MFA could be split into referenced files, and there are no references to external resources like Playwright's auth documentation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
04c149c
- Reviewed
Table of Contents
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.