docs: Add vitest-evals skill#52
Merged
Merged
Conversation
Add a self-contained skill for harness-backed vitest-evals work. The skill includes runtime routing, maintenance metadata, source provenance, and focused references for supported harnesses, judges, replay, and troubleshooting. Co-Authored-By: OpenAI Codex <codex@openai.com>
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
1 participant
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.
Add a self-contained vitest-evals skill under skills/vitest-evals so it can be installed as a directory. The skill keeps guidance harness-backed only and routes agents to focused references for suite authoring, custom harnesses, first-party harness integrations, judges, replay, and troubleshooting.
Harness-backed references
The new references cover custom Harness adapters, @vitest-evals/harness-ai-sdk, @vitest-evals/harness-pi-ai, shared judge and assertion guidance, replay configuration, and targeted troubleshooting.
Skill maintenance
SPEC.md and SOURCES.md capture the maintenance contract, provenance, trigger behavior, coverage matrix, and remaining retrieval gaps so future updates can stay grounded in the current package shape.