browser-tab-resource-investigation

Profile macOS browser processes and enumerate tabs to identify resource-heavy tabs.

9|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/DavidTeju/shared-skills --skill browser-tab-resource-investigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-tab-resource-investigation
Source: https://github.com/DavidTeju/shared-skills/tree/main/skills/browser-tab-resource-investigation
Command: npx skills add https://github.com/DavidTeju/shared-skills --skill browser-tab-resource-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Programmatically identify and manage resource-heavy browser tabs on macOS using ps, AppleScript, and forensic techniques. Use when user says: (1) "my browser is using a lot of CPU/memory", (2) "which tab is causing my Mac to run slow/hot", (3) "Edge/Chrome/Safari is hogging resources", (4) "find the runaway tab", (5) "there's a tab making my computer slow", (6) "close duplicate tabs", (7) "clean up my browser tabs". Covers process investigation, AppleScript tab enumeration, forensic identification (kill → observe → identify), and bulk tab operations.

Core Features & Use Cases

  • Identify high-resource browser processes by CPU and memory usage
  • Enumerate per-tab URLs and titles across Edge/Chrome/Safari using AppleScript
  • Forensic kill-and-observe technique to pinpoint culprit tab and bulk cleanup (close duplicates, old tabs, and redirect tabs)
  • Decode redirect URLs and rebrowse to real destinations for cleanup

Quick Start

Identify high-resource browser processes, enumerate open tabs with AppleScript, then use the kill-and-observe technique to identify the culprit tab and perform bulk cleanup as needed.

Frequently Asked Questions about browser-tab-resource-investigation

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

FAQPage Schema
How do I find which browser tab is using high CPU or memory on macOS?

Identify resource-heavy browser tabs on macOS by profiling active processes with ps and enumerating per-tab URLs and titles across Chrome, Edge, and Safari via AppleScript to pinpoint the culprit.

How does the kill-and-observe technique identify a runaway browser tab?

The kill-and-observe technique identifies a runaway browser tab by terminating high-resource browser processes and observing which tab disappears, forensically matching the process to the specific URL causing slowdowns.

Can I use AppleScript to close duplicate tabs and clean up Chrome or Edge?

Yes, AppleScript can enumerate open tabs across Chrome, Edge, and Safari to perform bulk tab operations, including closing duplicates, removing old tabs, and decoding redirect URLs for cleanup.

Does this tab identification method work across Safari, Chrome, and Edge on Mac?

Yes, this tab identification method works across Safari, Chrome, and Edge on macOS, using AppleScript access to enumerate tabs and identify processes causing high CPU or memory usage across different browser workflows.

What do I need to programmatically investigate browser tabs on macOS?

To programmatically investigate browser tabs on macOS, you need AppleScript access enabled, utilizing process profiling tools like ps and AppleScript enumeration to manage high CPU or memory usage across browsers.