browser-console vs remove-unused-includes
browser-console and remove-unused-includes are both browser automation skills. remove-unused-includes scores higher (84 vs 72 out of 100). remove-unused-includes has more GitHub stars (25k), and remove-unused-includes was updated more recently (yesterday). The table compares them side by side.
| browser-console | remove-unused-includes | |
|---|---|---|
| Score | 72 / 100 | 84 / 100 |
| What it does | Diagnose browser console errors and uncaught JavaScript exceptions without dumping routine logs. | Look through a given folder to find and safely remove unused includes specifically for Clang-compiled code (using clang-include-cleaner), verifying that referencing targets compile. |
| Publisher | Community: BetterWright | Community: chromium |
| Grades | Maintenance A, Licence A, Quality B | Maintenance A, Licence A, Quality A |
| npm downloads a week | Not on npm | Not on npm |
| Runs | Skill | Skill |
| Works with | Claude Code, Claude apps | Claude Code, Claude apps |
| GitHub stars | 340 | 25,092 |
| Last commit | 19 Oct 2026 | 20 Oct 2026 |
| Licence | MIT | BSD-3-Clause |
| Listed since | 20 Oct 2026 | 20 Oct 2026 |
| Install browser-console | Install remove-unused-includes |
Questions
Is browser-console or remove-unused-includes more popular?
remove-unused-includes has more GitHub stars: 25,092.
Can I use browser-console and remove-unused-includes together?
Yes. AI assistants can load several skills at once. Install both and the assistant picks the right one for each task.