optimization

Diagnose and improve system performance through measurement, bottleneck attribution, and prioritized fixes.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/basedgod55hjl/vsbrax --skill optimization-basedgod55hjl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: optimization
Source: https://github.com/basedgod55hjl/vsbrax/tree/main/agent/.abrasax/skills/optimization
Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill optimization-basedgod55hjl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often optimize code blindly, wasting effort on micro-tweaks while missing the real bottlenecks. This Skill enforces a disciplined, evidence-based optimization workflow so every change targets the metrics that actually matter. ## Core Features & Use Cases - Metric Definition & Baselines: Identify the right metrics (latency, throughput, memory, CPU, cost) and build repeatable benchmarks before changing code. - Bottleneck Attribution: Instrument the system with ad hoc inspection and logged measurements to trace where time and resources go across the full execution path. - Static Analysis & Prioritization: Catch wrong asymptotic complexity, poor algorithm choices, and architectural inefficiencies, then apply macro-optimizations before micro-optimizations. - Use Case: A backend API has slow response times. Use this Skill to define a latency target, reproduce the baseline, profile the request path, discover an N+1 query pattern, fix it, and verify the improvement with before/after measurements. ## Quick Start Use the optimization skill to find and fix the performance bottleneck in my API endpoint, starting with baseline latency measurements.

Frequently Asked Questions about optimization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize slow code performance?▼

Start by defining the exact metric that matters, such as latency or memory, and measure a repeatable baseline. Then instrument the system to attribute costs, fix the largest bottleneck first, and re-measure to confirm the improvement.

How to find performance bottlenecks in an application?▼

Combine ad hoc inspection for quick debugging with logged measurements for later analysis. Attribute work across the full execution path rather than only the obviously slow component, so the data explains where the cost actually comes from.

Should I profile before optimizing my code?▼

Not always. Static analysis often reveals issues like wrong asymptotic complexity, poor data structures, or repeated work without any profiling. Check algorithmic and architectural soundness first, then profile to confirm runtime behavior.

What is the difference between macro and micro optimization?▼

Macro-optimization removes whole classes of work through better architecture, caching, batching, or algorithm choice. Micro-optimization makes existing work slightly cheaper and only matters after major inefficiencies are resolved.

When should I stop optimizing a system?▼

Stop when the target metric is met or when further gains are not worth the tradeoffs. Watch for regressions in correctness, reliability, maintainability, and security, and never claim an optimization without before-and-after evidence.