skills/doctor/SKILL.md
Diagnose and fix oh-my-kimi installation issues
npx skillsauth add Goblin1024/oh-my-kimi doctorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Note: All ~/.kimi/... paths in this guide respect KIMI_HOME when that environment variable is set.
OMX installs skills to ${KIMI_HOME:-~/.codex}/skills/ �this is the path current Codex CLI natively loads as its skill root.
~/.agents/skills/ is a historical legacy path from an older Codex CLI release, before Codex settled on ~/.codex as its home directory. Current Codex CLI and OMX no longer write there.
In a mixed OMX + plain Codex environment:
${KIMI_HOME:-~/.codex}/skills/ (user scope) or .kimi/skills/ (project scope)~/.agents/skills/ �if this still exists alongside the canonical root, Codex's Enable/Disable Skills UI will show duplicate entries for any skill present in both trees~/.agents/skills/ once you have confirmed ${KIMI_HOME:-~/.codex}/skills/ is your active rootYou are the OMX Doctor - diagnose and fix installation issues.
# Get installed version
INSTALLED=$(ls ~/.kimi/plugins/cache/omc/oh-my-kimi/ 2>/dev/null | sort -V | tail -1)
echo "Installed: $INSTALLED"
# Get latest from npm
LATEST=$(npm view oh-my-kimi version 2>/dev/null)
echo "Latest: $LATEST"
Diagnosis:
Check ~/.kimi/config.toml first (current Codex config), then check legacy ~/.kimi/settings.json only if it exists.
Look for hook entries pointing to removed scripts like:
bash $HOME/.kimi/hooks/keyword-detector.shbash $HOME/.kimi/hooks/persistent-mode.shbash $HOME/.kimi/hooks/session-start.shDiagnosis:
ls -la ~/.kimi/hooks/*.sh 2>/dev/null
Diagnosis:
keyword-detector.sh, persistent-mode.sh, session-start.sh, or stop-continuation.sh exist: WARN - legacy scripts (can cause confusion)# Check if AGENTS.md exists
ls -la ~/.kimi/AGENTS.md 2>/dev/null
# Check for OMX marker
grep -q "oh-my-kimi Multi-Agent System" ~/.kimi/AGENTS.md 2>/dev/null && echo "Has OMX config" || echo "Missing OMX config"
Diagnosis:
# Count versions in cache
ls ~/.kimi/plugins/cache/omc/oh-my-kimi/ 2>/dev/null | wc -l
Diagnosis:
Check for legacy agents, commands, and historical legacy skill roots from older installs/migrations:
# Check for legacy agents directory
ls -la ~/.kimi/agents/ 2>/dev/null
# Check for legacy commands directory
ls -la ~/.kimi/commands/ 2>/dev/null
# Check canonical current skills directory
ls -la ${KIMI_HOME:-~/.codex}/skills/ 2>/dev/null
# Check historical legacy skill directory
ls -la ~/.agents/skills/ 2>/dev/null
Diagnosis:
~/.kimi/agents/ exists with oh-my-kimi-related files: WARN - legacy agents (now provided by plugin)~/.kimi/commands/ exists with oh-my-kimi-related files: WARN - legacy commands (now provided by plugin)${KIMI_HOME:-~/.codex}/skills/ exists with OMX skills: OK - canonical current user skill root~/.agents/skills/ exists: WARN - historical legacy skill root that can overlap with ${KIMI_HOME:-~/.codex}/skills/ and cause duplicate Enable/Disable Skills entriesLook for files like:
architect.md, researcher.md, explore.md, executor.md, etc. in agents/ultrawork.md, deepsearch.md, etc. in commands/.md files in skills/After running all checks, output a report:
## OMX Doctor Report
### Summary
[HEALTHY / ISSUES FOUND]
### Checks
| Check | Status | Details |
|-------|--------|---------|
| Plugin Version | OK/WARN/CRITICAL | ... |
| Hook Config (config.toml / legacy settings.json) | OK/CRITICAL | ... |
| Legacy Scripts (~/.kimi/hooks/) | OK/WARN | ... |
| AGENTS.md | OK/WARN/CRITICAL | ... |
| Plugin Cache | OK/WARN | ... |
| Legacy Agents (~/.kimi/agents/) | OK/WARN | ... |
| Legacy Commands (~/.kimi/commands/) | OK/WARN | ... |
| Skills (${KIMI_HOME:-~/.codex}/skills) | OK/WARN | ... |
| Legacy Skill Root (~/.agents/skills) | OK/WARN | ... |
### Issues Found
1. [Issue description]
2. [Issue description]
### Recommended Fixes
[List fixes based on issues]
If issues found, ask user: "Would you like me to fix these issues automatically?"
If yes, apply fixes:
If ~/.kimi/settings.json exists, remove the legacy "hooks" section (keep other settings intact).
rm -f ~/.kimi/hooks/keyword-detector.sh
rm -f ~/.kimi/hooks/persistent-mode.sh
rm -f ~/.kimi/hooks/session-start.sh
rm -f ~/.kimi/hooks/stop-continuation.sh
rm -rf ~/.kimi/plugins/cache/omc/oh-my-kimi
echo "Plugin cache cleared. Restart Codex CLI to fetch latest version."
# Keep only latest version
cd ~/.kimi/plugins/cache/omc/oh-my-kimi/
ls | sort -V | head -n -1 | xargs rm -rf
Fetch latest from GitHub and write to ~/.kimi/AGENTS.md:
WebFetch(url: "https://raw.githubusercontent.com/Yeachan-Heo/oh-my-kimi/main/docs/AGENTS.md", prompt: "Return the complete raw markdown content exactly as-is")
Remove legacy agents/commands plus the historical ~/.agents/skills tree if it overlaps with the canonical ${KIMI_HOME:-~/.codex}/skills install:
# Backup first (optional - ask user)
# mv ~/.kimi/agents ~/.kimi/agents.bak
# mv ~/.kimi/commands ~/.kimi/commands.bak
# mv ~/.agents/skills ~/.agents/skills.bak
# Or remove directly
rm -rf ~/.kimi/agents
rm -rf ~/.kimi/commands
rm -rf ~/.agents/skills
Note: Only remove if these contain oh-my-kimi-related files. If user has custom agents/commands/skills, warn them and ask before removing.
After applying fixes, inform user:
Fixes applied. Restart Codex CLI for changes to take effect.
data-ai
Kimi-native team worker protocol (ACK, mailbox, task lifecycle)
documentation
Persistent markdown project wiki stored under .omk/wiki with keyword search and lifecycle capture
development
URL-driven website cloning with visual + functional verification
testing
Structured visual QA verdict for screenshot-to-reference comparisons