cpu-profile-analysis Skill
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 us Published by microsoft in vscode.
What is cpu-profile-analysis Skill?
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 us Published by microsoft in vscode. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Data analysis
- Browser automation use cases
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use cpu-profile-analysis Skill
- Use it for browser automation.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode
- Skill file: .github/skills/cpu-profile-analysis/SKILL.md
What it does
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 us
Skill instructions
Analyze Performance Profiles Analyze .cpuprofile files (V8 sampling profiler) and DevTools trace files (Trace-.json, Chrome Trace Event Format) to find performance bottlenecks, compare code paths, and understand timing. When to Use - User provides a .cpuprofile or Trace-.json file and wants to understand performance - Investigating why one code path is slower than another - Finding what functions consume the most time - Comparing "before/after" or "old/new" implementations in a single profile - Investigating layout thrashing, long tasks, or rendering bottlenecks (trace files) - Analyzing VS Code user timing marks like code/didResolveTextFileEditorModel (trace files) - Understanding multi-process behavior (Browser, Renderer, GPU processes in trace files) Detecting File Type - .cpuprofile: Top-level JSON with nodes, samples, timeDeltas keys. Created by the VS Code profiler. - Trace-.json: Top-level JSON with traceEvents array (and optional metadata). Created by Chrome/Electron DevTools (
Explore related resources
Frequently asked questions
What is cpu-profile-analysis?
cpu-profile-analysis is a open-source AI agent skill with Copy skill directory. Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json).
Who is cpu-profile-analysis best for?
cpu-profile-analysis is best for reusing agent instructions, scripts, and references, browser automation workflows, data analysis workflows.
How do I install cpu-profile-analysis?
Install or run cpu-profile-analysis using Copy skill directory. Check cpu-profile-analysis for the latest setup command.
Is cpu-profile-analysis actively maintained?
cpu-profile-analysis may need a closer maintenance check before production use.
Auto-fetched from GitHub.
