Providing Performance Optimization Advice Agent Skill
| Produce a prioritized performance-optimization roadmap across frontend, backend, and infrastructure. Use as an explicit/manual helper after bottlenecks are known or suspected, not as the owner of regression detection, profiling capture, or test execution.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill providing-performance-optimization-adviceWhat comes with it
10 661 bytes besides the instructionWhat it tells the agent to use
found in the instruction textThe instruction itself
6 sections, as written by the authorPerformance Optimization Advisor
Positioning
Treat this skill as an explicit/manual advisor for prioritizing optimization work.
When to Use
Use this skill when:
- Prioritizing known or suspected performance bottlenecks from existing logs, traces, benchmarks, or user reports.
- Get recommendations for improving website loading speed.
- Optimize database query performance.
- Improve API response times.
- Reduce infrastructure costs.
Not For / Boundaries
- Build-to-build regression detection: use
detecting-performance-regressions - Raw benchmark execution or profiling capture: use
performance-testing - Test-result packaging for QA audiences: use
generating-test-reports
Typical Outputs
- A ranked optimization backlog by impact and effort
- Concrete hotspots by layer: frontend, backend, infra, or database
- Suggested validation steps to prove the optimization worked
Related Skills
detecting-performance-regressionsto prove there is a real regressionperformance-testingto collect the measurements behind the advice
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take foryourhealth111-pixel/providing-performance-optimization-advice from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.