SkillAgentSearch skills...

claude-skills-troubleshooting

Diagnose and resolve Claude Code plugin and skill issues. This skill should be used when plugins are installed but not showing in available skills list, skills are not activating as expected, or when troubleshooting enabledPlugins configuration in settings.json.

Install / Use

npx skills add daymade/claude-code-skills --skill claude-skills-troubleshooting

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Claude Code

Tags

Our assessment of claude-skills-troubleshooting

claude-skills-troubleshooting scores 89/100 on our quality scale, 1646th of 4,700 Development & Engineering skills we index (top 36%).

Its SKILL.md is 5.7 KB long, well organised into 22 sections with 6 code examples: a solid amount of guidance for an agent.

With 1,426 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so claude-skills-troubleshooting is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

claude-skills-troubleshooting compared with similar skills

All 4 of these similar skills score higher than claude-skills-troubleshooting; compare them before choosing.

SkillScoreStarsUpdatedFormat
claude-skills-troubleshooting (this skill)by daymade891.4k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install claude-skills-troubleshooting?
Run npx skills add daymade/claude-code-skills --skill claude-skills-troubleshooting. The install tabs above show the steps for each supported agent.
Which AI agents does claude-skills-troubleshooting work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is claude-skills-troubleshooting safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is claude-skills-troubleshooting still maintained?
The repository was last updated about 2 months ago, so claude-skills-troubleshooting is actively maintained.

name: claude-skills-troubleshooting disable-model-invocation: true description: Diagnose and resolve Claude Code plugin and skill issues. This skill should be used when plugins are installed but not showing in available skills list, skills are not activating as expected, or when troubleshooting enabledPlugins configuration in settings.json. Triggers include "plugin not working", "skill not showing", "installed but disabled", or "enabledPlugins" issues.

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 in both directions (installed-but-not-enabled and enabled-but-not-registered)
  • Missing enabledPlugins entries in settings.json
  • Stale marketplace cache using known_marketplaces.json lastUpdated
  • Missing, malformed, timezone-free, or future lastUpdated metadata
  • Invalid plugin configurations

Treat lastUpdated as the only cache-freshness source. Do not fall back to cache-directory modification times: marketplace updates can refresh nested files without changing that directory timestamp. The diagnostic exits nonzero for stale caches or invalid freshness metadata.

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

Mirror variant — enabled but not registered: If diagnosis instead shows the plugin in enabledPlugins but NOT in installed_plugins.json, the cause is the symlink-skip bug: the install ran under a config dir where installed_plugins.json is a symlink (multi-profile shared setups), and the CLI silently skipped writing it. See references/known_issues.md → "Symlinked installed_plugins.json". Fix:

# Reinstall from the config dir owning the real file
CLAUDE_CONFIG_DIR=~/.claude claude plugin install plugin-name@marketplace-name

# Then confirm
claude plugin list

Issue 2: Understanding Plugin State Architecture

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:

  1. Exists in installed_plugins.json (registered)
  2. Listed in settings.json → enabledPlugins 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

Related Skills

View on GitHub
GitHub Stars1.4k
CategoryDevelopment
Updated1mo ago
Forks219

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions