Name: performance-benchmark
Rating: 72.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

88%

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

Quality

Content

77%Weight 40%Scale 1-3

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 a clear, sequenced benchmarking workflow and concrete commands, but it is longer than necessary due to redundant example templates and keeps everything inline rather than splitting detailed material into bundle files.

Suggestions

Consolidate the three Step 1 benchmark templates (generic, String Operation, Collection Operation) into a single canonical example plus one varied one to reduce redundancy and token cost.

Move the optional @EgorBot section into a references/ file (e.g. EGORBOT.md) and keep only a one-line pointer in SKILL.md, since the instructions say to use it only when explicitly asked.

Add an explicit validation checkpoint in Step 2 (e.g. confirm the baseline CoreRun launches) before building the changed runtime, to harden the fragile build-and-copy sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient domain-specific guidance, but Step 1 repeats three near-identical benchmark templates (generic structure, String Operation, Collection Operation) that could be consolidated; it is tighter than the verbose anchor at 1 but does not fully earn the every-token-counts anchor at 3.	2 / 3
Actionability	It provides copy-paste-ready BenchmarkDotNet code, exact build commands ("./build.cmd\|.sh clr+libs -rc Release -lc Release"), and the comparison invocation with --coreRun, matching the fully-executable anchor; not 2 because no key detail is left as pseudocode.	3 / 3
Workflow Clarity	The three-step sequence is explicit and numbered (save changes, build baseline, copy testhost, rebuild changed, run comparison) with an error-recovery loop for the GetRuntimeVersion failure; not 2 because checkpoints and recovery guidance are present rather than merely listed.	3 / 3
Progressive Disclosure	Sections are well-organized and external links are clearly signaled, but the document is a ~233-line monolith with no bundle files, so content that could be split (e.g. the optional EgorBot section) is inline; not 3 because nothing is progressively split into referenced files, and not 1 because organization is strong rather than a wall of text.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise, third-person, and clearly answers both what the skill does and when to use it, with natural trigger terms and a narrow, low-conflict niche scoped to dotnet/runtime performance work.

Dimension	Reasoning	Score
Specificity	"Generate and run ad hoc performance benchmarks to validate code changes" names multiple concrete actions (generate, run, validate), matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	It states what it does ("Generate and run ad hoc performance benchmarks…") and gives an explicit "Use this when asked to benchmark, profile, or validate…" trigger, satisfying both what and when; not 2 because the when clause is explicit rather than implied.	3 / 3
Trigger Term Quality	"benchmark, profile, or validate the performance impact" covers the natural terms a user would say, in third person, with good variation rather than the single-keyword anchor at 2.	3 / 3
Distinctiveness Conflict Risk	The niche is scoped to "a code change in dotnet/runtime" with distinct benchmark/profile triggers, making conflict with other skills unlikely; not 2 because the scope and triggers are clearly distinct rather than overlapping.	3 / 3
	Total	12 / 12 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: ba10a6e

Reviewed: 8 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.