From plugin-upgrade
Use this skill when the user asks about "plugin management", "plugin upgrade issues", "plugin troubleshooting", "plugin version", "plugin not working after upgrade", "rollback plugin", "downgrade plugin", or has problems with Claude Code plugins. Provides guidance on managing, upgrading, and troubleshooting Claude Code plugins.
npx claudepluginhub sontixyou/claude-code-plugin-upgrader --plugin plugin-upgradeThis skill uses the workspace's default tool permissions.
This skill provides guidance for managing Claude Code plugins, including installation, upgrading, troubleshooting, and best practices.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
This skill provides guidance for managing Claude Code plugins, including installation, upgrading, troubleshooting, and best practices.
Claude Code plugins are stored in these locations:
| Location | Description |
|---|---|
~/.claude/plugins/ | User-installed plugins |
~/.claude/plugins/cache/ | Marketplace plugins (managed by Claude Code) |
.claude-plugin/ | Project-local plugins |
Plugins installed from Git repositories:
git pullUpgrade method:
cd ~/.claude/plugins/<plugin-name>
git fetch --all
git pull origin main
Official plugins from Claude Code marketplace:
~/.claude/plugins/cache/claude-plugins-official/claude plugins update <plugin-name>Plugins created or copied locally:
Check plugin structure:
.claude-plugin/plugin.json existsname field is presentVerify installation:
ls -la ~/.claude/plugins/<plugin-name>/
cat ~/.claude/plugins/<plugin-name>/.claude-plugin/plugin.json
Check Claude Code logs:
claude --debug
Check for breaking changes:
Rollback to previous version:
cd ~/.claude/plugins/<plugin-name>
git log --oneline # Find previous commit
git checkout <commit-hash>
Or checkout specific tag:
git tag -l # List available tags
git checkout v1.0.0 # Checkout stable version
Check command file location:
commands/ directory.md extensionVerify YAML frontmatter:
---
description: Command description
---
Restart Claude Code:
Verify hooks.json syntax:
cat ~/.claude/plugins/<plugin-name>/hooks/hooks.json | jq .
Check hook scripts are executable:
chmod +x ~/.claude/plugins/<plugin-name>/hooks/scripts/*.sh
Test hooks with debug mode:
claude --debug
Upgrade one plugin at a time, test after each:
/plugin-upgrade:checkUpgrade multiple plugins at once:
/plugin-upgrade:check/plugin-upgrade:upgrade to select multipleBefore upgrading, prepare rollback:
| Issue | Solution |
|---|---|
| "Plugin not found" | Check plugin directory exists and has valid plugin.json |
| "Command not recognized" | Restart Claude Code, verify command file exists |
| "Hook timeout" | Increase timeout in hooks.json or optimize hook script |
| "Git pull failed" | Check for local changes, try git stash first |
| "Permission denied" | Run chmod +x on script files |
If you encounter persistent issues:
claude --debug for detailed logs