plugin-health

Verify plugin integrity by comparing SHA256 hashes against on-disk files.

520|175|Updated Apr 8, 2026

Search Tags:#diagnostics #plugin management #integrity check #sha256 #plugin health #tamper detection #filesystem verification

Ready to run

npx skills add https://github.com/evolution-foundation/evo-nexus --skill plugin-health-evolution-foundation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-health
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/plugin-health
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill plugin-health-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plugin health checks prevent broken or tampered plugins from silently failing by confirming that the installed files still match their recorded integrity hashes.

Core Features & Use Cases

Integrity verification: Compares .install-manifest.json SHA256 entries against the actual files on disk to detect tampering or corruption.
Actionable diagnostics: Reports clear states like active, broken (with sha_mismatch or missing_files), or routine_activation_pending, so you know what to do next.
Common use cases: Use when a plugin appears not to work, when a user reports a plugin bug, or when you need to validate integrity after installs or filesystem/migration events.

Quick Start

Ask the AI to check plugin health for a specific plugin, for example: "Check the health of plugin 'my-plugin' and report whether it is active or broken."

Frequently Asked Questions about plugin-health

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

FAQPage Schema

How do I check if a plugin is broken or corrupted?▼

To check if a plugin is broken or corrupted, verify its integrity by comparing the SHA256 hashes recorded in the installation manifest against the actual files on disk. This detects any tampering or missing files causing the malfunction.

What does a SHA256 integrity mismatch mean for installed plugins?▼

A SHA256 integrity mismatch means the on-disk plugin files have been altered or corrupted since installation, resulting in a broken state. The diagnosis reports this as a sha_mismatch so you can take corrective action like reinstalling.

When should I run a plugin health check?▼

Run a plugin health check when a plugin appears not to work, after a user reports a bug, or following filesystem migrations and installations. It validates that the installed files still match their recorded integrity hashes to prevent silent failures.

How do I diagnose a plugin that is not working properly?▼

Diagnose a malfunctioning plugin by resolving its slug and calling the health endpoint to check filesystem verification. It returns an actionable diagnosis reporting active, broken with missing files, or sha_mismatch reasons.

Can I detect tampering in installed plugins using filesystem verification?▼

Yes, you can detect tampering using filesystem verification by matching manifest-recorded SHA256 hashes against on-disk files. This confirms whether the installation was corrupted or maliciously altered.