Login web

☁ Personal AI assistant for automation browser behaviors on CDP remote connection. Lightweight, safe, and isolate sandbox workspace

Install

npx -y skills add thuongtruong109/soniclaw --skill login-web

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

Copied from the file, not written here

Handles logging into a website using browser automation

1.7 KB, 375 tokens by cl100k_base, as published. Nobody here has run it

When the user wants to log into a website, use the browser-automator workflow against the remote CDP browser.

Navigate to the login page URL provided by the user
If the sign-in modal is not open, click Sign in.
Fill the username/email field and type username/email with user provides
Fill the password field and type the password with user provides
Click the login/sign in/submit button
If website asks for a 2FA verification, open and switch to new tab -> fill the 2FA keycode with user provides into the verification input -> submit -> copy 6-digit code
Paste the 6-digit code into the 2FA input field on the original tab

Use these browser commands as the default pattern:

openclaw browser navigate <LOGIN_PAGE_URL>
openclaw browser wait --load networkidle
openclaw browser snapshot --interactive --compact --depth 5

Then act on the latest refs for:

Do not assume refs persist after clicking Sign in or submitting forms.
If the login form fails or changes, take a fresh interactive snapshot and continue from current page state.
When this skill is used inside a larger workflow, keep the same browser session for all later steps in that job unless the workflow explicitly switches account/session.
Do not treat browser profile name alone as proof of which account is in use.
After login is verified or found already active, return to the current pipeline task instead of treating login as the endpoint.
Before reporting success, verify that the session is now on the authenticated UI rather than an auth screen.

Read from the repository

Just SKILL.md. No reference files, no scripts.