perf-baseline-manager

$npx mdskill add ComposioHQ/awesome-claude-plugins/perf-baseline-manager

Store one baseline JSON per version for performance tracking.

  • Consolidates metrics and environment data into single files.
  • Overwrites older records to prevent duplicate version files.
  • Reads state-dir paths to locate and manage baseline storage.
  • Outputs structured JSON with version, metrics, and file path.

SKILL.md

.github/skills/perf-baseline-managerView on GitHub ↗
---
name: perf-baseline-manager
description: "Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version."
version: 1.0.0
---

# 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.

More from ComposioHQ/awesome-claude-plugins

SkillDescription
add-subSubscribe to a skill event. Adds a subscription that injects context before or after a skill runs. Supports optional conditions at both insert-level (inherited by all subscriptions) and subscription-level (AND-stacked). Conditions include fileExists, gitBranch, envSet, envEquals, fileContains (with optional regex).
helpShow skill-bus overview, status, and available commands. Quick reference for all skill-bus features.
list-subsList all active skill-bus subscriptions across global and project scopes, showing merge status, insert-level and subscription-level conditions, effective condition stacking, and what would fire for each skill.
pause-subsTemporarily disable the skill bus. Quick toggle to stop all subscriptions from firing without removing them.
perf-analyzer"Use when synthesizing perf findings into evidence-backed recommendations and decisions."
perf-benchmarker"Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks."
perf-code-paths"Use when mapping code paths, entrypoints, and likely hot files before profiling."
perf-investigation-logger"Use when appending structured perf investigation notes and evidence."
perf-profiler"Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence."
perf-theory-gatherer"Use when generating performance hypotheses backed by git history and code evidence."