Performance Profiler
borghei/Claude-Skills
Performance profiling for Node.js, Python, and Go: CPU flamegraphs, memory leak detection, bundle analysis, query optimization, and k6 load testing.
Systematic performance profiling for Node.js, Python, and Go applications.
Install Performance Profiler
$ npx skills add alirezarezvani/claude-skills --skill performance-profiler -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills performance-profiler --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/skills/performance-profiler .claude/skills/performance-profiler && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "performance-profiler" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skills/performance-profiler into .claude/skills/performance-profiler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-profiler", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skills/performance-profilerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-skills --skill performance-profiler -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills performance-profiler --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/skills/performance-profiler .agents/skills/performance-profiler && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "performance-profiler" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skills/performance-profiler into .agents/skills/performance-profiler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-profiler", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill performance-profiler -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills performance-profiler --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/skills/performance-profiler .cursor/skills/performance-profiler && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "performance-profiler" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skills/performance-profiler into .cursor/skills/performance-profiler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-profiler", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path engineering/skills/performance-profiler--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-skills --skill performance-profiler -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills performance-profiler --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/skills/performance-profiler .gemini/skills/performance-profiler && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "performance-profiler" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skills/performance-profiler into .gemini/skills/performance-profiler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-profiler", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-skills performance-profilerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-skills --skill performance-profiler -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/skills/performance-profiler .github/skills/performance-profiler && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "performance-profiler" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skills/performance-profiler into .github/skills/performance-profiler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-profiler", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill performance-profiler -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills performance-profiler --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/skills/performance-profiler .opencode/skills/performance-profiler && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "performance-profiler" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skills/performance-profiler into .opencode/skills/performance-profiler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-profiler", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
performance-profiler- GitHub stars
- 28k
- Token cost
- ~684 tokens
- SKILL.md length
- 180 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Systematic performance profiling for Node.js, Python, and Go applications.
- Investigating a slow endpoint
- SKILL.md covers Overview, Core Capabilities, When to Use and Quick Start, plus 3 more sections
- Runs Python scripts from its folder; calls python3
- Planning a performance budget
What it does
Performance Profiler is an agent skill from alirezarezvani/claude-skills. Systematic performance profiling for Node.js, Python, and Go applications. Identifies CPU, memory, and I/O bottlenecks, generates flamegraphs, analyzes bundle sizes, optimizes database queries, runs load tests with k6 and Artillery. Always measures before and after. Use when investigating a slow endpoint, planning a performance budget, or hunting a memory leak in production.
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/optimization-playbook.md`, `references/profiling-recipes.md` and `scripts/performance_profiler.py`).
It sits in Development, covering Performance optimization, Load testing and Web performance. It works with Node.js and Python. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- Investigating a slow endpoint
- Planning a performance budget
- Hunting a memory leak in production
Example prompts
- “/performance-profiler”
Requirements
- Python 3
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Performance Profiler loads about 684 tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 180 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 180 words, ~684 tokens.
Download SKILL.mdSave it as
.claude/skills/performance-profiler/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- performance-profiler
- description
- Systematic performance profiling for Node.js, Python, and Go applications. Identifies CPU, memory, and I/O bottlenecks, generates flamegraphs, analyzes bundle sizes, optimizes database queries, runs load tests with k6 and Artillery. Always measures before and after. Use when investigating a slow endpoint, planning a performance budget, or hunting a memory leak in production.
Performance Profiler
Tier: POWERFUL
Category: Engineering
Domain: Performance Engineering
Overview
Systematic performance profiling for Node.js, Python, and Go applications. Identifies CPU, memory, and I/O bottlenecks; generates flamegraphs; analyzes bundle sizes; optimizes database queries; detects memory leaks; and runs load tests with k6 and Artillery. Always measures before and after.
Core Capabilities
- CPU profiling — flamegraphs for Node.js, py-spy for Python, pprof for Go
- Memory profiling — heap snapshots, leak detection, GC pressure
- Bundle analysis — webpack-bundle-analyzer, Next.js bundle analyzer
- Database optimization — EXPLAIN ANALYZE, slow query log, N+1 detection
- Load testing — k6 scripts, Artillery scenarios, ramp-up patterns
- Before/after measurement — establish baseline, profile, optimize, verify
When to Use
- App is slow and you don't know where the bottleneck is
- P99 latency exceeds SLA before a release
- Memory usage grows over time (suspected leak)
- Bundle size increased after adding dependencies
- Preparing for a traffic spike (load test before launch)
- Database queries taking >100ms
Quick Start
# Analyze a project for performance risk indicators
python3 scripts/performance_profiler.py /path/to/project
# JSON output for CI integration
python3 scripts/performance_profiler.py /path/to/project --json
# Custom large-file threshold
python3 scripts/performance_profiler.py /path/to/project --large-file-threshold-kb 256Golden Rule: Measure First
# Establish baseline BEFORE any optimization
# Record: P50, P95, P99 latency | RPS | error rate | memory usage
# Wrong: "I think the N+1 query is slow, let me fix it"
# Right: Profile → confirm bottleneck → fix → measure again → verify improvementNode.js Profiling
→ See references/profiling-recipes.md for details
References
- references/profiling-recipes.md — Node.js/Python/Go profiling commands, flamegraph generation, heap snapshots
- references/optimization-playbook.md — before/after measurement template, quick-win optimization checklist (DB/Node/bundle/API), common pitfalls, best practices
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in engineering/skills/performance-profiler of alirezarezvani/claude-skills.
- SKILL.md
- references/optimization-playbook.md
- references/profiling-recipes.md
- scripts/performance_profiler.py
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Performance Profiler next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Performance Profiler this skillalirezarezvani/claude-skills | 28k | — | ~684 | Automated safety check: Pass | MIT | |
| Performance Profilerborghei/Claude-Skills | 874 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Afrexai Performance EngineeringLeoYeAI/openclaw-master-skills | 2.2k | — | ~7.1k | Automated safety check: Pass | MIT | |
| Performanceaiskillstore/marketplace | 430 | 1 repos | ~2.6k | Automated safety check: Pass | None | |
| Phy Memory Leak DetectorLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.3k | Automated safety check: Pass | Apache-2.0 | |
| Electron DevTools Trace Analysiskeybase/client | 9.3k | — | ~809 | Automated safety check: Pass | BSD-3-Clause |
Similar skills
Afrexai Performance Engineering
LeoYeAI/openclaw-master-skills
Complete performance engineering system — profiling, optimization, load testing, capacity planning, and performance culture.
Performance
aiskillstore/marketplace
Comprehensive performance specialist covering analysis, optimization, load testing, and framework-specific performance.
Phy Memory Leak Detector
LeoYeAI/openclaw-master-skills
Static memory leak pattern scanner for Node.js, Python, Go, and Java.
Electron DevTools Trace Analysis
keybase/client
Analyzes Chrome or Electron DevTools Performance trace exports with Python scripts to find where render time actually goes, without opening DevTools.
Renderdoc GPU Debug
rudybear/renderdoc-skill
GPU frame debugging with RenderDoc via rdc-cli. An agent skill from rudybear/renderdoc-skill.
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Performance Profiler
What does Performance Profiler do?
Systematic performance profiling for Node.js, Python, and Go applications. Performance Profiler is an agent skill from alirezarezvani/claude-skills.js, Python, and Go applications.
When should I use Performance Profiler?
Performance Profiler fits situations like: investigating a slow endpoint; planning a performance budget; hunting a memory leak in production.
How do I install Performance Profiler in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill performance-profiler -a claude-code`. Or copy the skill folder (engineering/skills/performance-profiler in alirezarezvani/claude-skills) into .claude/skills/performance-profiler in your project. Claude Code loads it when a task matches its description.
How do I install Performance Profiler in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill performance-profiler -a codex`. Or copy the skill folder (engineering/skills/performance-profiler in alirezarezvani/claude-skills) into .agents/skills/performance-profiler in your project. Codex loads it when a task matches its description.
Can I use Performance Profiler in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill performance-profiler -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/performance-profiler, .gemini/skills/performance-profiler, .github/skills/performance-profiler and .opencode/skills/performance-profiler in your project.
What does Performance Profiler need to run?
Going by SKILL.md and its folder, Performance Profiler needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3; Node.js.
Does Performance Profiler access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Performance Profiler safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Performance Profiler use?
Performance Profiler is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Performance Profiler use?
About 684 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.7k tokens, read only when the agent opens those files.
What are the alternatives to Performance Profiler?
Skills that share tags, products or a category with Performance Profiler: Performance Profiler (borghei/Claude-Skills, 874 stars), Afrexai Performance Engineering (LeoYeAI/openclaw-master-skills, 2.2k stars), Performance (aiskillstore/marketplace, 430 stars) and Phy Memory Leak Detector (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Performance Profiler?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,788 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.