performance-testing

Benchmark indicator performance with BenchmarkDotNet. Use for Series/Buffer/Stream benchmarks, regression detection, and optimization patterns. Target 1.5x Series for StreamHub, 1.2x for BufferList.

Quality

85%

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

82%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.

An efficient, highly actionable body built around concrete commands and executable code patterns, with clear sections and a single well-signaled reference. Workflow clarity is good but could add an explicit regression-fix-and-rerun loop.

Suggestions

Add an explicit feedback loop after regression detection: on exit code 1, inspect the flagged indicators, apply a listed optimization pattern, then re-run detect-regressions.ps1 to confirm the fix.

Move or repeat the 'See references/benchmark-patterns.md' pointer near the 'Required optimization patterns' section so the reference is discoverable where it is most relevant.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command/code-driven with little explanation of concepts Claude already knows, though the two 'Note' lines and the somewhat overlapping 'Required'/'Prohibited' pattern lists could be tightened slightly.	4 / 5
Actionability	Provides copy-paste-ready commands (dotnet run filters, detect-regressions.ps1 with thresholds) and complete executable code snippets for the Series/Buffer/Stream patterns, covering the common cases.	5 / 5
Workflow Clarity	A clear benchmark → regression-detection → baseline-creation sequence exists with a validation checkpoint via exit codes (0/1), but the error-recovery feedback loop after a detected regression is only implicit.	4 / 5
Progressive Disclosure	Well-organized into labeled sections with a single one-level-deep reference (references/benchmark-patterns.md, verified present), though the reference is signposted only once at the very end rather than near the patterns it elaborates.	4 / 5
	Total	17 / 20 Passed

Description

87%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.

A strong, specific description that pairs a clear 'what' with an explicit 'Use for' trigger clause and concrete numeric performance targets. Trigger-term coverage is good but could include more everyday synonyms.

Suggestions

Add common natural-language synonyms like 'performance', 'speed', or 'slow indicator' so the description triggers when users phrase the need casually.

Replace the generic phrase 'optimization patterns' with a more concrete action such as 'apply hot-path optimization patterns' to sharpen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (indicator performance with BenchmarkDotNet) and several concrete actions—benchmarking, regression detection, optimization patterns—with explicit numeric targets, but 'optimization patterns' is somewhat generic and coverage of distinct actions is not exhaustive.	4 / 5
Completeness	Clearly states what it does ('Benchmark indicator performance with BenchmarkDotNet') and explicitly when to use it ('Use for Series/Buffer/Stream benchmarks, regression detection, and optimization patterns') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like 'Benchmark', 'regression detection', and 'Series/Buffer/Stream' appear, but it leans on domain-internal jargon and misses common synonyms users might say (e.g. 'performance', 'speed', 'slow').	4 / 5
Distinctiveness Conflict Risk	Occupies a narrow niche (BenchmarkDotNet-based indicator benchmarking with StreamHub/BufferList targets) with distinct triggers, making accidental activation by unrelated skills unlikely.	5 / 5
	Total	18 / 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: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/performance-testing/SKILL.md
Commit: d5ae560

Reviewed: 1 day 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.