Ext Ops Panel
Open dashboard
Comparison

breezeware-dev-plugins vs Chrome Extension Builder

breezeware-dev-plugins is a plugin bundle for AI coding tools published by Breezeware-OS. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Chrome Extension Builder is a plugin bundle for AI coding tools published by harry-harish. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-23. 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
Marketplacebreezeware-dev-pluginsChrome Extension Builder
Claude Code: claude-plugins-community Listed
Version: 44c96c2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.4.0
Forks (GitHub): 0
Stars (GitHub): 1
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

breezeware-dev-plugins vs Chrome Extension Builder
Factbreezeware-dev-pluginsChrome Extension Builder
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
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
Hooks it runs (differs)Not published3
Parts of the bundle (differs)Not published19
Licence (differs)Not statedMIT
Repository (differs)github.com/breezeware-os/breezeware-claude-pluginsgithub.com/harry-harish/chrome-extension-builder
Changes in the last 7 days00
First seen2026-10-112026-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

breezeware-dev-plugins

In its own words, on Claude Code: claude-plugins-community:

True Claude Code plugins for Breezeware development — auto-detecting, hook-powered, with skills and code review.

Chrome Extension Builder

In its own words, on Claude Code: claude-plugins-community:

Use when scaffolding, validating, testing, or publishing a Manifest V3 Chrome/Edge/Firefox extension. Builds end-to-end with WXT, Plasmo, or CRXJS — service-worker dispatcher, typed message passing, strict CSP, _locales/ i18n, Playwright smoke harness, Chrome Web Store submission prep.

How to run each

breezeware-dev-plugins As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install breezeware-dev-plugins@claude-community

Chrome Extension Builder As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install chrome-extension-builder@claude-community

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: breezeware-dev-plugins · What it can do: Chrome Extension Builder · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-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