Finding scripts
The Scripts page is your team’s catalog. Before you write a new script, look there, because someone may have built it already.
Search and filter
Section titled “Search and filter”- Search as you type. Words match the start of words in the name,
slug, description and tags, so
unl accfinds “Unlock an account”. - Tags: click a tag to see every script with it.
- Mine and Published only narrow the list.
The filters are in the page’s address, so you can share a filtered list. You only ever see scripts you may use. You can share a script with one team. People outside that team can’t see it, even in search.
The API, and agents over MCP, can search the same way:
curl "https://api.reminix.com/v1/scripts?q=unlock&tag=support&published=true" \ -H "Authorization: Bearer $REMINIX_TOKEN" -H "X-Workspace: acme"With q, the best matches come first, on a single page. Without q,
the list is newest first, and nextCursor gives the next page. To
filter by owner, pass a user id as owner.
Tags and README
Section titled “Tags and README”Set tags in the script’s Settings, or in reminix.json as
"tags": ["support"]. Tags in reminix.json replace the script’s tags
when you upload a version. A script can have up to 10 tags, made of
lowercase letters, digits and dashes.
Reminix keeps the README.md from the folder you publish with that version. The script’s page shows the README of the published version. In it, say what the script does, when to use it and what its inputs mean. The README is Markdown, and the page doesn’t show raw HTML.
Who uses it
Section titled “Who uses it”A script’s page shows who uses it. Over the last 30 days, it shows:
- its runs, the share that succeeded, and when it last ran
- where runs came from: the app, the API, the CLI, agents, schedules and triggers
- the people who ran it most
The page also lists the script’s schedules and triggers, and the
other scripts whose triggers start on its run.succeeded,
run.failed or run.cancelled events.
Before changing or retiring a script, check who would notice.