Finding scripts

The Scripts page is your team’s catalog. Before writing a new script, look there: someone may have built it already.

Search and filter

• Search as you type. Words match the start of words in the name, slug, description and tags, so rev mon finds “Monthly revenue report”.
• Tags: click a tag to see everything 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: a team’s script stays hidden from people outside the team, in search too.

From the API, and so from agents over MCP:

curl "https://api.reminix.com/v1/scripts?q=refund&tag=finance&published=true" \
  -H "Authorization: Bearer $REMINIX_TOKEN" -H "X-Workspace: acme"

With q, the best matches come first (one page). Without it, the list is newest first and pages with nextCursor. owner takes a user id.

Tags and README

Set tags in reminix.json ("tags": ["finance"]), which replace the script’s tags when you publish a version, or in the script’s Settings. Up to 10, using lowercase letters, digits and dashes.

Reminix keeps the README.md in the folder you publish from with that version, and shows it on the script’s page while the version is published. Say what it does, when to use it, and what its inputs mean. It’s Markdown; raw HTML isn’t shown.

Who uses it

Every script shows, for the last 30 days:

• its runs, the share that succeeded, and when it last ran;
• where runs came from: the app, the API, the command line, agents, schedules and triggers;
• the people who ran it most;
• its schedules and triggers, and the other scripts whose triggers run after it (on its run.completed or run.failed).

Before changing or retiring a script, check who would notice.