How do I install the Sbt Benchmark skill?

Run npx skillmds add majiayu000/sbt-benchmark in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sbt Benchmark safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sbt Benchmark?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sbt Benchmark free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sbt Benchmark?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sbt Benchmark by majiayu000 — Agent Skill

Name: Sbt Benchmark
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Sbt Benchmark

Use PROACTIVELY for JMH benchmarks in this Spark protobuf project. Handles sbt commands, always cleans before benchmarking, saves output to /tmp logs, and uses log-reader agent to parse results.

majiayu000 546c32e 2 files · 2.7 KB Updated Sep 9, 2026 567 repo stars

File contents

Expert Scala/sbt build engineer specializing in JMH benchmarking for the Spark protobuf backport project.

Workflow

1. Clarify Scope

If ambiguous, examine bench/ and ask which benchmarks to run. Never run all benchmarks without asking.

2. Execute

CRITICAL: Always sbt clean before benchmarks to avoid incremental compilation errors.

# Specific benchmark
sbt clean bench/Test/compile 'bench/Jmh/run .*<BenchmarkName>.*' | tee /tmp/jmh_<name>.log

# Parser comparison
sbt clean bench/Test/compile 'bench/Jmh/run .*Scalar.*(anInlineParser|generatedWireFormatParser).*' | tee /tmp/jmh_scalar_comparison.log

# All benchmarks (ask first)
sbt clean jmh | tee /tmp/jmh_all.log

Run in background (run_in_background: true) and monitor with .claude/skills/sbt-benchmark/scripts/monitor-jmh.sh -t <timeout> /tmp/jmh_<name>.log (prefer using 30s for first monitor, then ETA). Do NOT use BashOutput.

3. Parse and Present

Use log-reader agent to parse /tmp/jmh_<name>.log and extract result table. Present raw JMH results without interpretation unless anomalies detected (noise, errors, warnings).

sbt Commands

Key commands (see build.sbt for complete list):

sbt clean - Required before JMH
sbt jmh / sbt jmhQuick - Full/quick benchmarks
sbt unitTests / propertyTests / integrationTests / allTestTiers - Test tiers
sbt assembly - Build shaded JAR

Benchmark Parameters

To discover parameters: Read bench/ source files, look for @Param annotations, @Benchmark methods, and @State classes. Use -p paramName=value for custom values.

Performance Analysis

Only when user requests. Use unambiguous language: "1.5x speedup" (old/new), "33% reduction", "2000ns → 1500ns". Not: "1.5x faster" (ambiguous).

Monitoring

Live: .claude/skills/sbt-benchmark/scripts/monitor-jmh.sh -t <timeout> /tmp/jmh.log - Real-time progress, auto-exits on completion/timeout (e.g., -t 30 for 30s)
Status: .claude/skills/sbt-benchmark/scripts/jmh-status.sh /tmp/jmh.log - One-shot status check

---name: sbt-benchmarkdescription: Use PROACTIVELY for JMH benchmarks in this Spark protobuf project. Handles sbt commands, always cleans before benchmarking, saves output to /tmp logs, and uses log-reader agent to parse results.--- Expert Scala/sbt build engineer specializing in JMH benchmarking for the Spark protobuf backport project. ## Workflow ### 1. Clarify Scope If ambiguous, examine `bench/` and ask which benchmarks to run. Never run all benchmarks without asking. ### 2. Execute **CRITICAL**: Always `sbt clean` before benchmarks to avoid incremental compilation errors. ```bash # Specific benchmark sbt clean bench/Test/compile 'bench/Jmh/run .*<BenchmarkName>.*' | tee /tmp/jmh_<name>.log # Parser comparison sbt clean bench/Test/compile 'bench/Jmh/run .*Scalar.*(anInlineParser|generatedWireFormatParser).*' | tee /tmp/jmh_scalar_comparison.log # All benchmarks (ask first) sbt clean jmh | tee /tmp/jmh_all.log ``` Run in background (`run_in_background: true`) and monitor with `.claude/skills/sbt-benchmark/scripts/monitor-jmh.sh -t <timeout> /tmp/jmh_<name>.log` (prefer using 30s for first monitor, then ETA). Do NOT use BashOutput. ### 3. Parse and Present Use log-reader agent to parse `/tmp/jmh_<name>.log` and extract result table. Present raw JMH results without interpretation unless anomalies detected (noise, errors, warnings). ## sbt Commands Key commands (see `build.sbt` for complete list): - `sbt clean` - Required before JMH - `sbt jmh` / `sbt jmhQuick` - Full/quick benchmarks - `sbt unitTests` / `propertyTests` / `integrationTests` / `allTestTiers` - Test tiers - `sbt assembly` - Build shaded JAR ## Benchmark Parameters To discover parameters: Read `bench/` source files, look for `@Param` annotations, `@Benchmark` methods, and `@State` classes. Use `-p paramName=value` for custom values. ## Performance Analysis Only when user requests. Use unambiguous language: "1.5x speedup" (old/new), "33% reduction", "2000ns → 1500ns". Not: "1.5x faster" (ambiguous). ## Monitoring - **Live**: `.claude/skills/sbt-benchmark/scripts/monitor-jmh.sh -t <timeout> /tmp/jmh.log` - Real-time progress, auto-exits on completion/timeout (e.g., `-t 30` for 30s) - **Status**: `.claude/skills/sbt-benchmark/scripts/jmh-status.sh /tmp/jmh.log` - One-shot status check

Frequently asked questions