Ext Ops Panel
Open dashboard
Comparison

content-core vs tavily

content-core is a plugin bundle for AI coding tools published by Luis Novo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). tavily is a plugin bundle for AI coding tools published by tavily-ai. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-29. 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
Marketplacecontent-coretavily
Community marketplace lfnovo/content-core Listed
Version: 2.2.0
Forks (GitHub): 44
Stars (GitHub): 182
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 1.0.0
Forks (GitHub): 42
Stars (GitHub): 491
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 1.0.0
Forks (GitHub): 42
Stars (GitHub): 491
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 42
Stars (GitHub): 491
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

content-core vs tavily
Factcontent-coretavily
Marketplaces that list it (differs)1 (worse)4 (better)
Stars (GitHub) (differs)182 (worse)491 (better)
Forks (GitHub) (differs)44 (better)42 (worse)
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)18
LicenceMITMIT
Repository (differs)github.com/lfnovo/content-coregithub.com/tavily-ai/skills
Changes in the last 7 days (differs)20
First seen (differs)2026-10-262026-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

content-core

In its own words, on Community GitHub marketplaces:

Extract text content from URLs, documents, YouTube videos, Reddit posts, and audio/video files — via CLI (uvx) or MCP.

tavily

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

Build AI applications with real-time web data using Tavily's search, extract, crawl, and research APIs.

How to run each

content-core As a Claude Code plugin

Claude Code
/plugin marketplace add lfnovo/content-core
/plugin install content-core@content-core

tavily As a Claude Code plugin

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

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: content-core · What it can do: tavily · 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-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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. 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