Skip to main content

Doctor

Plugin Doctor

Understand your local Claude Code plugin health — findings, affected plugins, remediation, and always-on context size. Run one command, then read the report right here in your browser. Local, read-only, no account.

Run in your project folder
$
npx claudepluginhub doctor --json

Doctor scans your local Claude Code plugins offline and prints a sanitized JSON report — no absolute paths, file contents, secrets, or commands. Nothing is uploaded; paste the output below to read it in your browser.

Read your report

Paste the JSON, drop a file, or open the example. Everything is parsed locally — no report contents or diagnostics are uploaded.

Everything is processed in your browser — the report is never uploaded.

What Doctor checks

Install integrity

Missing, unreadable, or ambiguous plugin installations and duplicate records.

Manifests

Invalid JSON, invalid names, wrong field types, and declared-but-missing component paths.

Prerequisites

MCP/LSP executables not found on PATH and bin files without an executable bit.

Hooks

Broad, unconditional command hooks that would run on every matching tool event.

Dependencies

Declared plugin dependencies that are missing, disabled, or unverifiable.

Context size

Estimated always-on token cost per project context, with an incomplete-scan lower-bound signal.

How it works

  1. 1

    Run it in your project

    Run npx claudepluginhub doctor --json in your project folder. It scans your local plugins offline and read-only.

  2. 2

    Copy the JSON

    Copy the sanitized JSON it prints — no absolute paths, file contents, secrets, or commands are included.

  3. 3

    Read it here

    Paste, drop, or upload the JSON below. It is parsed entirely in your browser and never uploaded.

Your report stays in your browser

The report is parsed locally in your browser. No report contents or diagnostic details — plugin names, findings, versions, paths, or remediation — are uploaded anywhere. The site records only anonymous interaction events, such as “command copied” or “report opened”, with no report-derived fields.