AI Plugin Indexshaft-assertions vs remove-unused-includes
shaft-assertions and remove-unused-includes are both browser automation skills. remove-unused-includes scores higher (87 vs 68 out of 100). remove-unused-includes has more GitHub stars (25k), and shaft-assertions was updated more recently (3 days ago). The table compares them side by side.
| shaft-assertions | remove-unused-includes | |
|---|---|---|
| Score | 68 / 100 | 87 / 100 |
| What it does | Use when selecting or repairing SHAFT hard assertions, soft verifications, browser or element oracles, API checks, object checks, or failure messages. | 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: ShaftHQ | 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 | 416 | 25,092 |
| Last commit | 20 Oct 2026 | 20 Oct 2026 |
| Licence | MIT | BSD-3-Clause |
| Listed since | 19 Oct 2026 | 20 Oct 2026 |
| Install shaft-assertions | Install remove-unused-includes |
Questions
Is shaft-assertions or remove-unused-includes more popular?
remove-unused-includes has more GitHub stars: 25,092.
Can I use shaft-assertions 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.