skill-doctor

Run environment diagnostics across providers, auth, config, hooks, scheduler, and skills.

4.0k|369|Updated Jan 15, 2026

Search Tags:#authentication #config #setup #environment #diagnostics #providers #healthcheck

Ready to run

npx skills add https://github.com/nyldn/claude-octopus --skill skill-doctor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-doctor
Source: https://github.com/nyldn/claude-octopus/tree/main/skills/skill-doctor
Command: npx skills add https://github.com/nyldn/claude-octopus --skill skill-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Environment diagnostics across 11 check categories. Identifies misconfigured providers, stale state, broken hooks, and other issues that prevent Claude Octopus from working correctly.

Core Features & Use Cases

Run 11 checks to validate providers, authentication, config, state, hooks, scheduler, and skills.
Detect misconfigurations, stale state, broken hooks, and other issues before they impact workflows.
Use during setup, before demos, or after updates to ensure a healthy runtime environment.

Quick Start

From the plugin root, run the full diagnostics with bash scripts/orchestrate.sh doctor.

Frequently Asked Questions about skill-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run environment health diagnostics to check provider authentication and configuration?▼

Run environment health diagnostics with bash scripts/orchestrate.sh doctor to validate provider authentication, configuration, hooks, scheduler, and skills across 11 check categories, reporting misconfigurations and stale state.

What environment health checks should I run after installing or updating plugins?▼

After installation or updates, run a full diagnostics check covering providers, auth, config, state, hooks, scheduler, and skills to detect broken hooks, misconfigured providers, and stale state before they impact workflows.

Can I filter diagnostics by category and output results as JSON?▼

Yes, the diagnostics support category filtering to run targeted checks, and both verbose and JSON output formats for structured health reporting across the 11 check categories.

Why does my plugin setup fail with authentication or configuration errors?▼

Setup failures often stem from misconfigured providers, stale state, or broken hooks. Running comprehensive diagnostics across auth, config, and runtime state identifies which of the 11 check categories is causing the issue.

When should I run environment diagnostics for my plugin runtime?▼

Run environment diagnostics during initial setup, after installation or updates, before demos, and whenever issues arise to verify authentication, configuration, and runtime state are all healthy.

What is the best way to verify plugin health before a demo or presentation?▼

The best way to verify plugin health before demos is running comprehensive diagnostics that check providers, auth, config, hooks, scheduler, and skills, ensuring no misconfigurations or broken components will surface during runtime.