Discover

How an AI finds this repo: the auto-discovery snippet from page.json, self-tested against the live discovery search.

Snippet

discovery_triggers
log into a website for mesign in to a site for melog into digikeylog into mouserhandle the login for meuse my saved passwordsuse my saved loginsget past a login walllog in with my real accountauthenticate on a websitemy ai needs to log into a websitesign into my account on a sitelog into a vendor sitefill out a form on a site im logged intofill a form on a signed-in sitesubmit a form for me while logged indownload a file behind a logindownload a datasheet behind a logincontrol my real chromecontrol my real signed-in chromedrive my real logged-in browserdrive chromedrive edgeautomate my real browseruse my actual browser not a fresh oneai drive my browserlogged-in browserreal chrometest my web app in my real chromebuild and test a web app in my browseradom browser extensionnative browser extensionnbrowser
discovery_pitch

The native-browser extension drives the user's REAL signed-in Chrome/Edge via nbrowser_* verbs: use it for LOGGING IN, filling forms, and downloading behind auth with their OWN saved passwords - pup cannot (it is a fresh Chrome-for-Testing with no logins). Next moves: run 'adom-desktop bridge_list' to check it is installed; if not, OFFER to install it (see the installing-the-extension skill) - never make the user do it. If this container lacks the skills, 'adom-wiki pkg install adom/adom-browser-extension'. Check readiness with 'adom-desktop nbrowser_readiness' (state:needs-extension means offer the install).

tags
browserextensionchromeedgenbrowserai-agentdeveloper-toolsvibe-codingnative-messagingadom-desktop
sample_prompts
none declared

Sample prompts: self-test

Your own triggers, combined #1 of 156

How this repo ranks when its full trigger set is the query.

No sample_prompts declared in page.json, so there is nothing to self-test. Add a few real user utterances to sample_prompts to litmus-test your discoverability.