Ext Ops Panel
Open dashboard
Comparison

brewdoc vs distill

brewdoc is a plugin bundle for AI coding tools published by Maksim Kochetkov. Marketplaces we read that list it: 1 (Community GitHub marketplaces). distill is a plugin bundle for AI coding tools published by UtkarshJain98. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-28. 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
Marketplacebrewdocdistill
Community marketplace kochetkov-ma/claude-brewcode Listed
Version: 6.12.5
Forks (GitHub): 4
Stars (GitHub): 39
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.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

brewdoc vs distill
Factbrewdocdistill
Marketplaces that list it11
Stars (GitHub) (differs)39 (better)0 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last release (differs)2026-10-26Not 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)51
LicenceMITMIT
Repository (differs)github.com/kochetkov-ma/claude-brewcodegithub.com/utkarshjain98/distill
Changes in the last 7 days (differs)30
First seen (differs)2026-10-252026-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

brewdoc

In its own words, on Community GitHub marketplaces:

Brewdoc - Claude Code documentation tools: doc-staleness tracking, memory-sync generator, my-claude installation docs, Markdown to PDF, publishing to brewpage.app

distill

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

distill analyzes your codebase and generates structured context files in .claude/docs/. Instead of Claude reading source files to orient itself every session, it reads concise, pre-built docs on demand — testing.md when working on tests, api.md when working on endpoints, nothing when the task doesn't need it. Token cost becomes proportional to task relevance, not project size. Supports incremental updates (--update only regenerates stale docs), depth profiles (--lean for 30-line summaries, --deep for comprehensive reference), parallel generation for large doc sets, monorepo detection, team configuration via .distill.yml, and a pre-push hook that warns when docs drift.

How to run each

brewdoc As a Claude Code plugin

Claude Code
/plugin marketplace add kochetkov-ma/claude-brewcode
/plugin install brewdoc@claude-brewcode

distill As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install distill@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: brewdoc · What it can do: distill · 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/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