Playwright vs browser-caching
Playwright and browser-caching are both browser automation skills. browser-caching scores higher (84 vs 41 out of 100). browser-caching has more GitHub stars (75k), and browser-caching was updated more recently (16 days ago). The table compares them side by side.
| Playwright | browser-caching | |
|---|---|---|
| Score | 41 / 100 | 84 / 100 |
| What it does | Use when running E2E checks or debugging the web app with Playwright MCP, especially when you need to (1) ensure the demo user exists with superadmin permissions via demo.sql, and (2) login via /demoLogin on localhost. | 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: oxedom | Community: thedaviddias |
| Grades | Maintenance D, Licence F, Quality C | 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 | 34 | 74,518 |
| Last commit | 2 Feb 2026 | 6 Oct 2026 |
| Licence | None found | MIT |
| Listed since | 19 Oct 2026 | 20 Oct 2026 |
| Install Playwright | Install browser-caching |
Questions
Is Playwright or browser-caching more popular?
browser-caching has more GitHub stars: 74,518.
Can I use Playwright 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.