Performance Test Plan
Load testing, profiling, SLA verification, bottleneck identification.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill performance-test-plangit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/testing/skills/performance-test-plan ~/.claude/skills/performance-test-planPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Performance Test Plan Strategy for measuring and verifying performance characteristics. ## Context You are designing performance tests. Measure baseline, set thresholds, identify bottlenecks. ## Domain Context - **Load Testing**: How system behaves under expected/peak load - **Stress Testing**: At what point does system break? - **Profiling**: Where do CPU/memory/I/O bottlenecks exist? - **SLA Verification**: Does system meet response time, throughput commitments? - **Regression Detection**: Did recent changes degrade performance? ## Instructions 1. **Define SLAs**: Response time P99? Throughput? Memory budget? 2. **Create Load Profile**: How many users? What do they do? 3. **Measure Baseline**: Establish baseline metrics before optimization 4. **Profile Hot Paths**: Identify which code consumes CPU/memory 5. **Set Thresholds**: Alert if response time exceeds target 6. **Run Regularly**: Performance tests in CI to catch regressions 7. **Compare Versions**: Before/after comparison for optimization ## Anti-Patterns - Performance tests that are flaky or environment-dependent; unreliable signals - Benchmarking without realistic load; lab results don't match production - Micro-optimizations without profiling; premature optimization is evil - Ignoring memory leaks in performance tests; good data won't show memory creep - Setting unrealistic SLAs; know your hardware limits ## Further Reading - Brendan Gregg, _Systems Performance: Enterprise and the Cloud_
Details
- Skill name
performance-test-plan- Repository
- sethdford/claude-skills
- Path
engineer/testing/skills/performance-test-plan/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Performance Test Plan skill do?
Load testing, profiling, SLA verification, bottleneck identification.
How do I install the Performance Test Plan skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Performance Test Plan popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Performance Test Report
48sethdford/claude-skills
Expert approach to performance-test-report in performance testing. Use when working with .
Performance Baseline
48sethdford/claude-skills
Expert approach to performance-baseline in performance testing. Use when working with .
Property Based Testing
48sethdford/claude-skills
Generative testing with QuickCheck/Hypothesis; testing properties that should hold for all inputs.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.