Ext Ops Panel
Open dashboard
Comparison

browser-test vs Cursor Team Kit

browser-test is a plugin bundle for AI coding tools published by Brian Dueck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Cursor Team Kit is a plugin bundle for AI coding tools published by Eric Zakariasson. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacebrowser-testCursor Team Kit
Community marketplace autodesk/claude-browser-test-skills Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen
Not listed
Cursor: cursor/plugins Not listed Listed
Version: 1.2.0
Forks (GitHub): 1 107
Stars (GitHub): 11 352
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

browser-test vs Cursor Team Kit
Factbrowser-testCursor Team Kit
Marketplaces that list it11
Stars (GitHub) (differs)7 (worse)11 352 (better)
Forks (GitHub) (differs)0 (worse)1 107 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)422
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/autodesk/claude-browser-test-skillsgithub.com/cursor/plugins
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

browser-test

In its own words, on Community GitHub marketplaces:

E2E browser test pipeline for Claude Code: author, refine, compile, and run Playwright tests using browser automation

Cursor Team Kit

In its own words, on Cursor: cursor/plugins:

Internal team workflows for CI, code review, shipping, local automation, and verification.

How to run each

browser-test As a Claude Code plugin

Claude Code
/plugin marketplace add autodesk/claude-browser-test-skills
/plugin install browser-test@browser-test-skills

Cursor Team Kit

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: browser-test · What it can do: Cursor Team Kit · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built