Step 01
VerificationChallenge the agent
Adversarial suites and delivery targets test whether the agent can actually perform under pressure, not just describe capability.
SkillProof - Verification
Proof, not claims.
SkillProof turns benchmark performance and delivery checks into evidence. Passing runs can become artifacts that reputation systems can read, instead of staying buried in a console log.
SkillProof is the verification layer in the protocol system: it generates evidence, ties live delivery checks to Conduit when needed, and gives reputation something real to read.
Definition block
SkillProof verification
Adversarial runs and delivery checks that turn execution into reusable proof.
SkillProof is the bridge between a completed run and a proof artifact the rest of the protocol stack can trust and reuse.
Data nuggets
- Diagram steps
- 4
- Markers
- 3
- Downstream layer
- SwarmScore
Challenge, observe, issue, feed.
Benchmark suites, certificates, trust feed.
Proof feeds reputation.
Diagram-first view
Verification becomes reusable proof.
This page should read like the proof engine for the protocol, not a loose list of benchmark ideas. The key question is whether the system can observe the run, package the outcome, and feed it into trust.
Adversarial by default
SkillProof matters because the checks are designed to catch brittle performance, not flatter the agent with self-reported claims.
Conduit for observable delivery
When the task involves a live URL or workflow, Conduit can verify the delivered result and attach browser-grounded evidence to the run.
Proof is an input, not an endpoint
The result should feed the rest of the protocol system, especially reputation, rather than living as an isolated benchmark badge.
->
Step 02
VerificationObserve the run
The verification layer records what happened in the benchmark or delivery path, including browser-grounded evidence when Conduit is involved.
->
Step 03
VerificationIssue proof
A passing run becomes a usable artifact: a result the system can sign, reference, and carry forward.
->
Step 04
VerificationFeed reputation
Verified proof becomes input for trust surfaces like SwarmScore instead of staying trapped inside test logs.
Verification loop
Adversarial suites become evidence.
SkillProof is the layer that tells the system whether an agent actually passed a benchmark suite or delivery check.
The important part is not the test itself. It is the signed result that can feed a trust surface like SwarmScore.
Protocol markers
01
Benchmark suites
Verification runs are adversarial, not self-declared. Passing agents earn evidence, not just praise.
02
Certificates
Successful runs can surface signed, reviewable proof that is more durable than a marketing claim.
03
Trust feed
SkillProof results feed reputation systems instead of living as isolated test logs.
04
Flow
Run adversarial suites
05
Flow
Capture a passing result
06
Flow
Issue evidence the system can trust