From 17d34a8ccacde98bff41bebb78e087a5abbe2e78 Mon Sep 17 00:00:00 2001 From: Paulo Lacerda Date: Wed, 10 Jun 2026 11:18:20 -0300 Subject: [PATCH] docs: drop redundant smoke-core callout from step 10 The `What is smoke-core?` callout previously sat in step 10 right after `agentops eval init`, but the evaluator name is only actually needed in step 11 where `Find the evaluator name` already explains the same content in proper context. Removing the duplicate keeps step 10 focused on running the smoke gate. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- docs/tutorial-prompt-agent-quickstart.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/docs/tutorial-prompt-agent-quickstart.md b/docs/tutorial-prompt-agent-quickstart.md index 54628e4..68f332e 100644 --- a/docs/tutorial-prompt-agent-quickstart.md +++ b/docs/tutorial-prompt-agent-quickstart.md @@ -795,15 +795,6 @@ eval_recipe: src/travel-agent/eval.yaml Use `--force` only when you intentionally want to regenerate an existing `eval.yaml`. For the normal flow, run it without `--force`. -> **What is `smoke-core`?** In the generated `src/travel-agent/eval.yaml`, -> azd may include an evaluator like `name: smoke-core` with -> `local_uri: evaluators\smoke-core\rubric_dimensions.json`. That is the -> local rubric evaluator generated for this quickstart's smoke gate. The -> built-in evaluators (`builtin.coherence`, `builtin.fluency`) check -> general response quality; `smoke-core` points at rubric dimensions -> specific to this Travel Agent. When you add `rubrics:` to -> `agentops.yaml` later, use the evaluator name that appears here. - Run the gate locally: ```powershell