Skip to content

Publish a script with your agent

Your coding agent can prepare a script you already have for your team. Its inputs become a form and an agent tool, secrets stay out of the code, and the agent proves the draft works before you decide to publish.

Connect it to Reminix’s MCP server, or let it use the command line, and give it the skill that explains how Reminix works (Use with AI agents).

Publish scripts/<your-script> to Reminix. Search the team's
scripts first in case one exists. Describe its inputs in the input
schema with clear titles, write a short README, keep every secret out of
the code (ask me to save it as a Reminix secret) and declare only the
hosts it calls. Upload it as a draft, test-run it with realistic inputs,
show me the result, and ask me before publishing.
  1. reminix init creates reminix.json, README.md and an entry file with run(inputs, ctx).
  2. It fills in the inputs, the README and the code. It ports a Python script to JavaScript, keeping its inputs and behaviour.
  3. reminix scripts publish uploads a draft. Nobody else can run it yet.
  4. It test-runs the draft: reminix scripts run <slug> --version <n> --input '{…}' --log. Reminix marks a test run as one, doesn’t count it as the team’s use, and starts no triggers or webhooks from it.
  5. It shows you the result and asks you to publish, in the app or with reminix scripts publish --publish. If your workspace requires a second person to publish, you get an approval link.

The script’s owner, workspace owners and admins, and the person who uploaded a version can test-run that version:

Terminal window
curl -X POST https://api.reminix.com/v1/scripts/nightly-report/versions/3/runs \
-H "Authorization: Bearer $REMINIX_TOKEN" -H "X-Workspace: acme" \
-H "Content-Type: application/json" -d '{ "inputs": { "team": "sales" } }'

The script’s approval policy still applies to test runs.