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.
npx skills add foryourhealth111-pixel/Vibe-Skills --skill performance-testing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Performance testing ## Running benchmarks ```bash cd tools/performance # Run all benchmarks (~15-20 minutes) dotnet run -c Release # Run specific category dotnet run -c Release --filter *StreamIndicators* dotnet run -c Release --filter *BufferIndicators* dotnet run -c Release --filter *SeriesIndicators* # Run specific indicator dotnet run -c Release --filter *.EmaHub ``` ## Adding benchmarks ###
What does the performance-testing skill do?
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.
How do I install it?
Run `npx skills add foryourhealth111-pixel/Vibe-Skills --skill performance-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From foryourhealth111-pixel/Vibe-Skills, a repository with 2,593 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.