paragon-try-tools

Installation
SKILL.md

Try the Paragon Tools API

Get the user from zero to a real tool run in their own Paragon project, using curl. API calls need a signed JWT, so scripts/paragon-env.sh mints one with openssl (no other dependencies) and loads $PARAGON_TOKEN, $AGENTOS_URL, $ZEUS_URL, and $PARAGON_PROJECT_ID. Shell state doesn't carry over between commands, so start every call with source <this skill's dir>/scripts/paragon-env.sh &&. Below, $T stands for $AGENTOS_URL/api/tools/projects/$PARAGON_PROJECT_ID. Define it inline: T="$AGENTOS_URL/api/tools/projects/$PARAGON_PROJECT_ID".

Rules for secrets and actions

  • Never ask the user to paste a signing key, API key, or token into chat. Never cat, echo, or print the key file or $PARAGON_TOKEN.
  • The key lives in ~/.paragon/signing-key.pem (mode 600), outside any repository.
  • Tools act on the user's real accounts. Run read tools freely. Before running any tool whose sideEffect is write, delete, send, or unknown, show the user the tool and its exact args and wait for a yes.

1. Collect settings from the dashboard

Ask the user for, or have them confirm:

  1. Project ID: in the Paragon dashboard, click Copy Project ID under the environment switcher. It isn't secret.
  2. Region: us (dashboard.useparagon.com) or eu. Defaults to us.
  3. Test user ID: the Connected User to act as. To use apps the user already connected through their own product, use that user's existing Paragon user ID. Otherwise pick any stable ID, such as their email. This becomes the token sub.

Write them to ~/.paragon/agent-os.env:

Installs
6
First Seen
Nov 2, 2026