login-flows
Common login automation patterns for web apps using Playwright
67
60%
Does it follow best practices?
Impact
Pending
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
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 identifies a specific niche (login automation with Playwright) but is too terse and lacks actionable detail. It fails to list concrete capabilities and entirely omits a 'Use when...' clause, making it difficult for Claude to reliably select this skill from a large pool.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user needs to automate login flows, handle authentication in browser tests, or script sign-in pages with Playwright.'
List specific concrete actions such as 'Fill login forms, handle OAuth redirects, manage session cookies, deal with MFA prompts, and retry failed authentication attempts.'
Include natural keyword variations users might say: 'sign in', 'authentication', 'credentials', 'browser automation', 'e2e testing login'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (login automation) and the tool (Playwright), but does not list specific concrete actions like 'fill login forms, handle MFA, manage session cookies, bypass CAPTCHAs'. | 2 / 3 |
Completeness | Describes what at a high level (login automation patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores 1. | 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 'browser testing'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'login automation' and 'Playwright' 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 | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides concrete, executable patterns for common login automation scenarios in Playwright. Its strengths are excellent actionability with copy-paste ready code and efficient use of tokens. The main weakness is the lack of error handling guidance and validation steps — for instance, what to do when login fails or how to verify that storageState was persisted correctly.
Suggestions
Add brief error handling/validation guidance, e.g., checking for error messages after login attempts or verifying storageState file exists before tests run
Consider adding a short note on how to choose between patterns (e.g., 'Use storageState by default; use direct login only when testing the login flow itself')
| 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, proper imports, and realistic flow sequences. The storageState section even includes both the setup file and the config file needed, making it copy-paste ready. | 3 / 3 |
Workflow Clarity | Each individual pattern is clear and well-sequenced, but there's no guidance on when to choose which pattern, no error handling or validation steps (e.g., what to do if login fails, how to verify auth state was saved correctly), and no feedback loops for debugging failed logins. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope, the content is well-organized into clearly labeled sections that progress from simple (basic login) to complex (MFA). No external references are needed, and the structure allows easy navigation to the relevant pattern. | 3 / 3 |
Total | 11 / 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
eeb895b
- 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.