Plugin Management
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.
What this skill does
# Plugin Management for Claude Code ## Overview This skill provides guidance for managing Claude Code plugins, including installation, upgrading, troubleshooting, and best practices. ## Plugin Locations 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 | ## Plugin Types by Source ### Git Repository Plugins Plugins installed from Git repositories: - Can be upgraded using `git pull` - Support version tags - May have upstream changes **Upgrade method:** ```bash cd ~/.claude/plugins/<plugin-name> git fetch --all git pull origin main ``` ### Marketplace Plugins Official plugins from Claude Code marketplace: - Managed by Claude Code - Located in `~/.claude/plugins/cache/claude-plugins-official/` - Upgrade via Claude CLI: `claude plugins update <plugin-name>` ### Local Plugins Plugins created or copied locally: - No automatic upgrade path - Must be updated manually - Check plugin repository for updates ## Troubleshooting ### Plugin Not Loading 1. **Check plugin structure:** - Verify `.claude-plugin/plugin.json` exists - Confirm JSON syntax is valid - Check `name` field is present 2. **Verify installation:** ```bash ls -la ~/.claude/plugins/<plugin-name>/ cat ~/.claude/plugins/<plugin-name>/.claude-plugin/plugin.json ``` 3. **Check Claude Code logs:** ```bash claude --debug ``` ### Plugin Broken After Upgrade 1. **Check for breaking changes:** - Read plugin's CHANGELOG or release notes - Check if dependencies updated 2. **Rollback to previous version:** ```bash cd ~/.claude/plugins/<plugin-name> git log --oneline # Find previous commit git checkout <commit-hash> ``` 3. **Or checkout specific tag:** ```bash git tag -l # List available tags git checkout v1.0.0 # Checkout stable version ``` ### Commands Not Appearing 1. **Check command file location:** - Commands must be in `commands/` directory - Files must have `.md` extension 2. **Verify YAML frontmatter:** ```yaml --- description: Command description --- ``` 3. **Restart Claude Code:** - Exit current session - Start new session ### Hooks Not Executing 1. **Verify hooks.json syntax:** ```bash cat ~/.claude/plugins/<plugin-name>/hooks/hooks.json | jq . ``` 2. **Check hook scripts are executable:** ```bash chmod +x ~/.claude/plugins/<plugin-name>/hooks/scripts/*.sh ``` 3. **Test hooks with debug mode:** ```bash claude --debug ``` ## Upgrade Strategies ### Conservative Upgrade Upgrade one plugin at a time, test after each: 1. Check for updates: `/plugin-upgrade:check` 2. Read release notes 3. Upgrade single plugin 4. Test plugin functionality 5. Proceed to next plugin ### Batch Upgrade Upgrade multiple plugins at once: 1. Check for updates: `/plugin-upgrade:check` 2. Review all changes available 3. Use `/plugin-upgrade:upgrade` to select multiple 4. Test all upgraded plugins ### Rollback Plan Before upgrading, prepare rollback: 1. Note current versions 2. For Git plugins, note current commit hash 3. After upgrade, if issues occur, rollback immediately ## Best Practices ### Before Upgrading - Read release notes or CHANGELOG - Check for breaking changes - Backup custom configurations - Note current working version ### After Upgrading - Restart Claude Code session - Test core plugin functionality - Check for deprecation warnings - Update any dependent configurations ### Regular Maintenance - Check for updates periodically - Keep plugins reasonably current - Remove unused plugins - Document custom plugin modifications ## Common Issues and Solutions | 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 | ## Getting Help If you encounter persistent issues: 1. Check plugin's GitHub issues 2. Review plugin documentation 3. Use `claude --debug` for detailed logs 4. Contact plugin maintainer
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.