Ext Ops Panel
Open dashboard
Comparison

summarize-meetings vs vault-pkm

summarize-meetings is a plugin bundle for AI coding tools published by 2389-research. Marketplaces we read that list it: 1 (Community GitHub marketplaces). vault-pkm is a plugin bundle for AI coding tools published by AdrianV101. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-18. 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
Marketplacesummarize-meetingsvault-pkm
Community marketplace 2389-research/claude-plugins Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 15
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 3.10.1
Forks (GitHub): 3
Stars (GitHub): 14
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

summarize-meetings vs vault-pkm
Factsummarize-meetingsvault-pkm
Marketplaces that list it11
Stars (GitHub) (differs)15 (better)14 (worse)
Forks (GitHub) (differs)1 (worse)3 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (obsidian-pkm)
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not published14
Licence (differs)Not statedMIT
Repository (differs)github.com/2389-research/summarize-meetingsgithub.com/adrianv101/obsidian-pkm-plugin
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-12

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

summarize-meetings

In its own words, on Community GitHub marketplaces:

Batch-process meeting transcripts from Obsidian vault into structured summaries with knowledge graph updates, people notes, and concept extraction

vault-pkm

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

Personal knowledge management for Claude Code. Connect to your Obsidian vault with 20 MCP tools, semantic search, wikilink graph traversal, template-based note creation, link health audits, and cross-session activity logging. Includes 3 autonomous agents and hooks for proactive knowledge capture.

How to run each

summarize-meetings As a Claude Code plugin

Claude Code
/plugin marketplace add 2389-research/claude-plugins
/plugin install summarize-meetings@2389-research

vault-pkm As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vault-pkm@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 summarize-meetings publish no settings it asks for, so we do not compare settings.

What it can do: summarize-meetings · What it can do: vault-pkm · 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