Name: performance-benchmark
Rating: 64.8 (1 reviews)
Author: dotnet

performance-benchmark

Generate and run ad hoc performance benchmarks to validate code changes. Use this when asked to benchmark, profile, or validate the performance impact of a code change in dotnet/runtime.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/performance-benchmark/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable code and exact commands, and is well-organized with one-level references. The main weaknesses are repetition in the code examples that hurts conciseness, and the absence of an explicit validation/feedback checkpoint in the baseline-vs-changed build workflow.

Suggestions

Add an explicit validation step to Step 3 — e.g., confirm the benchmark completed and sanity-check that baseline and changed CoreRun binaries differ before trusting the comparison — to satisfy the batch-workflow feedback-loop expectation.

Reduce repeated boilerplate: show the BenchmarkSwitcher/`using` header once, then show only the differing benchmark class bodies for the string and collection examples to improve token efficiency.

Move the @EgorBot target-flag list and common options to a short reference or a single compact table to avoid inlining reference material in the main body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but repeats the full BenchmarkSwitcher boilerplate across three code examples and re-states several BenchmarkDotNet principles Claude would already know, which could be tightened without losing clarity.	3 / 5
Actionability	Provides fully executable, copy-paste-ready benchmark code and exact shell commands (`./build.cmd\|.sh clr+libs -rc Release -lc Release`, the `dotnet run -c Release -- --filter "*" --coreRun ...` invocation), covering the common cases concretely.	5 / 5
Workflow Clarity	Steps 1–3 are clearly sequenced, but this batch/parallel build-and-compare workflow lacks an explicit validation checkpoint confirming the benchmark actually ran successfully or that baseline/changed binaries are non-stale before comparison; the cap for missing validation in a batch workflow applies.	3 / 5
Progressive Disclosure	Structure is good with clear section headings and one-level-deep external links (Microbenchmark Design Guidelines, BenchmarkDotNet CLI args, EgorBot manual) that are clearly signaled; minor gap is that some reference-style material (the EgorBot target flags and options) is inlined rather than linked out.	4 / 5
	Total	15 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it concisely states both the capability and a concrete 'Use when...' trigger clause, and scopes itself to dotnet/runtime. Adding synonyms like 'perf', 'measure', and 'speed up' would push trigger term coverage to the top level.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Generate and run ad hoc performance benchmarks to validate code changes') covering benchmark generation, execution, and validation, with only minor gaps in coverage (e.g., no mention of comparison/reporting).	4 / 5
Completeness	Explicitly answers both what ('Generate and run ad hoc performance benchmarks to validate code changes') and when ('Use this when asked to benchmark, profile, or validate the performance impact of a code change in dotnet/runtime'), matching the top anchor.	5 / 5
Trigger Term Quality	Good natural trigger coverage ('benchmark, profile, or validate the performance impact'), though it omits common synonyms like 'perf', 'measure', or 'speed up' that a user might actually say.	4 / 5
Distinctiveness Conflict Risk	The 'dotnet/runtime' scope and benchmarking niche make it mostly distinct from other skills, but 'validate code changes' is broad enough to risk minor overlap with general code-review or testing skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: dotnet/runtime
Path: .github/skills/performance-benchmark/SKILL.md
Commit: b030ed4

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.