docs: document single-file form for eval questions#11145
Merged
Conversation
Eval questions can live in a single top-level agents/eval_questions.yml file or be split across agents/eval_questions/*.yml files; the parser merges all of them. Lead the authoring example with the single-file form and remove the directory-only framing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Claude finished @keydunov's task in 41s —— View job Review: docs: document single-file form for eval questionsVerdict: LGTM — accurate, well-scoped clarification. No blockers. Details
What's good
Nits (non-blocking)
Out of scope for this review
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Evals docs page documented eval-question authoring as only the directory form (
agents/eval_questions/*.yml), implying a single file is not supported. That's inaccurate.The cube-runtime agents-config parser picks up both a single top-level
agents/eval_questions.ymlfile and any number of files underagents/eval_questions/, flattening every file'seval_questions:list into one set (verified on a live deployment).Changes
agents/eval_questions.ymlform (simplest entry point), then present the directory form as the way to split as the set grows.# agents/eval_questions.yml.Everything else (the
eval_questions:list shape;name+question+ exactly one ofsql/certifiedQuery; optionalspace:) is unchanged.🤖 Generated with Claude Code