Skip to content

docs: explain the auto-generated rubric evaluator in step 11 #294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
placerda merged 1 commit into from
Jun 10, 2026
Merged

docs: explain the auto-generated rubric evaluator in step 11 #294

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/tutorial-prompt-agent-quickstart.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -902,6 +902,15 @@ Fill in two kinds of real names: the rubric evaluator name and the rubric
dimension names. Do not invent values — both must come from files
`agentops eval init` already generated on disk.

> **About the auto-generated evaluator.** When you ran `agentops eval
> init`, azd seeded `src/travel-agent/eval.yaml` with two kinds of
> evaluators: built-ins like `builtin.coherence` and `builtin.fluency`
> (general response-quality checks) plus a local rubric evaluator —
> typically `name: smoke-core` — whose `local_uri` points at a JSON file
> with rubric dimensions specific to this Travel Agent. That local
> evaluator is the hook AgentOps `rubrics:` bind to. You will reference
> its `name:` and its dimension `id`s in the next two steps.

**1. Find the evaluator name.** Open `src/travel-agent/eval.yaml` and
look under `evaluators:` for the entry with a `local_uri`:

Expand Down
Loading