profile-optimizer

Solid

Analyzes React DevTools Profiler exports, Chrome DevTools Performance traces, and Chrome heap snapshots / heap-timelines / heap-profiles. Identifies the highest-impact bottlenecks (long tasks, expensive renders, layout thrash, wasted memoisation, blocking scripts, retained memory, leaks) and proposes concrete code fixes ranked by measured impact. Auto-detects the input format (React `.json` profile, Chrome trace `.json` / `.cpuprofile`, or `.heapsnapshot` / `.heaptimeline` / `.heapprofile`). Iterates via the `/confidence` skill — if root-cause certainty is below 90%, it digs deeper before recommending a fix. Use when handed a profile file, asked "why is this slow?", "why is memory growing?", or asked to optimise a hot path with evidence. Triggers on "analyze profile", "react profiler", "chrome performance", "optimize from profile", "profile this", "why is this slow", "memory leak", "heap snapshot", "/profile-optimizer".

Data & Documents 8 stars 2 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Profile Optimizer Turn a profile file into a ranked, evidence-backed optimisation plan. > **Index file.** Detailed analysis rules, optimisation patterns, and report > templates live under `rules/`, `references/`, and `templates/`. Load only > what the current phase needs — the body of `SKILL.md` is a thin orchestrator. --- ## Inputs The user passes one or more profile files. Accept any of: | Format | Extension | Detection signal | | -------------------------- | ------------------------ | ----------------------------------------------------------------- | | React DevTools Profiler | `.json` (often `.reactprofile`) | Top-level keys include `dataForRoots` and `rendererID` / `version` | | Chrome Performance trace | `.json` / `.json.gz` | Top-level `traceEvents` array (or NDJSON with `ph`, `ts`, `cat`) | | Chrome CPU profile (legacy)| `.cpuprofile` | Top-level `nodes`, `samples`, `timeDeltas` | | Chrome heap snapshot | `.heapsnapshot` | Top-level `snapshot.meta.node_fields` + `nodes`/`edges`/`strings` | | Chrome heap timeline | `.heaptimeline` | Heap snapshot shape + `samples` array | | Chrome heap profile (sampled allocations) | `.heapprofile` | Top-level `head` + `samples` (V8 sampling-allocation profile) | If the file is gzipped, decompress with `gunzip -k` before parsing. If mu...

Details

Author: mthines
Repository: mthines/agent-skills
Created: 3 months ago
Last Updated: 2 days ago
Language: TypeScript
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-*.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating user timing marks.

23 Updated today

chapmanjw

Data & Documents Solid

upwork-profile-optimizer

Audit and improve an Upwork freelancer profile. Use when the user pastes their profile (title, overview, portfolio list, skills, stats) and wants it scored and fixed, or asks why they aren't getting invitations or search visibility. Triggers include "review my Upwork profile", "why am I not getting invites", "improve my profile", "profile title help", "optimize my overview". Returns a prioritized fix list, biggest lever first. Companion to upwork-proposal-writer (the proposal earns the profile visit; the profile closes it).

95 Updated 2 weeks ago

abullaisi

Data & Documents Featured

happier-profile-and-optimize

The method for profiling and optimizing anything whose success is a measured cost — frame the phase and metric, choose an instrument that can actually see the cost, label the waste, falsify the hypothesis with a cheap control before building a fix, and prove the result without over-claiming. Covers app/device and server/database work. Use when work is about slowness, jank, startup/open time, blocked JS, hangs, memory, render churn, a slow query, or a claimed speedup. It does not carry the write-time gotchas for UI code — those live in `apps/ui/AGENTS.md`.

1,495 Updated today

happier-dev