Agent skill · software engineering · daymade
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. Triggers include "plugin not working", "skill not showing", "installed but disabled", or "enabledPlugins" issues.
Why this skill is useful
Adds a diagnostic script and specific commands for troubleshooting Claude Code plugin issues that the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 1,320 stars on the source repository.
What this skill does
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: 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 knownmarketplaces.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 installedplugins.json Root Cause: Known bug (GitHub #17832) - plugins are added to installedplugins.json but NOT automatically added to enabledPlugins in settings.json. Diagnosis: Solution: Mirror variant — enabled but not registered: If diagnosis instead shows the plugin in enabledPlugins but NOT in installedplugins.json, the cause is the symlink-skip bug: the install ran under a config dir where installedplugins.json is a symlink (multi-profile shared setups), and the CLI silently skipped writing it. See references/knownissues.md → "Symlinked installedplugins.json". …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/claude-skills-troubleshooting