claude-skills-troubleshooting

Name: claude-skills-troubleshooting
Author: daymade

Engineering Community

Repo stars 1,187
Forks 185
Author updated Jun 14, 2026, 10:01 AM
Author repo claude-code-skills

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Engineering
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @daymade · no license declared
Token usage: Lean
Setup complexity: Plug-and-play
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Network behavior: External requests
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview claude-skills-troubleshooting.preview

---
name: claude-skills-troubleshooting
description: Diagnose and resolve Claude Code plugin and skill issues. This skill should be used when plugins…
category: engineering
runtime: no special runtime
---

# claude-skills-troubleshooting output preview

## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Quick Diagnosis / Common Issues” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “Overview / Quick Diagnosis / Common Issues” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.

## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: claude-skills-troubleshooting
description: Diagnose and resolve Claude Code plugin and skill issues. This skill should be used when plugins…
category: engineering
source: daymade/claude-code-skills
---

# claude-skills-troubleshooting

## When to use
- Diagnose and resolve Claude Code plugin and skill issues. This skill should be used when plugins are installed but not…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Overview / Quick Diagnosis / Common Issues” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "claude-skills-troubleshooting" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Overview / Quick Diagnosis / Common Issues
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files | may access external network resources
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Diagnose and resolve Claude Code plugin and skill issues. This skill should be used when plugins are installed but not showing i…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Overview”, “Quick Diagnosis”, “Common Issues”, “Issue 1: Plugin Installed But Not Showing in Available Skills”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name claude-skills-troubleshooting directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Overview / Quick Diagnosis / Common Issues” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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

Exists in installed_plugins.json (registered)
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):

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
```

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:

Skills (in skills/ directory)
- Auto-activated based on description matching
- Loaded when user request matches skill description
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

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

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

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: local
daymade/claude-code-skills
中文

More by @daymade

Category & tags

Category Engineering