Use browser-debugger-cli when an agent needs to inspect a live Chromium tab by pulling DOM snapshots, console errors, network activity, cookies, or raw CDP output during a failing browser task. Invoke it instead of using the browser normally when the job is diagnosis and telemetry collection, not routine browsing or end-to-end automation. The scope boundary is tight and skill-shaped: this is a live-session debugging workflow around Chrome DevTools Protocol, not a generic browser platform, SDK, or framework listing.