Ext Ops Panel
Open dashboard
Comparison

vibe-to-prod-skills vs plugin-pilot

vibe-to-prod-skills is a plugin bundle for AI coding tools published by muyen. Marketplaces we read that list it: 1 (Community GitHub marketplaces). plugin-pilot is a plugin bundle for AI coding tools published by wion4. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-30. 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
Marketplacevibe-to-prod-skillsplugin-pilot
Community marketplace muyen/vibe-to-prod Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.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

vibe-to-prod-skills vs plugin-pilot
Factvibe-to-prod-skillsplugin-pilot
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
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 for (differs)3, secrets among them: 3Not published
Hooks it runs (differs)Not published1
Parts of the bundle (differs)135
LicenceNot statedNot stated
Repository (differs)github.com/muyen/vibe-to-prodgithub.com/wion4/plugin-pilot
Changes in the last 7 days (differs)20
First seen (differs)2026-10-292026-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

vibe-to-prod-skills

In its own words, on Community GitHub marketplaces:

Production-ready skills including ralph-invoke (Claude-initiated autonomous loops), code-review, dev-workflow, git-workflow, security-scan, and more

plugin-pilot

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

AI-driven plugin lifecycle manager for Claude Code. Automatically detects which plugins, skills, and stacks are relevant to your current task based on project files, frameworks, and context. Searches official marketplace and GitHub for matching tools, tracks usage to suggest cleanup of unused plugins, and integrates into plan mode. Includes legal framework (TOS, Privacy Policy), trust scoring for community plugins, and system language detection

How to run each

vibe-to-prod-skills As a Claude Code plugin

Claude Code
/plugin marketplace add muyen/vibe-to-prod
/plugin install vibe-to-prod-skills@vibe-to-prod

plugin-pilot As a Claude Code plugin

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

What it can do: vibe-to-prod-skills · What it can do: plugin-pilot · 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