analyze-profile

Analyze Firefox Profiler captures and generate structured findings reports.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill analyze-profile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-profile
Source: https://github.com/alastor0325/fx-bug-toolkit/tree/main/skills/analyze-profile
Command: npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill analyze-profile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes Firefox Profiler captures and converts raw profiling data into a structured findings report that supports bug triage, bug-start, and investigation workflows.

Core Features & Use Cases

  • Profiler analysis: loads share.firefox.dev or profiler.firefox.com/public links and extracts performance hotspots, thread activity, and demux issues.
  • Report generation: produces a structured, consumable findings report that can be pasted into bug reports or investigation files.
  • Scope and guidance: enforces that callers pass a valid profiler URL and guides downstream skills to avoid direct profiler-cli invocations.

Quick Start

Invoke the skill with a Firefox Profiler URL to generate a structured findings report.

Frequently Asked Questions about analyze-profile

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

FAQPage Schema
How do I analyze a Firefox Profiler capture for bug triage?▼

To analyze a Firefox Profiler capture, provide a share.firefox.dev or profiler.firefox.com/public link to generate a structured findings report for bug triage workflows. The skill extracts performance hotspots and thread activity automatically.

What is the best way to turn profiler captures into actionable findings?▼

The best way to turn profiler captures into actionable findings is using an automated analysis skill that processes profiler URLs and outputs a structured report. It extracts performance hotspots, thread activity, and demux issues for direct pasting into bug reports.

Do I need profiler-cli installed to analyze Firefox Profiler links?▼

Yes, you need profiler-cli installed on your PATH to analyze Firefox Profiler links. You can install it via the /init command, and a functioning Firefox-enabled environment is also required for the analysis workflow.

Can I use a Firefox Profiler URL directly to generate a bug report?▼

Yes, you can use a Firefox Profiler URL directly to generate a bug report. The skill accepts share.firefox.dev or profiler.firefox.com/public links and produces a consumable findings report that can be pasted directly into bug reports or investigation files.

What limitations exist when analyzing Firefox Profiler captures?▼

A key limitation is that valid profiler URLs are strictly enforced, and the environment requires profiler-cli on PATH plus a functioning Firefox setup. Additionally, downstream skills are guided to avoid direct profiler-cli invocations.