performance-optimization SKILL.md skillA

performance-optimization from khaledsaeed18/dotclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add khaledsaeed18/dotclaude/performance-optimization@git:20260921.4ccfb75

Pins git:20260921.4ccfb75 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

khaledsaeed18/dotclaude

Path

.claude-plugin/plugins/engineering/skills/performance-optimization/SKILL.md

Versions recorded

2

Latest version

git:20260921.4ccfb75, committed Sep 21, 2026

First version recorded

Jul 4, 2026

Size

5,223 bytes

Repository stars

5

License

MIT

Fix a performance problem by profiling first, making one targeted change, and verifying both the speedup and that correctness held. Use when a feature is measurably slow, a page or API exceeds its budget, or a query takes too long. Do not use to pre-optimize code that has not been measured.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

Profile first. Every performance intuition is wrong until the profiler confirms it. The code that looks slow is rarely the bottleneck; the bottleneck is almost always somewhere the code looks unremarkable. An optimization without a measurement is a guess. A guess that happens to speed things up does not mean you found the right thing.

## The one rule

**No change before you have a baseline measurement and a profiled bottleneck.** If you cannot name the specific file, function, and line where the most time or memory is spent - with numbers - you are still in the investigation phase.

## Step 1: Establish the baseline

Define what "slow" means in terms the problem must satisfy:

- What is the current measured value? (response time, frame rate, memory usage, query duration, build time)
- What is the target? (a budget from a spec, a regression from a previous version, a user-reported threshold)
- Can the scenario be reproduced reliably? If not, instrument first and gather data before optimizing.

Run the scenario and record the baseline:

```bash
# For Node.js / server-side
node --prof app.js           # then: node --prof-process isolate-*.log
# or: clinic flame -- node app.js
…

Read the whole file at its exact version.

How to install

mdr add khaledsaeed18/dotclaude/performance-optimization@sha256:b2677188c40a9cd2

[![mdr](https://markdownregistry.com/badge/art_hnjvcjojipmwa772.svg)](https://markdownregistry.com/a/art_hnjvcjojipmwa772)

Versions

The registry has recorded 2 versions of this file, between Jul 4, 2026 and Sep 21, 2026, about one every 80 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_hnjvcjojipmwa772
GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/performance-optimization
GET https://markdownregistry.com/api/v1/blob/b2677188c40a9cd215b71cdeec0af1929f08c7922efe9587774bc4828427d637

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from khaledsaeed18/dotclaude

Every file in khaledsaeed18/dotclaude

Other files named performance-optimization

Browse by kind, by grade A, or by owner.