performance-analysis
/performance-analysis
Measure before optimizing. Profile startup time, latency, throughput, memory, or bundle size, find the dominant cost with evidence, and propose the smallest change that moves the number. Use for "slow", "takes N seconds", "high CPU or memory", and performance regressions.
- Author
- autohandai ↗
- Repository
- code-cli ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Measure before optimizing. Profile startup time, latency, throughput, memory, or bundle size, find the dominant cost with evidence, and propose the smallest change that moves the number. Use for "slow", "takes N seconds", "high CPU or memory", and performance regressions.
Triggers from the description
Original author description
Measure before optimizing. Profile startup time, latency, throughput, memory, or bundle size, find the dominant cost with evidence, and propose the smallest change that moves the number. Use for "slow", "takes N seconds", "high CPU or memory", and performance regressions.
How it works
- Establish the baseline
- Find the dominant cost
- Change one thing, then measure again
- Report
SKILL.md preview
--- name: performance-analysis description: Measure before optimizing. Profile startup time, latency, throughput, memory, or bundle size, find the dominant cost with evidence, and propose the smallest change that moves the number. Use for "slow", "takes N seconds", "high CPU or memory", and performance regressions. allowed-tools: read_file find_grep fff_find list_tree run_command git_log git_diff file_stats --- # Analyze performance with numbers Optimizing without a measurement changes the code without changing the outcome. Every step below produces a number you can show. ## Establish the baseline 1. Define the metric and the scenario exactly: what is slow, from which event to which, on what input size, on what machine. Ask if unclear. 2. Measure it three times with the tools the project already has (timers, `--profile` flags, `time`, `hyperfine`, language profilers, `--cpu-prof`, heap snapshots, bundle analyzers). Record median and spread. 3. Record the environment: load average, CPU count, disk free, network, concurrent processes. A loaded machine invalidates comparisons. ## Find the dominant cost - Break the total into phases with timestamps or a profiler; sort by time. - Distinguish blocking waits (network, disk, subprocess, locks, timeouts) from CPU work; the fix differs. - Look for the usual shapes: sequential awaits that could be parallel, work repeated per item that could be cached, unbounded scans that need a budget, startup work that could be lazy or deferred, N+1 calls, large payloads, synchronous I/O on the main thread, retries with long timeouts. - Check what scales with input size using two sizes and compare. ## Change one thing, then measure again - Pick the change with the best ratio of expected gain to risk. State the expected gain before making it. - Re-measure the same way. Report before and after with the spread. - Add a guard so it stays fixed: a timing assertion with a generous bound, a budget constant, or a test that the work is deferred or cached. ## Report Metric, scenario, baseline, cause with file:line, change, result, and what was not addressed. If the measurement showed the suspected cause was wrong, say so.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · autohandai/code-cli | 100 | Apache-2.0 |
| frankxai/claude-skills-library | 100 | MIT |
| dreamlab-ai/agentbox | 100 | AGPL-3.0 |
| 0xsarwagya/ontoly | 100 | AGPL-3.0 |
| rsmdt/the-startup | 90 | MIT |
Database snapshot: 13.11.2026 · package version 9f2470ebd243 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100performance-optimization
Measure, diagnose, and improve application, API, database, frontend, build, and infrastructure performance. Use when latency, throughput, memory, CPU, bundle size, startup time, or operating cost is a material concern. - 90performance-auditor
Profile and optimize applications - hot paths, N+1 queries, blocking I/O, caching, bundle size, memory, startup time. Use for /turbo, "why is it slow?", or pre-launch performance passes. - 100performance-profiling
Finds and fixes backend and application performance problems by measuring first - define the target metric, reproduce under realistic load, profile CPU, memory, I/O and locks, fix the biggest bottleneck, re-measure, and add a regression guard. Use when code or a service is slow,… - 100performance-optimization
Diagnoses and improves measured latency, throughput, memory, CPU, bundle, rendering, query, or resource performance by defining a target, profiling a representative workload, locating the bottleneck, making one change at a time, and comparing before/after evidence. Use for… - 100performance-tuning
Finds and fixes the dominant cost in a slow JVM service: baseline metric, profile (JFR/async-profiler, traces, GC, locks), one fix, re-measure. Use for high latency, low throughput, CPU/memory/GC pressure or leaks. A single slow query goes to sql-optimization. - 100performance-investigation
Diagnose a measured latency, memory, throughput, or resource regression and propose the smallest supported optimization. Use for performance questions; measure before tuning.