analyze

Parse performance trace data to identify bottlenecks and resource utilization.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SteeZyT33/perf-lab-plugin --skill analyze-steezyt33
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/SteeZyT33/perf-lab-plugin/tree/main/skills/analyze
Command: npx skills add https://github.com/SteeZyT33/perf-lab-plugin --skill analyze-steezyt33

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps pinpoint performance bottlenecks in code by analyzing trace data, identifying resource utilization issues, and suggesting optimization opportunities.

Core Features & Use Cases

  • Trace Data Analysis: Parses output from performance traces to understand resource usage.
  • Bottleneck Identification: Determines the primary resource limiting performance.
  • Optimization Suggestions: Provides actionable insights into where to focus optimization efforts.
  • Use Case: After a performance regression, use this Skill to analyze the trace output, identify the new bottleneck, and understand how it differs from previous analyses.

Quick Start

Analyze the performance trace data by running the analyze skill.

Frequently Asked Questions about analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify performance bottlenecks from trace data?

To identify performance bottlenecks from trace data, parse the trace output to evaluate resource utilization and pinpoint binding constraints. This process highlights critical cycle utilization gaps and idle stretches that limit software performance.

What causes low cycle utilization and idle stretches during performance profiling?

Low cycle utilization and idle stretches during performance profiling are caused by resource underutilization and binding constraints. Analyzing trace data helps identify these limiting factors within your code execution.

How do I compare current trace analysis results against previous performance runs?

Compare current trace analysis results against previous performance runs by parsing new trace output to identify binding constraints. This highlights how current resource utilization and bottlenecks differ from past analyses.

Can I use this to find optimization opportunities after a performance regression?

Yes, you can find optimization opportunities after a performance regression by analyzing trace output. The analysis identifies the new bottleneck, assesses resource underutilization, and suggests where to focus optimization efforts.

Does this trace analysis approach work for software profiling without external dependencies?

Yes, trace analysis works for software profiling without external dependencies. It parses performance trace output directly to determine resource utilization and identify the primary binding constraints limiting performance.