FAQ · Terminology without fog

What the evaluation proves—and what it does not.

Agent evaluation language is dangerously easy to overstate. These answers keep objective verification, model judgment, source identity, validation, holdouts, and release claims distinct.

Skivolve

Product and scope

What is Skivolve?

Skivolve is an open-source Python framework for reproducible A/B evaluation of agent skills and instruction bundles through agent harnesses. Suites define the observable task, source variants, cases, verifier resources, provider boundaries, and comparison arms.

Does Skivolve automatically improve a skill?

No. It evaluates candidate changes. A separate human or system may propose the candidate, but Skivolve does not claim autonomous self-improvement.

Is it an LLM benchmark or leaderboard?

No. The project does not publish model rankings or claim that one harness or bundle is superior. Its reference corpus demonstrates an evaluation contract.

Can it evaluate instructions outside software engineering?

Yes. A suite may target any instruction bundle with cases that exercise observable behavior. New domains should use objective case verifiers or contribute a separately calibrated comparator profile.

Why is it an expert Linux alpha?

The isolation model depends on Linux user and mount namespaces plus transient systemd --user units. The current release expects operators to understand provider credentials, local runtime prerequisites, and the documented trust boundary.

Method

Verifiers, judges, and ordering

What is an objective case verifier?

A bounded executable oracle that checks the case’s declared observable behavior. It must accept a known-good implementation and reject known-bad and adversarial variants for the failure modes it claims to detect.

Why not use a model judge for every result?

Model judgment is not an independent oracle for crisp behavior and can leak identity or presentation order. Skivolve uses objective verification first and permits calibrated comparison only for declared ambiguity.

What does blinded AB/BA comparison mean?

The two artifacts are anonymized and presented in both A/B and reversed B/A order. Balanced ordering makes presentation effects visible and reduces—but does not eliminate—judge bias.

What does calibrated comparison establish?

A versioned profile records the rubric, corpus, schemas, model configuration, expected decisions, support by criterion, runtime sources, and limits. Calibration authority remains scoped to that profile and corpus; it is not a universal model-judge guarantee.

What outputs can a case evaluate?

Current schemas support canonical workspace diffs, strict LF-normalized final text, and bounded RFC 8785 canonical final JSON.

Trust

Source, providers, and holdouts

Why bind evaluation sources to Git?

A path or prompt label does not prove what bytes ran. Skivolve fingerprints exact commits, bundle locators, file bytes, executable modes, and context files, then rejects source drift before dispatch.

Does provider support equal production authority?

No. Claude has generation and comparison capabilities under the production contract. Codex app-server is a diagnostic generation adapter. The deterministic fake is test-only. Capability and authority are separate.

Does the public corpus contain a private holdout?

No. It contains train and validation cases. A private release holdout must be stored separately and frozen before candidate evaluation.

Why is a holdout plan single-attempt?

Every non-dry attempt records consumption before provider or comparator dispatch, including failed and interrupted runs. This reduces accidental reruns, but a hostile same-UID process can remove that record; it is not an append-only or cryptographic control. The recorded reviewer labels and references are operator declarations, not authenticated proof of review.

Can Skivolve protect against hostile root or kernel compromise?

No. The isolation model does not claim protection against malicious root, a compromised kernel, hostile same-UID processes outside the unit, or colluding reviewers. Sensitive holdouts belong on a dedicated trusted host.

Quick glossary

The nouns that carry authority.

Skill or instruction bundle

The versioned source under evaluation—not the evaluator and not the provider.

Harness provider

The reviewed adapter that invokes an agent runtime under declared capabilities and limits.

Case

A task, fixture, verifier, resource limit, artifact contract, and set of observable expectations.

Validation split

Public cases not used as the train split. Still public, and therefore not a private release holdout.

Comparator profile

A versioned judgment contract with locked resources, calibration support, provider identity, and authority scope.

Evidence gate

A required observation that must close at its own authority layer before the claim may proceed.