profile
Skill2 starsChanged 4 months agoMITView on GitHub
Profile a program to find where it actually spends time or memory — capture a CPU/heap profile under a realistic workload, read the hot paths, and point to the real bottleneck before optimizing. Use when the user says "profile this", "where does the time go", "find the hotspot", "why is this using so much memory", "capture a flamegraph", "which function is slow", or "find the bottleneck before I optimize".
30 other projects use a version of this.
Adopted by
Most recently taken up by
- DataDog/dd-trace-pytheir own version, first seen Nov 16, 2026
- rafaym1/scholarship-desktheir own version, first seen Nov 16, 2026
- baekenough/oh-my-customcodetheir own version, first seen Nov 14, 2026
- galiprandi/job-seekertheir own version, first seen Nov 14, 2026
- qbeka/jev-job-searchtheir own version, first seen Nov 12, 2026
- nockawa/NockMontheir own version, first seen Nov 8, 2026
Used with
Projects with it also use apply, status and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
rhowardstoneSkillapply
Research-backed job application workflow emphasizing relationship-building over mass applications
Also in 3 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 3 projects that use this
Microsoft AzureSkilldocs
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- FalkorDB/FalkorDB★ 11ksame name
- pytorch/executorch★ 5.2ksame name
- verl-project/verl-omni★ 1.5ksame name
- DataDog/dd-trace-py★ 655same name
- qbeka/jev-job-search★ 368same name
- nockawa/Typhon★ 253same name
- galiprandi/job-seeker★ 136same name
- the-void-ia/void-box★ 88same name
20 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- licenseSkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- squashSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Prefer a sampling profiler for realistic CPU cost (low overhead) and an allocation/heap profiler for memory.
- Distinctive: line 33
Always measure before optimizing — identify the hotspot from a profile rather than intuition.
- Distinctive: line 36
Read self vs. cumulative time (and retained vs.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Language, runtime & profiler signals
!grep -rilE "pprof|py-spy|cProfile|line_profiler|memory_profiler|clinic|0x|--prof|--inspect|perf|flamegraph|criterion|pytest-benchmark|scalene|austin" --include='*.*' package.json pyproject.toml go.mod Gemfile Cargo.toml Makefile 2>/dev/null | grep -vE 'node_modules|\.git|dist|build' | head -8
Instructions
Find where the code in $ARGUMENTS truly spends its time or memory by measuring, not guessing. Profiling locates the bottleneck; fixing it is the optimize skill's job and confirming the win is the benchmark skill's. Reuse whatever profiler already fits the project's language/runtime.
Method
- Pin down what and which resource. Decide CPU time vs. wall-clock (I/O-bound) vs. memory/allocations — they need different tools and lead to different fixes. Identify the smallest reproducible entrypoint that exhibits the problem.
- Profile under a realistic workload. A profile of a trivial or cold run is misleading — use representative input size, a warm cache/JIT where relevant, and enough iterations/duration that the hot code dominates the sample. For a server, profile while it's under load (drive it with the real path).
- Pick the profiler that fits:
- Node:
node --prof+--prof-process,--cpu-prof/--heap-prof, Clinic.js, or0xfor a flamegraph;--inspect+ DevTools for heap snapshots. - Python:
cProfile+snakeviz/pstatsfor CPU,py-spy/austinto sample a running process,line_profilerfor per-line,memory_profiler/scalene/tracemallocfor memory. - Go:
runtime/pprofornet/http/pprof, thengo tool pprof(-httpfor a flamegraph);go test -cpuprofile/-memprofile. - Native/other:
perf+ FlameGraph,valgrind --tool=callgrind, or the platform sampler. Prefer a sampling profiler for realistic CPU cost (low overhead) and an allocation/heap profiler for memory; note that instrumenting profilers can distort timings.
- Node:
- Read the profile for the real cost. Look at cumulative/total time and self time, and follow the flamegraph's widest frames. Distinguish a genuine hot leaf from a function that's merely on the path. For memory, separate live retained heap (leak/bloat) from transient allocation churn (GC pressure).
- Report the bottleneck, don't fix blindly. State the top few hotspots with their share of time/allocations, the workload used, and where the evidence points (CPU in a parser, GC from per-row allocation, a synchronous I/O stall, an N+1). Hand off the fix to
optimizeand re-measure withbenchmark— optimizing without a profile is guessing. - Clean up artifacts. Profiles, flamegraph SVGs, and
isolate-*.logfiles shouldn't be committed — add them to.gitignoreif they'll recur (see thegitignoreskill).
Rules
- Always measure before optimizing — identify the hotspot from a profile rather than intuition; report evidence, not a guess.
- Profile a realistic, warmed, sufficiently long workload; a cold or toy run misattributes cost.
- Match the tool to the resource: sampling profiler for CPU cost, heap/allocation profiler for memory, wall-clock for I/O-bound — and note when an instrumenting profiler is distorting timings.
- Read self vs. cumulative time (and retained vs. transient memory) so you blame the true hot code, not a frame merely on the path.
- End with the top hotspots and their share, the workload profiled, the suspected cause, and a handoff to
optimize/benchmark; don't commit profiler output.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

