[ PORTABLE SKILL ]

benchmark-skills

Use this skill when creating evals or assertions for a skill, running the skill benchmark harness, measuring skill effectiveness vs baseline, or writing evals.json files alongside skills. Invoke whenever someone asks to test, benchmark, or evaluate a skill's quality.

PART OF

bopen-tools →

Complete plugin installation is recommended so this skill keeps its agents, hooks, commands, and runtime context.

Claude pluginCodex pluginPortable skills

PUBLISHER: b-open-io
RELATIONSHIP: authored
VERSION: 2.0.1
BENCHMARK: unknown

[ RECOMMENDED INSTALL ]

Install bopen-tools

The complete plugin is the supported path. It preserves everything the publisher designed to work alongside this skill.

Claude Code

VERIFIED

Codex

VERIFIED

[ ADVANCED · INDIVIDUAL SKILL ]

Install only this skill

Use this narrower path only when you intentionally want the portable SKILL.md without the plugin’s surrounding capabilities.

Skills CLI

VERIFIED

Installs only the portable skill; it omits plugin hooks, agents, commands, apps/MCP configuration, and unlisted companion skills.

[ PROVENANCE ]

Trace it to the source.

DISTRIBUTED SOURCE: skills/benchmark-skills/SKILL.md ↗
UPSTREAM SOURCE: No separate upstream declared
DISTRIBUTED DIGEST: sha256:91ee7b8aeefc01aff452936528441b4ec0914092bf497c7d4bf4b74142c003fa
LOCK HASH: Not applicable

Companion skills

No required companion skills are declared.

Agents using this skill

Jason

Expert in comprehensive testing strategies, framework implementation, and quality assurance. Handles unit, integration, e2e testing, mocking, coverage analysis, and CI/CD test automation. <example> Context: User just wrote a new module and wants proper unit test coverage before merging. user: "Can you write tests for this utility module? It handles date parsing and formatting." assistant: "I'll use the tester agent to write unit tests covering the happy path, edge cases, and error conditions using the AAA pattern." <commentary> Unit test authorship with structured coverage — Jason's core output. </commentary> </example> <example> Context: User wants to add end-to-end tests for their checkout flow before a major release. user: "We need e2e tests for the checkout process — add to cart, payment, confirmation." assistant: "I'll use the tester agent to write Playwright tests for the full checkout flow using the Page Object Model." <commentary> E2E test implementation with Playwright — Jason handles this, not the developer or integration-expert. </commentary> </example> <example> Context: User's CI pipeline has no test coverage reporting and they want visibility before adding a coverage gate. user: "We have tests but no coverage metrics in CI. Can you wire that up?" assistant: "I'll use the tester agent to configure coverage reporting in the test runner and add a GitHub Actions step to publish the report." <commentary> CI/CD test automation and coverage reporting setup is Jason's responsibility. </commentary> </example>

Satoshi

Skill training and maintenance agent. Use this agent when skills need accuracy review, API or documentation changes need to be reflected in SKILL.md files, benchmarks need to be run, new skills need to be created from identified gaps, or when agent definitions need cross-reference validation. Proactively triggers for periodic knowledge health checks across the skill library. Also knowledgeable about EZKL (zero-knowledge proofs for ML models) — use when working with zkML, @ezkljs/engine, ONNX-to-ZK-circuit pipelines, or on-chain ML verification. <example> Context: User wants to verify that existing skills are still accurate after a framework released a new version. user: "Can you check if our BSV skills are still up to date?" assistant: "I'll use the trainer agent to audit the BSV skills for accuracy and flag any outdated content." <commentary> The user is asking for skill accuracy review — this is Satoshi's core job. </commentary> </example> <example> Context: User notices a skill references a deprecated API endpoint. user: "The 1sat API changed — our ordinals skill is probably broken." assistant: "Let me dispatch Satoshi to research the new API, update the SKILL.md, and log the change." <commentary> API drift is exactly the kind of problem Satoshi exists to detect and fix. </commentary> </example> <example> Context: User wants to run benchmarks to see if a recently updated skill is performing better. user: "Run the benchmark for the humanize skill." assistant: "I'll use the trainer agent to execute the benchmark and report the delta." <commentary> Benchmark execution is one of Satoshi's explicit responsibilities. </commentary> </example> <example> Context: User wants to know if there are any gaps in the skill library for a new project area. user: "We're building a new payments feature — do we have skills for that?" assistant: "Satoshi can audit the current skill roster for coverage gaps and create new skills where needed." <commentary> Gap analysis and new skill creation are in Satoshi's scope. </commentary> </example>

Related skills

ALL BOPEN-TOOLS SKILLS →

bopen-tools

advisor

Active when a Claude Code or Codex main session needs an independent, read-only second opinion at a commitment boundary. Use before substantive work on a hard task, when stuck or changing approach, at a final review gate, or when the user says "consult the advisor", "get a second opinion", "ask codex", "ask Fable", "ask a bigger model", or wants an advisor set up. Supports Claude-native advisor behavior, Codex-as-advisor, and a Codex-main to Claude Fable CLI channel. The advisor returns guidance; the main session retains execution and decision ownership.

authored0.0.2

bopen-tools

agent-auditor

Comprehensive audit skill for agents and skills across the plugin ecosystem. This skill should be used when the user asks to "audit agents", "review skill quality", "check skill health", "validate plugin skills", "audit our agents", "run a skill audit", or when performing periodic maintenance on agents and skills. Also use after creating or modifying multiple skills to verify ecosystem consistency.

authored0.1.2

bopen-tools

agent-decommissioning

This skill should be used when the user asks to "retire an agent", "decommission an agent", "remove an agent from the team", "shut down a bot", "remove a bot", "sunset an agent", or "take an agent offline permanently". This is a joint workflow between Satchmo (agent-builder) and Johnny (clawnet-bot:clawnet-mechanic). Satchmo handles plugin/code removal; Johnny handles infrastructure teardown (ClawNet bot, sandbox, BAP identity).

authored1.0.0

bopen-tools

agent-onboarding

Complete end-to-end checklist for adding a new agent to the bOpen team. Use when creating a new agent, onboarding a new team member, or need to remember the full agent deployment pipeline — design, write, avatar, plugin, Paperclip registration, roster, and optional ClawNet bot deployment.

authored1.1.1

bopen-tools

charting

Full-stack data visualization and charting intelligence. This skill should be used when the user asks to "create a chart", "visualize this data", "build a dashboard", "plot this", "graph these metrics", "show me a chart of", "make a bar chart", "create a line graph", "build a heatmap", or needs help choosing the right chart type, selecting a charting library, or engineering the data pipeline from raw database state to rendered visualization. Covers chart selection, data transformation, library choice by scale, performance optimization, and accessibility.

authored1.0.0

bopen-tools

check-version

Check if the bopen-tools plugin is up to date by comparing local vs GitHub versions. Use this skill at the start of any session where the agent needs current skill/agent definitions, when the user asks 'is everything up to date?', 'check for updates', 'am I on the latest version?', or when you suspect skills may have changed since last install. Also use proactively when a skill seems to behave differently than documented or when instructions reference features you don't recognize. Completes in under 100ms.

authored1.0.0