Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Plugin Health

ASecurity

Check an installed plugin's health — verify manifest SHA256 matches files on disk, detect tampering or corruption. Use when the user asks if a plugin is working, reports a bug, or wants to validate integrity. Triggers on "plugin X está funcionando?", "health plugin X", "status plugin X", "está ok o plugin Y?".

529 stars
0 votes
0 copies
0 views
Added 5/29/2026
ai-agentspythongogitapibackend

Works with

cliapi

Security Analysis

A100/100

Scanned 5/29/2026

$npx -y skills add evolution-foundation/evo-nexus --skill plugin-health --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Plugin Health?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Plugin Health
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/evolution-foundation-plugin-health/badge)](https://www.skillsdirectory.com/skills/evolution-foundation-plugin-health)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: plugin-health
description: Check an installed plugin's health — verify manifest SHA256 matches files on disk, detect tampering or corruption. Use when the user asks if a plugin is working, reports a bug, or wants to validate integrity. Triggers on "plugin X está funcionando?", "health plugin X", "status plugin X", "está ok o plugin Y?".
metadata:
  category: plugins
  version: 1.0.0
---

# Plugin Health

Run on-demand integrity check for a plugin. Compares `.install-manifest.json` SHA256 entries against actual files on disk. Detects tampering, partial corruption, or missing files.

## How to use

### Step 1 — Resolve the slug

If not given, list and ask:

```python
from dashboard.backend.sdk_client import evo

plugins = evo.get("/api/plugins")
```

### Step 2 — Run health check

```python
health = evo.get(f"/api/plugins/{slug}/health")
```

Response shape:

```json
{
  "status": "active" | "broken" | "routine_activation_pending",
  "reason": "sha_mismatch" | "missing_files" | null,
  "files": [".claude/agents/plugin-foo-agent.md", ...],  // if broken
  "checked_at": "..."
}
```

### Step 3 — Report

**If `active`:** plugin is healthy. Summarise: total files checked, all SHA256 matching, registered hooks/heartbeats/routines still wired.

**If `broken`:**
- List corrupted/missing files
- Suggest options:
  - Reinstall: `plugin-install` with same source URL (overwrites files, preserves data)
  - Uninstall + reinstall: clean slate
  - Manual fix: edit files back to original state (if user knows what was changed)

**If `routine_activation_pending`:** scheduler was offline during install. Tell user to start/restart scheduler.

## Error handling

- `HTTP 404 not_found` — plugin not installed.
- `HTTP 500 health_check_failed` — filesystem permission issue or manifest unreadable. Check `ADWs/logs/plugins/`.

## Notes for the agent

- Broken state doesn't auto-disable. Plugin files may still work partially. User should decide whether to act.
- If multiple plugins broken at once, likely the user did a git operation or `.claude/` migration. Health check is diagnostic, not autofix.

Attribution

evolution-foundationevolution-foundation
View sourceSee grades on GitHubMore from evolution-foundation →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →