claude-skills-troubleshooting_skill

This skill helps diagnose and resolve Claude Code plugin and skill activation issues, guiding you through installation, enablement, and cache problems.

Python

609

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

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

SKILL.md4.6 KB

Overview

This skill diagnoses and resolves Claude Code plugin and skill configuration issues. It provides targeted troubleshooting for plugins that are installed but not listed, skills that fail to activate, and problems with enabledPlugins in settings.json. Use it to quickly identify root causes and apply practical fixes.

How this skill works

The skill runs a set of checks against the local Claude configuration, installed plugin registry, and marketplace cache to detect mismatches and invalid configurations. It guides you through CLI and manual fixes: enabling plugins in settings.json, updating marketplace caches, and validating marketplace or skill metadata. It also includes scripts for bulk enabling and diagnostic commands for verification.

When to use it

You installed a plugin but it does not appear in the Skill tool available list
Skills are not activating automatically when a matching request is made
A plugin shows as installed but remains disabled
enabledPlugins entries are missing or incorrect in settings.json
Marketplace updates aren’t reflecting new or updated plugins

Best practices

Run the diagnostic script first: python3 scripts/diagnose_plugins.py to get a prioritized list of issues
Prefer the CLI enable command (claude plugin enable) over manual edits when possible to avoid formatting errors
Keep marketplace sources up to date: claude plugin marketplace update {name} after pushing changes
Validate JSON files (marketplace.json, settings.json) with a JSON tool before reloading
Use the cache-clearing step when installs return stale versions

Example use cases

Enable a plugin that is listed in installed_plugins.json but missing from settings.json
Clear and refresh a marketplace cache when newly added plugins are not visible
Run a quick check to list installed vs enabled plugins and reconcile differences
Bulk-enable all installed plugins from a marketplace using the provided script
Verify that a skill intended for explicit invocation has a corresponding command file

FAQ

Ensure the plugin appears in ~/.claude/plugins/installed_plugins.json and add or set its entry to true in settings.json → enabledPlugins, or run claude plugin enable {plugin}@{marketplace}.

Why do I see an older plugin version after updating the marketplace?

The local marketplace cache may be stale. Run claude plugin marketplace update {marketplace} or remove ~/.claude/plugins/cache/{marketplace} and update again.