plugin-doctor

name	plugin-doctor
platforms	["cowork","claude-code"]
description	Run a health check on the marketing skills plugin environment. Use when someone says 'plugin-doctor', 'doctor', 'check my setup', 'is everything working?', 'diagnose', 'health check', 'something's not working', or reports errors with skills that depend on Tiger Den. Also useful after initial setup to confirm everything is connected.

Plugin Doctor — Environment Health Check

Run diagnostic checks on the tools and connections that marketing skills depend on. Report results clearly with pass/fail status and actionable fix instructions.

Detect runtime

Determine whether you're running in Cowork or Claude Code:

• If the google_drive_search tool is available → Cowork
• Otherwise → Claude Code

Checks to run

Run all checks in parallel where possible, then present a single summary.

1. Tiger Den MCP (required)

This is the primary check. All skills that use reference docs depend on Tiger Den.

Try a Tiger Den-specific tool (same in both runtimes):

list_voice_profiles()

Why list_voice_profiles and not search_content? Other connectors (like Tiger Docs) also expose a search_content tool. list_voice_profiles is unique to Tiger Den, so it won't produce false positives.

• Pass: Returns a list of voice profiles without error.
• Fail: Tool list_voice_profiles not available, connection refused, or auth error.
• Fix (Cowork): "Tiger Den isn't connected. Go to Settings (gear icon) → Connectors → find Den.tigerdata.com → click Connect and sign in. Then start a new Cowork session and run /plugin-doctor again."
• Fix (Claude Code): "Tiger Den isn't connected. Run this in a separate terminal: claude mcp add -s user --transport http tiger_den https://den.tigerdata.com/api/mcp/mcp — then restart Claude Code."

2. Google Drive (optional, Cowork only)

Google Drive is no longer required for reference docs (Tiger Den handles that now). However, some skills like case-study-prep still use google_drive_fetch to read user-provided Google Docs — so the connector is still useful in Cowork.

In Cowork, try:

google_drive_search(api_query: "name contains 'brand' and '1DUPUkDyG8bkQgoWWI4kvoLTyMk_sT1n2' in parents")

• Pass: Report "Google Drive — Connected (used for reading user docs in some skills)"
• Fail: Report "Google Drive — Not connected (optional — only needed if you use skills that read Google Docs)"
• This is informational, not a blocker. Do not present it as an error.

In Claude Code, skip this check entirely.

3. Contributor tools (optional, Claude Code only)

Contributor tools are only needed if the user plans to edit or add skills. They are not required for normal use of the plugin. Frame missing items as informational, not errors.

In Cowork, skip this check entirely — the sandbox can't probe the user's host machine, and /skill-contributor already handles missing tools in-flow for Cowork contributors.

In Claude Code, check all three in parallel via Bash:

• which gh → is the GitHub CLI installed?
• gh auth status → is the GitHub CLI authenticated? (only run this if which gh succeeded)
• git config --global user.name and git config --global user.email → is the git identity set?

Report as a grouped block labeled Contributor tools (optional):

• If all three pass → ✅ Contributor tools — ready (one line, that's it).
• If any fail → list each missing item with an ℹ️ prefix, and end with: → If you plan to contribute to skills, run /contributor-setup to get these sorted.

Never present missing contributor tools as a plugin problem — they are strictly optional.

Presenting results

Use this format:

## Plugin Health Check

✅ Tiger Den — Connected
ℹ️ Google Drive — Connected (optional)
✅ Contributor tools — ready

The Google Drive line only appears in Cowork. The Contributor tools line only appears in Claude Code.

Or with issues:

## Plugin Health Check

❌ Tiger Den — Not connected
ℹ️ Google Drive — Not connected (optional)
ℹ️ Contributor tools — gh not installed, git identity not set
  → If you plan to contribute to skills, run /contributor-setup.

1 issue found — details below.

Contributor-tool issues are not counted in the "issues found" total — only Tiger Den failures are blockers.

For each failed check, include the fix instructions directly in the output. Be concise — one or two sentences per fix, with exact steps.

If Tiger Den passes, end with: "You're all set — all the skills in this plugin have what they need."

If Tiger Den fails, end with: "Run /setup for step-by-step help getting Tiger Den configured."

Tone

Be brief and diagnostic. This isn't onboarding — the user wants a quick status report, not a tutorial. Save the hand-holding for /setup.