Analyze Firefox performance profiles using the profiler-cli CLI tool. Trigger when given a profiler.firefox.com or share.firefox.dev link, a local profile path, or when the user wants to investigate an issue in a Firefox profile. Always use this skill instead of WebFetch for Firefox profiler URLs; WebFetch only retrieves the profiler UI's HTML shell and cannot access profile data, whereas profiler-cli downloads and parses the actual profile into a local daemon that supports structured queries over stacks, markers, threads, and samples.
Non-shareable profile URL handling
Identifies non-shareable URL type
100%
100%
Explains local-storage limitation
100%
100%
No load attempt
100%
100%
No WebFetch attempt
100%
100%
Share button instruction
100%
100%
Correct shareable URL formats
100%
100%
Local file path alternative
100%
100%
Full profiler-cli analysis workflow
Guide run first
0%
100%
profiler-cli load (not WebFetch)
46%
100%
Glob used for case studies
0%
0%
Relevant case study selected
0%
0%
Thread selection performed
100%
100%
Sample analysis commands used
100%
100%
Marker analysis performed
100%
100%
profiler-cli stop called
0%
100%
Results interpreted (not just printed)
100%
100%
Root cause identified
100%
100%
Extension hang root-cause analysis
Guide run before analysis
0%
100%
profiler-cli load (not WebFetch)
0%
100%
Glob used for references
0%
0%
Appropriate case study identified
0%
0%
Thread selection used
0%
100%
Top-down or bottom-up sample tree used
0%
100%
profiler-cli stop called
0%
100%
Commands executed and interpreted
100%
100%
Root cause identified
100%
100%
Next steps suggested
100%
100%
31bc07f
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.