doctor

Run functional checks, security audits, and cleanup for Gobby CLI and MCP tools.

19|3|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/GobbyAI/gobby --skill doctor-gobbyai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/GobbyAI/gobby/tree/main/src/gobby/install/shared/skills/doctor
Command: npx skills add https://github.com/GobbyAI/gobby --skill doctor-gobbyai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates comprehensive system health checks and security audits to validate Gobby's CLI and MCP tooling, ensuring reliability, safety, and integrity across daemon operations.

Core Features & Use Cases

  • Functional health verification: validates that daemon commands and MCP integrations operate correctly.
  • Security and integrity audits: scans for misconfigurations, insecure bindings, and potential exposure.
  • Automated cleanup and diagnostics: identifies and removes stale diagnostic artifacts and reports results for remediation.

Quick Start

Start by listing available options with /gobby doctor, then run full checks with --all, security-focused audits with --security, or cleanup with --cleanup.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I run a health check on the Gobby CLI daemon?

Run a Gobby CLI health check by executing /gobby doctor with the --all flag to perform functional verifications and read-only checks during daemon operation, reporting per-test PASS or FAIL results.

Can I scan for security misconfigurations and insecure bindings in MCP tools?

Yes, you can scan for security misconfigurations in MCP tools by running /gobby doctor --security, which performs security audits to detect insecure bindings and potential exposure risks.

What is the best way to automate system health validation for CLI and MCP integrations?

Automating system health validation for CLI and MCP integrations is best handled by running /gobby doctor, which enforces phased execution, tracks diagnostic artifacts, and verifies functional operations.

How do I clean up stale diagnostic artifacts after a system audit?

Clean up stale diagnostic artifacts after a system audit by running /gobby doctor --cleanup, which identifies and removes leftover files while reporting the validation results for remediation.

Does the Gobby security audit support read-only verifications during daemon operation?

Yes, the Gobby security audit supports read-only verifications during daemon operation, applying automated checks to validate system integrity and safety without modifying the active environment.

Why does my Gobby system audit report FAIL for specific diagnostic tests?

A Gobby system audit reports FAIL for specific diagnostic tests when functional checks, security validations, or integrity scans detect misconfigurations, insecure bindings, or stale artifacts requiring remediation.