Ext Ops Panel
Open dashboard
Comparison

skill-provenance vs io.github.oxbshw/watch-skill

skill-provenance is a plugin bundle for AI coding tools published by snapsynapse. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.oxbshw/watch-skill is an MCP server published by oxbshw. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
Marketplaceskill-provenanceio.github.oxbshw/watch-skill
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 1
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.3
Downloads/month (PyPI): 2 097
Downloads/week (PyPI): 468
Forks (GitHub): 69
Stars (GitHub): 484
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

skill-provenance vs io.github.oxbshw/watch-skill
Factskill-provenanceio.github.oxbshw/watch-skill
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 (worse)484 (better)
Forks (GitHub) (differs)1 (worse)69 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (watch-skill)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)512
LicenceMITMIT
Repository (differs)github.com/snapsynapse/skill-provenancegithub.com/oxbshw/watch-skill
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-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

skill-provenance

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

Version tracking for Agent Skills bundles across sessions, surfaces, and platforms. When you load a skill into a new session, Skill Provenance reads the manifest, verifies file hashes, flags stale evals, and tells you what needs attention. When you save, it bumps versions, recomputes hashes, and updates the changelog. Works anywhere the agentskills.io standard does (30+ agent tools).

io.github.oxbshw/watch-skill

In its own words, on Official MCP Registry:

Watch video and live sessions, keep timestamped evidence, and verify an agent's own work.

How to run each

skill-provenance As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install skill-provenance@claude-community

io.github.oxbshw/watch-skill As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio watch-skill -- uvx --from "watch-skill[standard]==1.4.3" watch-skill serve

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: skill-provenance · What it can do: io.github.oxbshw/watch-skill · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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