doctor

Diagnoses and repairs oh-my-kimi installation issues including hooks and config.

2|Updated May 11, 2026

Search Tags:#hooks #mcp #configuration validation #installation diagnostics #kimi cli #skill symlinks

Ready to run

npx skills add https://github.com/xz1220/oh-my-kimi --skill doctor-xz1220

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/xz1220/oh-my-kimi/tree/main/skills/doctor
Command: npx skills add https://github.com/xz1220/oh-my-kimi --skill doctor-xz1220

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly identify why your oh-my-kimi installation is partially broken (missing skills, failing hooks, a faulty wrapper, invalid config) and provides exact commands to fix it.

Core Features & Use Cases

Installation health checks: Verifies Kimi CLI availability/version, repo layout, skill symlinks, the kimi-omk wrapper, and managed hook TOML integrity.
Hook and wrapper verification: Confirms hook scripts are executable and the managed config.toml block is present and parseable.
Optional MCP server reporting: When MCP is expected, it checks whether recommended MCP servers are installed.

Quick Start

Ask the AI to run a non-destructive diagnosis by using the doctor skill without any fix actions.

Frequently Asked Questions about doctor

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

FAQPage Schema

How do I fix oh-my-kimi installation issues when skill lookups fail?▼

To fix oh-my-kimi installation issues when skill lookups fail, you need to verify the Kimi CLI availability, check repo layout, and validate skill symlinks. Run a non-destructive diagnosis to identify missing components and get exact repair commands.

Why does kimi report invalid TOML in config.toml during hook configuration?▼

Kimi reports invalid TOML in config.toml when the managed hook configuration block is unparseable or missing required markers. You must verify the hook scripts are executable and enforce expected hook markers to restore TOML integrity.

How do I troubleshoot kimi-omk wrapper crashes and hooks that do not trigger?▼

To troubleshoot kimi-omk wrapper crashes and hooks that do not trigger, verify the wrapper installation and confirm hook scripts are executable. A diagnostic check validates the wrapper layout and enforces hook markers to resolve execution failures.

Can I check recommended MCP server installation for Kimi CLI?▼

You can check recommended MCP server installation for Kimi CLI by running an optional MCP server reporting diagnostic. This validates whether expected MCP servers are present within your oh-my-kimi setup.

What is the best way to diagnose a partially broken oh-my-kimi setup?▼

The best way to diagnose a partially broken oh-my-kimi setup is to run a non-destructive health check. This verifies the Kimi CLI version, repo layout, skill symlinks, wrapper integrity, and managed hook TOML to provide exact fix commands.