Keeping your Claude Marketplace plugins updated

There are two separate things to keep current: the marketplace catalog and the plugins themselves. They update with different commands.

Catalog vs plugin

Refresh the catalog to pick up newly added plugins and version changes:

claude plugin marketplace update robworks-claude-code-plugins

Update an installed plugin to its latest pinned version:

claude plugin update <plugin-name>@robworks-claude-code-plugins

Refreshing the catalog does not upgrade what you already have installed - you still run plugin update for that. Do the catalog refresh first, then the plugin update.

How often to check

There’s no fixed schedule, but a few natural moments:

• When a plugin tells you. Some plugins (like claude-quikgif and ga-mcp-full) check on session start and print a short “new version available” notice. That’s your cue.
• Before reporting a problem. If something’s misbehaving, refresh the catalog and update the plugin first - the fix may already be shipped.
• Periodically. A quick catalog refresh every couple of weeks is plenty for most people.

How versions work

Each marketplace entry pins a plugin to a released version tag. When we ship a new release and bump that pin, plugin update moves you to it. You can see every plugin’s current version and description, rendered live from the catalog, at code.robworks.info/plugins.

Making an update take effect

Installing or updating downloads the new version, but its commands, skills, and MCP tools load when you start a session. Restart Claude Code after updating so the new version is active.

Update not sticking? Send us a message and a human will reply by email.