health

Identify and report health issues in the blitz plugin across structure, hooks, sessions, and registry.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/lasswellt/cc-plugin-suite --skill health-lasswellt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/lasswellt/cc-plugin-suite/tree/main/skills/health
Command: npx skills add https://github.com/lasswellt/cc-plugin-suite --skill health-lasswellt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detect and report health issues in the blitz plugin, spanning structure, hooks, sessions, and registry.

Core Features & Use Cases

  • Structural checks that verify the plugin layout, required files, and session state.
  • Hook, registry, and session validation to prevent misconfigurations from impacting runtime behavior.
  • Use case: during development, run automated health checks to surface misconfigurations before deployment and after plugin updates.

Quick Start

Run the health check to validate the plugin's structural integrity and operational readiness.

Frequently Asked Questions about health

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

FAQPage Schema
How do I run a health check on my blitz plugin to validate its hooks and structure?

To run a blitz plugin health check, execute the diagnostic script to verify structural integrity, validate hook configurations, analyze sessions, and compare registry states. The process surfaces misconfigurations and outputs a concise report with actionable remediation steps.

What does plugin structural validation check for during blitz development?

Plugin structural validation checks the blitz plugin layout, required files, and session state to ensure operational readiness. It verifies the physical structure and configuration align with expected standards before runtime execution or deployment.

Why does my blitz plugin fail during runtime after a recent update?

Runtime failures after updates often stem from plugin registry mismatches or invalid hook configurations. Running a diagnostic health check identifies these specific misconfigurations across structure, sessions, and registry, providing actionable steps to resolve the issues.

Can I use automated diagnostics to prevent misconfigurations before deploying a blitz plugin?

Yes, you can use automated diagnostics to prevent misconfigurations by running health checks during development and testing. This validates hook setups, structural layouts, and registry states before deployment, ensuring end-to-end plugin reliability.

When do I need to perform a registry comparison for my blitz plugin?

You need to perform a registry comparison when diagnosing plugin operational issues or after applying updates. It verifies that the active registry state matches expected configurations, preventing registry mismatches from impacting runtime behavior.

What is the best way to identify hook misconfigurations in a blitz plugin?

The best way to identify hook misconfigurations is to run an automated hook validation diagnostic. This process analyzes the plugin's hook setups against expected configurations and highlights discrepancies in a concise health report.