Diagnose and resolve common Claude Code plugin and skill configuration issues. This skill provides systematic debugging workflows for plugin installation, enablement, and activation problems.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionclaude-skills-troubleshootingExecute the skills CLI command in your project's root directory to begin installation:
Fetches claude-skills-troubleshooting from daymade/claude-code-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate claude-skills-troubleshooting. Access via /claude-skills-troubleshooting in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
784
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
784
stars
Diagnose and resolve common Claude Code plugin and skill configuration issues. This skill provides systematic debugging workflows for plugin installation, enablement, and activation problems.
Run the diagnostic script to identify common issues:
python3 scripts/diagnose_plugins.py
The script checks:
Symptoms:
/plugin shows plugin as installedinstalled_plugins.jsonRoot Cause: Known bug (GitHub #17832) - plugins are added to installed_plugins.json but NOT automatically added to enabledPlugins in settings.json.
Diagnosis:
# Check if plugin is in installed_plugins.json
cat ~/.claude/plugins/installed_plugins.json | grep "plugin-name"
# Check if plugin is enabled in settings.json
cat ~/.claude/settings.json | grep "plugin-name"
Solution:
# Option 1: Use CLI to enable
claude plugin enable plugin-name@marketplace-name
# Option 2: Manually edit settings.json
# Add to enabledPlugins section:
# "plugin-name@marketplace-name": true
Key files:
| File | Purpose |
|---|---|
~/.claude/plugins/installed_plugins.json |
Registry of ALL plugins (installed + disabled) |
~/.claude/settings.json → enabledPlugins |
Controls which plugins are ACTIVE |
~/.claude/plugins/known_marketplaces.json |
Registered marketplace sources |
~/.claude/plugins/cache/ |
Actual plugin files |
A plugin is active ONLY when:
installed_plugins.json (registered)settings.json → enabledPlugins with value trueSymptoms:
Solution:
# Update marketplace cache
claude plugin marketplace update marketplace-name
# Or clear and re-fetch
rm -rf ~/.claude/plugins/cache/marketplace-name
claude plugin marketplace update marketplace-name
Common causes (in order of likelihood):
Local changes not pushed to GitHub - Most common!
git status
git push
claude plugin marketplace update marketplace-name
marketplace.json configuration error
python3 -m json.tool .claude-plugin/marketplace.json
Skill directory missing
ls -la skill-name/SKILL.md
| Purpose | Command |
|---|---|
| List marketplaces | claude plugin marketplace list |
| Update marketplace | claude plugin marketplace update {name} |
| Install plugin | claude plugin install {plugin}@{marketplace} |
| Enable plugin | claude plugin enable {plugin}@{marketplace} |
| Disable plugin | claude plugin disable {plugin}@{marketplace} |
| Uninstall plugin | claude plugin uninstall {plugin}@{marketplace} |
| Check installed | cat ~/.claude/plugins/installed_plugins.json | jq '.plugins | keys' |
| Check enabled | cat ~/.claude/settings.json | jq '.enabledPlugins' |
To enable all installed but disabled plugins from a marketplace:
python3 scripts/enable_all_plugins.py marketplace-name
Claude Code has two types of user-invocable extensions:
Skills (in skills/ directory)
Commands (in commands/ directory)
/command-namecommands/seer.md)If a skill should be explicitly invocable, add a corresponding command file.
references/known_issues.md for GitHub issue trackingreferences/architecture.md for detailed plugin architecturePrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
JuliusBrussee/caveman
daymade/claude-code-skills
vercel-labs/skills
We added claude-skills-troubleshooting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend claude-skills-troubleshooting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in claude-skills-troubleshooting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in claude-skills-troubleshooting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
claude-skills-troubleshooting fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for claude-skills-troubleshooting matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: claude-skills-troubleshooting is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: claude-skills-troubleshooting is focused, and the summary matches what you get after install.
claude-skills-troubleshooting has been reliable in day-to-day use. Documentation quality is above average for community skills.
claude-skills-troubleshooting has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 65