PluginPublic

testmuai/rook-cli

Rook CLI by TestMu AI (Formerly LambdaTest). Use rook to test, evaluate, red-team or regression-check an AI agent the user owns, or to interpret saved Rook results. Does not apply to ordinary unit tests, browser automation or web UI checks without an AI agent under test.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Profiles: how rook reaches the agent

A profile is a script rook wrote plus the environment-variable names it needs. The execute hook receives the goal on stdin and returns one JSON object with a nonempty agent_reply. Values live in rook env, referenced as ${VAR}, so a profile is safe to commit.

Three kinds of target:

Kind	Give rook	Example
HTTP	a curl	`curl http://127.0.0.1:9110/v1/triage -H 'content-type: application/json' -d '{"input":"look at T-1043"}'`
command	a command line with `{{goal}}`	`claude -p "{{goal}}"`
MCP	a tool on a declared server	see `mcp.md`

Authoring headlessly

printf '%s\n' "curl http://127.0.0.1:9110/v1/triage -H 'content-type: application/json' -d '{\"input\":\"{{goal}}\"}'" > /tmp/profile.txt
rook profile add triage-http --from /tmp/profile.txt --yes
rook profile add refund-cli --command 'claude -p "{{goal}}"' --yes
rook profile test --goal "Say hello and nothing else."
rook profile use <id>
rook profile show <id>

profile add writes the script, runs it against the agent to verify it, and corrects it. It may make several real target calls and costs Rook credits. It may emit text despite --json; --yes (or --allow rules) permits its test calls without a prompt. With neither --from nor --command, it reads the material from stdin. If authoring stops after saving a profile but before verification, the CLI keeps it as unverified. Inspect the saved script and generated profile README, then use rook profile test <id> or rook profile fix <id> as appropriate; do not treat the draft as ready to run.

profile test calls the agent once with --goal and says what came back. Run it before the first rook run and after any change to the agent's URL, auth, or command. The call is real: read agent.yaml for write: true calls before it, as before a run, and give it a goal that asks for nothing but a reply.

profile fix [id] --what "<what is wrong>" diagnoses and repairs; without --what it runs the profile and finds out.

Secrets

rook env set '{"API_KEY":"…","BASE_URL":"https://staging.example.com"}'
rook env list                                          # masked
rook env show API_KEY
rook env rm API_KEY

Never paste a value into a profile, a scenario, a transcript, or a commit. Reference it as ${API_KEY}. A verified profile add can store values it actually used during verification; check rook env list and set any remaining variables with rook env set. The shell's value takes precedence over a stored value. rook env show prints the full secret, so avoid it in logs.