fairtask-eval skill: run the evaluation tooling from inside an agent session - #7
Merged
Merged
Conversation
…n agent session Co-Authored-By: Claude Fable 5 <noreply@anthropic.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
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.
Why
The screening skill (
/fairtask) covers the product use, but everything else a reader might want to see — the evaluation set, scores, the comparison report, the evidence audit, one instance laid out — still required a terminal. Task authors and judges work inside agents; the evaluation should be reachable there too, with numbers that come from the scripts rather than from the model's memory.What changed
skills/fairtask-eval/SKILL.md: maps a request to one of the repository's evaluation commands (data:eval-set,score,report,audit,code-check,data:annotations --check,show,trajectory), runs it from the repository root, prints the output verbatim, and adds one or two sentences on how to read it. Offline except the pinned data fetches; makes no model calls; refuses to start paid reproduction runs and points at REPRODUCE.md instead.Skills (2); the manifest validator checks both skills' frontmatter.Verified by invoking the skill for "show the evaluation set": it ran
npm run data:eval-set, printed the 30-row table, andgit statusstayed clean. (A first version of this branch, #6, accidentally carried a 6-byte edit to the annotation CSV; CI's provenance check caught it, which is what it is for.)