agentleFS
sudeepgupta90sudeepgupta90/my-ai-marketplace/skills/plugin-doctor/SKILL.md

plugin-doctor

Skill0 starsChanged 9 days agoMITView on GitHub

Diagnose plugin problems - plugins disabled by unresolved dependencies, missing marketplaces, or cache misses. Use when a skill that should be available is missing, when a plugin appears disabled unexpectedly, when the /plugin Errors tab shows something, or when the user asks to check or verify their AI setup.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After any fix, run /reload-plugins — installing or enabling a plugin does not activate it in the current session.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plugin doctor

Reports plugins that loaded with errors, and the exact command to fix each one.

Why this exists

A plugin whose dependency fails to resolve is disabled quietly. The reason is recorded in the /plugin Errors tab, which nobody opens, so the usual symptom is "a skill I installed just isn't there".

The most common cause is a dependency living in a marketplace the user never registered. Dependency resolution only searches marketplaces that have been added, so an unregistered one produces no error at install time — the dependency is simply left unresolved and the dependent plugin is switched off.

Run it

node "${CLAUDE_PLUGIN_ROOT}/scripts/doctor.mjs"

Report the output to the user. If it lists problems, each one comes with a fix: line — offer to run it.

Interpreting the common errors

ErrorMeaningFix
dependency-unsatisfiedA declared dependency is not installed, or is installed but disabledInstall it. If its marketplace is not registered, claude plugin marketplace add <source> first — Claude Code then resolves the dependency automatically, with no reinstall needed
cross-marketplaceA plugin depends on another marketplace that is not in the root marketplace's allowCrossMarketplaceDependenciesOnAdd it to catalog/marketplace.yaml and rebuild, or install the dependency manually first (an already-installed dependency satisfies the constraint)
plugin-cache-missUsually follows a rename; the plugin must be re-fetched under its new nameclaude plugin install <name>@<marketplace>
range-conflictTwo plugins demand incompatible versions of the same dependencyWiden or drop one constraint; my-ai-marketplace uses unconstrained dependencies precisely to avoid this

After any fix, run /reload-plugins — installing or enabling a plugin does not activate it in the current session.

Note on scope

dependency-unsatisfied can also mean the dependency is installed but disabled, which reads as a missing-plugin problem but needs claude plugin enable rather than an install. The doctor output distinguishes these: anything merely disabled is listed separately, under "Also disabled".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.