Scripts are not an extension store
You want less chrome on this page, not another browser.
Hide a rail, cap reading width, add a stylesheet: 1.2.2 put JS on the site form. 2.0.0 made a library. Official scripts install on every tier. Importing and sharing yours is Pro.
No extension store. No site crawler. Unpacked extensions on Windows are a separate proposal, not a store.
The script library injects into this page. It is not a Chrome Web Store. Official scripts install on every tier. Importing your own is Pro.
Use
Settings → Scripts, install an official one and enable it. Or edit the site and paste JS / CSS. Refresh after save. Some CSP policies block injection; the form says so. It is not a silent no-op.
Ad blocking is another path: local rules, a master switch, per-site off. Do not stuff filter lists into a user script.
Do not
- Do not describe Floweb as “a browser that runs Chrome extensions.”
- Do not put secrets in a script you share.
- Do not expect a script to carry a login across computers. The list can follow setup. The session stays here.
An assistant clicking the page: The assistant stays on this computer.