Perf Baseline Manager
- 2 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/awesome-slash
perf-baseline-manager is a skill that manages performance baselines, keeping one baseline JSON per version and comparing versions.
About
This skill manages performance baselines by storing one JSON file per version and comparing versions. A developer uses it to keep a consistent record of benchmark metrics and environment metadata across releases. It enforces a single baseline per version and overwrites older baselines for the same version to avoid duplicates.
- Manages performance baseline storage and version comparison
- Enforces exactly one baseline JSON per version under a state directory
- Records metrics plus environment metadata for each baseline
Perf Baseline Manager by the numbers
- 2 all-time installs (skills.sh)
- Ranked #467 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
perf-baseline-manager capabilities & compatibility
- Capabilities
- baseline management · regression tracking · performance analysis
- Use cases
- debugging · data analysis
What perf-baseline-manager says it does
One baseline JSON per version.
Store under `{state-dir}/perf/baselines/<version>.json`.
Do not create multiple files for one version.
npx skills add https://github.com/avifenesh/awesome-slash --skill perf-baseline-managerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/awesome-slash ↗ |
What it does
Store and compare one performance baseline JSON per version, recording metrics and environment metadata.
Who is it for?
Developers tracking benchmark regressions across releases who need a single canonical baseline per version.
Skip if: Running the benchmarks themselves or analyzing why a regression occurred.
When should I use this skill?
You are managing perf baselines, consolidating results, or comparing versions.
What you get
One authoritative baseline JSON per version with metrics and environment metadata, ready for comparison.
- per-version baseline JSON
By the numbers
- one baseline JSON per version
Files
perf-baseline-manager
Manage baseline storage and comparison.
Follow docs/perf-requirements.md as the canonical contract.
Required Rules
- One baseline JSON per version.
- Store under
{state-dir}/perf/baselines/<version>.json. - Record metrics + environment metadata.
Output Format
baseline_version: <version>
metrics: <summary>
file: <path>Constraints
- Overwrite older baseline for the same version.
- Do not create multiple files for one version.
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
How many baseline files per version?
Exactly one baseline JSON per version, stored under the state directory's perf/baselines folder.
What happens to an older baseline for the same version?
It is overwritten so there is never more than one file for a single version.