login-flow
Skill8 starsChanged 7 months agoMITView on GitHub
Signs into a site using credentials provided via `vars` (typically sourced from environment variables) or via a pre-saved Playwright persistent context. Never harvests or stores credentials. See docs/ethics.md.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- jhy0285/monofieldtheir own version, first seen Oct 13, 2026
- jpoindexter/theft-kittheir own version, first seen May 20, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- jhy0285/monofield★ 6same name
- jpoindexter/theft-kit★ 1same name
- davidanthonyn/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- date-picker-widgetSkill
- detect-captchaSkill
- dismiss-cookie-bannerSkill
- dismiss-newsletter-popupSkill
- exit-tracking-popupSkill
- extract-table-paginationSkill
- fill-multi-step-formSkill
- handle-infinite-scrollSkill
- handle-modal-dialogSkill
- pagination-next-pageSkill
- searchable-dropdownSkill
- search-and-filterSkill
- upload-download-fileSkill
- verify-page-loadedSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 58
MFA-protected logins: If MFA is enabled and there's no pre-saved session, the recipe will hit the MFA challenge and stop.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Login Flow
When to invoke
The user task requires authentication. The agent provides credentials in:
vars.username(orvars.email)vars.password
Per and docs/ethics.md: we use the
agent-provided creds only — typically sourced by the agent from env
vars ($SITE_X_USER, $SITE_X_PASS) the user has set, or from a
password manager the user controls. We never harvest, prompt for, or
store credentials. The sensitive: true metadata flag tells the
trace recorder to redact form-fill events in the exported zip.
Recipe
- wait_for_dom_ready timeout=5s
- wait_for_selector selector="input[type='password']" state=visible timeout=5s
- fill selector="input[type='email'], input[name='username'], input[name='email'], input[id='username'], input[id='email']" value="$vars.username"
- fill selector="input[type='password']" value="$vars.password"
- click selector="button[type='submit'], button:has-text('Sign in'), button:has-text('Log in'), input[type='submit']"
- wait extra=1000ms
Success criteria
- assert no_visible_element selector="input[type='password']"
- assert url_changed_since=step1 OR cookie_set_named="session"
When NOT to use
- OAuth / SSO flows that redirect through identity providers
(Google, Microsoft, Okta). Use
handle-oauth-redirect(v0.2.0). - Magic-link / passwordless flows. Out of v1 scope; agent must poll its inbox separately.
- MFA-protected logins. If MFA is enabled and there's no pre-saved session, the recipe will hit the MFA challenge and stop. The agent surfaces the MFA prompt and asks the user how to proceed.
Known failures
- Sites that hide the password field until the email is submitted first (Google-style): the recipe fills email, submits, then needs to re-find the password field. v0.1 fails on these; the agent can retry with a "submit, wait, re-invoke" loop.
- Captcha after a few failed attempts:
detect-captchashould be chained after this skill. - "Are you sure?" dialogs post-login:
handle-modal-dialogchains.
Trace handling
Per sensitive: true:
- form-fill events for password fields are recorded as
{value: "[REDACTED]"}in the trace - screenshots taken during this skill's steps are blackened over the password field's bounding box (v0.1 omits screenshots from this skill entirely)
Related skills
dismiss-cookie-banner— sites with consent walls hit this firstdetect-captcha— failed-login rate-limiting often triggers captcha
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.