doctor

Detect and repair Kronon-Forge installation problems by scanning plugin versions and configuration files.

Updated Apr 10, 2026

Search Tags:#hooks #plugin #cache #installation #diagnose #forge #kronon

Ready to run

npx skills add https://github.com/lpjhelder/kronon-forge --skill doctor-lpjhelder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/lpjhelder/kronon-forge/tree/main/skills/doctor
Command: npx skills add https://github.com/lpjhelder/kronon-forge --skill doctor-lpjhelder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Doctor skill quickly identifies and repairs installation issues that prevent Kronon‑Forge from functioning correctly.

Core Features & Use Cases

Version verification: Detects missing, outdated, or multiple cached plugin versions.
Legacy hook detection: Finds obsolete hook scripts and configuration entries that can cause conflicts.
Cache cleanup: Spots and removes stale plugin caches.
Configuration validation: Checks AGENTS.md and related settings for correctness.
Legacy content removal: Identifies old agents, commands, and skill directories that may interfere with the current setup.

Quick Start

Run the doctor skill to perform a full installation health check and apply automatic fixes.

Frequently Asked Questions about doctor

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

FAQPage Schema

How do I diagnose Kronon-Forge installation problems and fix plugin conflicts?▼

To diagnose Kronon-Forge installation problems, run a health check that scans plugin versions, configuration files, legacy hook scripts, and cache directories in your local ~/.kronon environment. It automatically detects and repairs conflicts caused by missing, outdated, or multiple cached plugin versions.

Why does Kronon-Forge fail to function correctly after an update?▼

Kronon-Forge failures after updates often stem from obsolete hook scripts, stale plugin caches, or old agent directories. Scanning the local environment detects these legacy entries and configuration mismatches, allowing automatic removal of conflicting content to restore functionality.

How do I clean up stale plugin caches and legacy hook scripts in Kronon?▼

Clean up stale plugin caches and legacy hook scripts in Kronon by running an automated repair scan on the ~/.kronon directory. This process spots obsolete cached files and configuration entries, safely removing them to prevent conflicts with the current setup.

Do I need npm to verify installed Kronon-Forge plugin versions?▼

Yes, you need npm installed to verify Kronon-Forge plugin versions. The diagnosis process requires npm to compare your locally installed plugin versions against the latest available versions, detecting any missing or outdated packages in your environment.

What permissions are required to repair a Kronon-Forge installation?▼

Repairing a Kronon-Forge installation requires read and write access to the ~/.kronon directory. This access allows the diagnostic tool to scan configuration files, validate AGENTS.md settings, clear caches, and apply automatic fixes to legacy directories.