calibrate CLI against Calibrate’s public API and
covers the full loop: connect an agent, build tests, run them, and — Calibrate’s
signature move — calibrate the LLM judges against human labels so the
automated scores are trustworthy.
Install
Install every Calibrate skill with one command. Pass--agent to target your
specific coding agent — without it, the command defaults to whichever agent it
detects, which may not be the one you want:
-g flag installs globally (available in all projects). After installing,
restart your coding agent session for the new skills to appear.
You also need the Calibrate CLI (which the skills drive) and an API key:
Skills are the knowledge layer — they teach your agent how to evaluate. The
CLI they drive is the execution layer. See the
overview for how skills, MCP, and
the CLI fit together.
Skills versus MCP and CLI
Skills and the CLI work best together: the skills carry the methodology, and the
CLI runs the operations they describe.
Available skills
Installing the pack adds the following skills. Invoke any of them by name (e.g./connect-agent), or start with /onboard, which
orchestrates the whole set.
The primitives
Every skill maps to one of Calibrate’s five public API resources — deliberately, there is no persona, simulation, trace, dashboard, or report resource.How skills load
Skills load progressively, so they stay cheap in context:- At startup — only each skill’s name and description load (~100 tokens total), enough for your agent to know one exists.
- On activation — the full
SKILL.mdinstructions load when a skill is triggered. - On demand — reference files, assets, and scripts load only when a skill needs them.
skills/<category>/<skill-name>/ with a SKILL.md
entrypoint and optional references/, assets/, and scripts/ folders. The
full source is on GitHub.
Next steps
Run guided onboarding
Kick off
/onboard to go from nothing to a trustworthy first evaluation.Connect the MCP server
Give your agent native Calibrate tools alongside the skills.