This skill should be used for SB-owned benchmark and adversarial evaluation workflows across agents, models, providers, prompts, or implementation approaches.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add alo-exp/silver-bullet --skill silver:benchmark --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Silver:Benchmark?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/alo-exp-silver-benchmark)More formats (shields.io, HTML) on the badges page.
---
name: silver:benchmark
description: >
This skill should be used for SB-owned benchmark and adversarial evaluation
workflows across agents, models, providers, prompts, or implementation
approaches.
argument-hint: "<benchmark task> [--providers <list>] [--rounds N]"
version: 0.1.0
---
# /silver:benchmark - Agent And Approach Evaluation
SB-owned benchmark workflow for repeatable evaluation. External providers may
enrich the run only when installed and requested; SB owns the fixture, scoring,
evidence, and final decision.
**Pre-execution** (blocks benchmark runs until recorded):
`silver:context` → `silver:plan`
**Post-execution:** `silver:execute` → `silver:verify` → `silver:ensure-docs`
Queue source: `hooks/lib/orchestrator-state.sh` (`silver-benchmark` composer).
## Output
Write or update `.planning/BENCHMARK.md`.
The report must include:
- task fixture, constraints, and accepted-answer rubric;
- compared agents/models/providers/approaches;
- cost, latency, tool use, evidence quality, and correctness observations;
- self-evaluation bias checks when applicable;
- winning decision or inconclusive result with next step;
- retained artifacts and cleanup notes.
## Process
1. Display `SILVER BULLET > BENCHMARK`.
2. Define a task fixture that can be repeated without hidden context.
3. Define scoring before running candidates: correctness, requirement coverage,
safety, maintainability, verification quality, cost, and latency.
4. Run each candidate under the same constraints. If external providers are not
available, benchmark local approaches or prompt variants and record the
limitation.
5. Use an adversarial review pass for top candidates when the result will
influence architecture, release, security, or high-cost work.
6. Invoke or apply `silver:domain-audit --pack benchmark-eval`.
7. Normalize findings into `silver:review` or `silver:deep-research` when the
benchmark drives implementation.
## Exit Gate
A benchmark result is valid only when the fixture, rubric, raw evidence, and
decision rationale are sufficient for another session to reproduce the
comparison.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!