One post tagged with "evaluation"

Writing a capability into a SKILL.md and packaging it as an Agent plugin is not hard. The hard part comes later: once that capability is invoked over and over by different users, in different projects, and on different Agent hosts, how do you guarantee that it is still triggered, executed, and verified correctly? And how do you prove that a change made it better rather than worse?

Drawing on how Better Harness is actually developed, this post walks through five engineering practices - spec-driven behavior, context orchestration, deterministic verification, behavioral evaluation, and the evidence loop - that move a plugin capability from "it works when I run it" to a software asset that is verifiable, maintainable, and safe to evolve.