accessible-tooltips vs remove-unused-includes
accessible-tooltips and remove-unused-includes are both browser automation skills. accessible-tooltips scores higher (87 vs 87 out of 100). accessible-tooltips has more GitHub stars (75k), and remove-unused-includes was updated more recently (3 days ago). The table compares them side by side.
| accessible-tooltips | remove-unused-includes | |
|---|---|---|
| Score | 87 / 100 | 87 / 100 |
| What it does | Use when reviewing templates, rendered HTML, or shared components related to Create accessible tooltips. Validate the final browser-facing markup, not just the source framework abstraction. | 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: thedaviddias | Community: chromium |
| Grades | Maintenance A, Licence A, Quality A | 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 | 74,518 | 25,092 |
| Last commit | 6 Oct 2026 | 20 Oct 2026 |
| Licence | MIT | BSD-3-Clause |
| Listed since | 20 Oct 2026 | 20 Oct 2026 |
| Install accessible-tooltips | Install remove-unused-includes |
Questions
Is accessible-tooltips or remove-unused-includes more popular?
accessible-tooltips has more GitHub stars: 74,518.
Can I use accessible-tooltips 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.