perf-diagnose

Diagnose client-side performance issues in the Kolu UI using Chrome DevTools MCP measurements.

47|9|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/juspay/kolu --skill perf-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-diagnose
Source: https://github.com/juspay/kolu/tree/main/.apm/skills/perf-diagnose
Command: npx skills add https://github.com/juspay/kolu --skill perf-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and triage client-side performance issues in the Kolu UI, focusing on memory leaks, high GPU usage, and slow interactions using measurement data from Chrome DevTools MCP and the built-in Diagnostic info dialog.

Core Features & Use Cases

  • Grounded measurement-driven analysis with per-terminal lifecycle insights.
  • Uses Debug → Diagnostic info dialog and heap-snapshot analyzers to identify memory and rendering leaks.
  • Master tracking and runbook approach for reproducibility in production issues.

Quick Start

Open the Kolu Diagnostic panel and initiate a performance run to collect measurements and begin analysis.

Frequently Asked Questions about perf-diagnose

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

FAQPage Schema
How do I diagnose memory leaks in a WebGL UI using Chrome DevTools heap snapshots?

Diagnose memory leaks by collecting Chrome DevTools MCP measurement data and generating heap snapshots. Analyze retention paths to identify holding references and validate remediation steps for rendering bottlenecks in the UI.

What is the best way to identify high GPU usage and slow interactions in a multi-terminal workload?

Analyze high GPU usage and slow interactions by tracing per-terminal WebGL lifecycles and accessing built-in diagnostic data. This evidence-based measurement approach isolates rendering bottlenecks across multi-terminal workloads.

How do I trace retention paths to validate memory leak fixes in a web application?

Trace retention paths by generating heap snapshots and analyzing collected measurement data. This validates whether memory leak fixes successfully release holding references and resolves per-terminal lifecycle issues.

Does this diagnostic approach work for per-terminal performance issues in production environments?

Yes, this diagnostic approach applies to per-terminal performance issues in production. It uses a master tracking and runbook method with the built-in Diagnostic info dialog to ensure reproducibility for production issues.

How do I collect live measurements to triage client-side performance issues?

Collect live measurements by opening the diagnostic panel and initiating a performance run. This gathers data from Chrome DevTools MCP and the built-in diagnostic info dialog to triage client-side performance issues.