Ext Ops Panel
Open dashboard
Comparison

alloydb vs pok-dex

alloydb is a plugin bundle for AI coding tools published by gemini-cli-extensions. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). pok-dex is a plugin bundle for AI coding tools published by SNLabat. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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
Marketplacealloydbpok-dex
Claude Code: claude-plugins-official Listed
Version: 0.2.0
Forks (GitHub): 6
Stars (GitHub): 24
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 6
Stars (GitHub): 24
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

alloydb vs pok-dex
Factalloydbpok-dex
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)42 (better)0 (worse)
Forks (GitHub) (differs)7 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@toolbox-sdk/server)Installs as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 1Not published
Parts of the bundle (differs)81
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/gemini-cli-extensions/alloydbgithub.com/snlabat/pokemon-pokedex-plugin
Changes in the last 7 days (differs)130
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

alloydb

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

Create, connect, and interact with an AlloyDB for PostgreSQL database and data.

pok-dex

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

Complete Pokemon Pokedex for Claude Code covering all 1,025 Pokemon across Generations 1–9. Includes base stats, abilities, egg groups, catch rates, type effectiveness charts, and a 765-move database with power, accuracy, PP, and effect descriptions. Ideal for Pokemon fans, game developers, and data analysts who want instant Pokedex lookups, type matchup calculations, or ready-to-use JSON datasets for building Pokemon apps and tools.

How to run each

alloydb As a Claude Code plugin

Claude Code
/plugin install alloydb@claude-plugins-official

pok-dex As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install pok-dex@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

The marketplaces of pok-dex publish no settings it asks for, so we do not compare settings.

What it can do: alloydb · What it can do: pok-dex · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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