Repository navigation
feat(agent): evaluate evolved skill candidates - #148
Merged
Pepps233 merged 2 commits intoAug 31, 2026
Merged
Conversation
This was referenced Aug 28, 2026
Pepps233
force-pushed
the
feat/evaluate-evolved-skills
branch
from
August 30, 2026 02:56
8d78ce2 to
4c246ff
Compare
Pepps233
force-pushed
the
feat/evaluate-evolved-skills
branch
from
August 30, 2026 15:10
4c246ff to
21fbbd8
Compare
Pepps233
force-pushed
the
feat/evaluate-evolved-skills
branch
from
August 30, 2026 21:32
21fbbd8 to
b089030
Compare
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
Evaluate structurally valid evolved-skill drafts with separate retrieval and behavioral gates before they can enter the accepted candidate state, without adding a skill writer or activation path.
Reasoning
Evidence qualification and deterministic draft validation establish recurrence, provenance, structure, scope, and security, but they do not show that a skill is retrieved for the right tasks or improves downstream outcomes. Exact retrieval accuracy is also insufficient because a selected skill can still regress execution or be misapplied to neighboring and unrelated tasks.
Evaluation therefore uses exact source replay for reproducibility, independently held-out intended cases for improvement, and hard-negative and unrelated cases for non-regression. Baseline and candidate-available arms remain pinned to the same harness and deterministic verifier configuration.
Changes
evaluation-pendingcheckpoints toacceptedorquarantined, and invalidate stale evaluations when proposal revisions change.Stack
Position: 8 of 12
Base: #147
Next: #149
Testing
cd packages/evolution && node ../../node_modules/vitest/dist/cli.js --run test/skill-evaluator.test.ts test/skill-candidate-registry.test.ts test/skill-candidate-worker.test.ts test/filesystem-store.test.ts test/skill-draft-validator.test.ts test/skill-synthesizer.test.tsnpm run check(blocked by pre-existing model-catalog TypeScript failures reproduced at feat(agent): measure procedural information loss #147 headc09ee8035; nopackages/evolutionerrors)This pull request is AI-generated by Diffex.