verify vs browser-caching
verify and browser-caching are both browser automation skills. browser-caching scores higher (84 vs 69 out of 100). browser-caching has more GitHub stars (75k), and verify was updated more recently (2 days ago). The table compares them side by side.
| verify | browser-caching | |
|---|---|---|
| Score | 69 / 100 | 84 / 100 |
| What it does | Verify UI changes in microlink/www by driving the Gatsby dev server with agent-browser. | Use when auditing slow page loads, heavy assets, or rendering delays related to Enable browser caching. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes. |
| Publisher | Community: microlinkhq | Community: thedaviddias |
| 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 | 142 | 74,518 |
| Last commit | 20 Oct 2026 | 6 Oct 2026 |
| Licence | MIT | MIT |
| Listed since | 19 Oct 2026 | 20 Oct 2026 |
| Install verify | Install browser-caching |
Questions
Is verify or browser-caching more popular?
browser-caching has more GitHub stars: 74,518.
Can I use verify and browser-caching together?
Yes. AI assistants can load several skills at once. Install both and the assistant picks the right one for each task.