harness-bench
Manage `@metaharness/darwin` bench suites — `bench create <repo>` scaffolds a JSON suite from a repo's test corpus; `bench verify <suite.json>` checks suite well-formedness. Bench suites are the fixed evaluation corpora that `harness-evolve --bench <suite.json>` scores variants against, decoupling evolution from the repo's natural tests. Degrades gracefully when @metaharness/darwin is absent.
Profile →npx skills add ruvnet/ruflo --skill harness-bench --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Surfaces `metaharness-darwin bench <create|verify>` — the supporting verb for `harness-evolve --bench`. Use when you want evolution scored against a fixed corpus (independent of `npm test`) so champion fitness is comparable across commits or across forks of the same harness. ## When to use - Setting up a new evolution pipeline for a repo whose `npm test` is flaky, slow, or undersized — scaffold a deterministic bench suite once, then evolve against it repeatedly. - CI: `bench verify` the checked-in suite on every PR that touches it (cheap; ~5s). - Forking a harness to a new domain: copy and edit the suite to retarget the evaluation without losing comparability to the parent. ## Algorithm Implementation: [`scripts/bench.mjs`](../../scripts/bench.mjs). ### `--op create` 1. Resolve `--repo` path; reject if missing. 2. Shell to `metaharness-darwin bench create <repo> [--out <suite.json>]`. 3. Default output path: `<repo>/.metaharness/bench/suite.json` (chosen by upstream). 4. Suite shape (per upstream): array of `{ input, expectedOutput, weight }` tasks derived from existing test cases. ### `--op verify` 1. Resolve `--suite` path; reject if missing. 2. Shell to `metaharness-darwin bench
- When to use
- Algorithm
- --op create
- --op verify
- Output shape
- Exit codes
- Graceful degradation
What does the harness-bench skill do?
Manage `@metaharness/darwin` bench suites — `bench create <repo>` scaffolds a JSON suite from a repo's test corpus; `bench verify <suite.json>` checks suite well-formedness. Bench suites are the fixed evaluation corpora that `harness-evolve --bench <suite.json>` scores variants against, decoupling evolution from the repo's natural tests. Degrades gracefully when @metaharness/darwin is absent.
How do I install it?
Run `npx skills add ruvnet/ruflo --skill harness-bench --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.