midnight-plugin-utils:dependency-checker

Validate plugin and system dependencies against the current environment.

37|9|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-plugin-utils-dependency-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: midnight-plugin-utils:dependency-checker
Source: https://github.com/devrelaicom/midnight-expert/tree/main/plugins/midnight-plugin-utils/skills/dependency-checker
Command: npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-plugin-utils-dependency-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Detects and explains missing, disabled, or version-incompatible plugin and system dependencies so plugins can run reliably without blind failures.

Core Features & Use Cases

  • Declarative Validation: Reads each plugin's .claude-plugin/extends-plugin.json and cross-references installed_plugins, enabled plugins, and known marketplaces to determine dependency status.
  • System Tool Checks: Verifies presence and versions of CLI tools in PATH and tolerantly handles unknown version formats.
  • Actionable Output: Emits structured JSON, renders ASCII tables, and generates numbered resolution steps to guide installation or updates.
  • Use Case: Run after installing or updating plugins to confirm required plugins and CLI tools are present and version-compatible before deployment.

Quick Start

Run the dependency checker to validate all enabled plugins and produce a JSON report plus human-readable tables and resolution steps.

Frequently Asked Questions about midnight-plugin-utils:dependency-checker

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

FAQPage Schema
How do I check plugin dependencies and system CLI tools before deploying?

You can check plugin and system dependencies by validating declared requirements against the current environment, reading ~/.claude configuration and each plugin's extends-plugin.json, and verifying required CLI tools in PATH to detect missing or version-incompatible dependencies.

Why does my Claude plugin fail to run after installation?

Plugins fail when missing, disabled, or version-incompatible plugin and system dependencies go undetected. A dependency checker cross-references installed plugins and enabled plugins against declared semantic version constraints to identify exact resolution steps.

What is the best way to validate semantic version constraints for installed plugins?

Validating semantic version constraints involves evaluating each plugin's declared version requirements against the installed environment, producing structured JSON results and actionable resolution steps to guide updates or installations.

Does the dependency checker work with marketplace-scoped plugins?

Yes, dependency checking applies to enabled, installed, or marketplace-scoped plugins. It reads known marketplaces alongside ~/.claude configuration to determine marketplace-scoped plugin dependency status during install, update, or pre-deploy checks.

How do I fix missing CLI tools required by my plugins?

Fix missing CLI tools by running a dependency check to scan PATH for required system tools and generate numbered resolution steps. The output renders ASCII tables and structured JSON detailing absent tools and installation actions.