install-doctor

Scan project environments for plugin conflicts and MCP security risks.

7|Updated May 26, 2026
One-click install
npx skills add https://github.com/chrono-meta/forge-harness --skill install-doctor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: install-doctor
Source: https://github.com/chrono-meta/forge-harness/tree/main/plugins/fh-meta/skills/install-doctor
Command: npx skills add https://github.com/chrono-meta/forge-harness --skill install-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Installing meta-harness plugins into existing projects often leads to unexpected conflicts with pre-existing CLAUDE.md rules, custom skills, hook events, or audit practices that can break workflows or cause silent file overwrites. This skill eliminates guesswork by scanning your environment before and after installation to flag all potential issues before they cause problems.

Core Features & Use Cases

  • Pre and post-install environment scanning: Detects conflicts across 5 key areas: CLAUDE.md rule definitions, skill trigger vocabulary, hook event assignments, .claudeignore scope rules, and existing audit/log file formats.
  • MCP transport security checks: Flags unauthenticated HTTP/SSE MCP server configurations that expose local network ports to remote access risks.
  • Actionable diagnosis reports: Separates immediate action required items from recommended post-install checks, so you know exactly what to fix before proceeding with installation.
  • Use Case: If you want to add the fh-meta plugin to a project that already has custom PR review rules and existing Claude Code skills, run this skill first to confirm there are no overlapping triggers or conflicting audit practices that would disrupt your team's workflow.

Quick Start

Ask the AI to run the install-doctor skill to scan your current project environment for potential conflicts with the fh-meta meta-harness plugin before you proceed with installation.

Frequently Asked Questions about install-doctor

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

FAQPage Schema
How do I check for Claude Code plugin install conflicts before overwriting existing project rules?▼

To check for Claude Code plugin install conflicts, scan your environment for overlapping CLAUDE.md rules, custom skills, and hook events. This skill diagnoses potential silent overwrite risks and generates categorized reports separating immediate actions from post-install checks.

Why does installing a meta-harness plugin break my existing Claude Code hook events?▼

Installing a meta-harness plugin breaks existing Claude Code hook events when new assignments overlap with your pre-existing configurations. Environment scanning identifies these conflicting hook event definitions and flags them before the installation disrupts your workflow.

Can I detect unauthenticated MCP HTTP transport security vulnerabilities before plugin installation?▼

You can detect unauthenticated MCP HTTP transport security vulnerabilities by validating server configurations during the environment scan. This process flags exposed local network ports that allow remote access risks before you proceed with plugin installation.

How do I scan .claudeignore scope rules for conflicts with new audit log practices?▼

To scan .claudeignore scope rules for conflicts, run an environment diagnosis that checks existing audit and log file formats against incoming plugin definitions. This detects overlapping rules and generates an actionable report to prevent silent workflow breaks.

What is the best way to avoid silent file overwrites when adding custom skills to an existing Claude Code project?▼

The best way to avoid silent file overwrites is to perform a pre-install environment scan that detects overlapping trigger vocabulary and conflicting definitions. This diagnosis separates immediate action required items from recommended post-install checks to ensure workflow safety.