Skriptey Userscripts

A collection of browser userscripts. Each script is hand-written plain JavaScript — the file in this repo is exactly what gets installed, nothing is bundled or minified, so you can read every line before you run it.

➡️ Browse & install: https://skriptey.github.io/Userscripts/

Install a userscript

1. Install a userscript manager: Tampermonkey (Chrome/Edge/Safari/Firefox) or Violentmonkey (Chrome/Firefox).
2. Open the install index and click Install on the script you want. (Alternatively, advanced users can open a scripts/<slug>/<slug>.user.js file directly on GitHub and the manager will offer to install it.)

Installed scripts auto-update: each one's @updateURL points back at its published copy, so your manager pulls new versions automatically.

Repository layout

Userscripts/
├── scripts/                     # one folder per userscript
│   └── <slug>/
│       ├── <slug>.user.js       # the script (metadata block + code)
│       └── README.md            # per-script docs
├── tools/                       # dependency-free Node build helpers
│   ├── build-index.mjs          # generates the Pages install index
│   ├── validate-metadata.mjs    # CI gate: checks required metadata
│   └── lib/meta.mjs             # shared metadata parser/validator
├── docs/                        # long-form docs; docs/wiki/ = GitHub Wiki source
├── site/                        # generated Pages output (built in CI, git-ignored)
├── .github/                     # workflows, issue/PR templates, Dependabot
├── .claude/                     # Claude context + memory (committed, portable)
├── LICENSE                      # GPL-3.0
├── SECURITY.md                  # how to report vulnerabilities
└── CONTRIBUTING.md              # how to add a script

Why a folder per script? It scales: each script keeps its own README, icon, and changelog next to the code, and the install index is generated by scanning scripts/.

How releases work

There is no build step for the scripts themselves — they ship verbatim. On every push to main, the pages.yml workflow:

1. validates every script's metadata,
2. runs tools/build-index.mjs, which parses each *.user.js metadata block, copies each script folder into site/<slug>/, and writes site/index.html, then
3. deploys site/ to GitHub Pages.

Install URLs are therefore stable: https://skriptey.github.io/Userscripts/<slug>/<slug>.user.js.

Contributing

See CONTRIBUTING.md. In short: copy scripts/example-hello-world/, edit the metadata + code, run npm run validate, and open a pull request.

Security

Please report vulnerabilities privately — see SECURITY.md. Do not open a public issue for a security problem.

License

GPL-3.0-or-later. Each script also declares @license GPL-3.0-or-later in its metadata block.