claude-skills-troubleshooting

daymade/claude-code-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/daymade/claude-code-skills --skill claude-skills-troubleshooting
0 commentsdiscussion
summary

Diagnose and resolve common Claude Code plugin and skill configuration issues. This skill provides systematic debugging workflows for plugin installation, enablement, and activation problems.

skill.md

Claude Skills Troubleshooting

Overview

Diagnose and resolve common Claude Code plugin and skill configuration issues. This skill provides systematic debugging workflows for plugin installation, enablement, and activation problems.

Quick Diagnosis

Run the diagnostic script to identify common issues:

python3 scripts/diagnose_plugins.py

The script checks:

  • Installed vs enabled plugins mismatch
  • Missing enabledPlugins entries in settings.json
  • Stale marketplace cache
  • Invalid plugin configurations

Common Issues

Issue 1: Plugin Installed But Not Showing in Available Skills

Symptoms:

  • /plugin shows plugin as installed
  • Skill not appearing in Skill tool's available list
  • Plugin metadata exists in installed_plugins.json

Root 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

Issue 2: Understanding Plugin State Architecture

Key files:

File Purpose
~/.claude/plugins/installed_plugins.json Registry of ALL plugins (installed + disabled)
~/.claude/settings.jsonenabledPlugins 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:

  1. Exists in installed_plugins.json (registered)
  2. Listed in settings.jsonenabledPlugins with value true

Issue 3: Marketplace Cache Stale

Symptoms:

  • GitHub has latest changes
  • Install finds plugin but gets old version
  • Newly added plugins not visible

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

Issue 4: Plugin Not Found in Marketplace

Common causes (in order of likelihood):

  1. Local changes not pushed to GitHub - Most common!

    git status
    git push
    claude plugin marketplace update marketplace-name
    
  2. marketplace.json configuration error

    python3 -m json.tool .claude-plugin/marketplace.json
    
  3. Skill directory missing

    ls -la skill-name/SKILL.md
    

Diagnostic Commands Reference

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'

Batch Enable Missing Plugins

To enable all installed but disabled plugins from a marketplace:

python3 scripts/enable_all_plugins.py marketplace-name

Skills vs Commands Architecture

Claude Code has two types of user-invocable extensions:

  1. Skills (in skills/ directory)

    • Auto-activated based on description matching
    • Loaded when user request matches skill description
  2. Commands (in commands/ directory)

    • Explicitly invocable via /command-name
    • Appears in Skill tool's available list
    • Requires command file (e.g., commands/seer.md)

If a skill should be explicitly invocable, add a corresponding command file.

References

  • See references/known_issues.md for GitHub issue tracking
  • See references/architecture.md for detailed plugin architecture
how to use claude-skills-troubleshooting

How to use claude-skills-troubleshooting on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add claude-skills-troubleshooting
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/daymade/claude-code-skills --skill claude-skills-troubleshooting

The skills CLI fetches claude-skills-troubleshooting from GitHub repository daymade/claude-code-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/claude-skills-troubleshooting

Reload or restart Cursor to activate claude-skills-troubleshooting. Access the skill through slash commands (e.g., /claude-skills-troubleshooting) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ 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.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.765 reviews
  • Aisha Abbas· Dec 28, 2024

    We added claude-skills-troubleshooting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Zara Huang· Dec 28, 2024

    I recommend claude-skills-troubleshooting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Dhruvi Jain· Dec 24, 2024

    Useful defaults in claude-skills-troubleshooting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Nia Garcia· Dec 24, 2024

    Useful defaults in claude-skills-troubleshooting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kaira Farah· Dec 12, 2024

    claude-skills-troubleshooting fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Amina Kim· Dec 4, 2024

    Registry listing for claude-skills-troubleshooting matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Tariq Ramirez· Nov 23, 2024

    Keeps context tight: claude-skills-troubleshooting is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kiara Martin· Nov 19, 2024

    Solid pick for teams standardizing on skills: claude-skills-troubleshooting is focused, and the summary matches what you get after install.

  • Oshnikdeep· Nov 15, 2024

    claude-skills-troubleshooting has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Kaira Torres· Nov 15, 2024

    claude-skills-troubleshooting has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 65

1 / 7