Diagnose Claude Code plugin skill load, trigger, and runtime failures.
npx skills add https://github.com/iVintik/claude-plugin-ops --skill diagnose-ivintik
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/iVintik/claude-plugin-ops/tree/main/skills/diagnose Command: npx skills add https://github.com/iVintik/claude-plugin-ops --skill diagnose-ivintik
This Skill diagnoses why a Claude Code plugin or one of its skills fails to load, does not trigger when expected, errors at runtime, or behaves unexpectedly, turning vague user reports into concrete defect findings and actionable fixes.
Diagnose the plugin in the current directory for load, trigger, and hook problems and include --skill SKILL-NAME to focus the investigation.
High-intent search queries and answers about installing and using this skill.
Plugin skills fail to trigger due to weak or missing trigger phrases, malformed YAML frontmatter, or description-driven trigger failures. Diagnosing the issue involves validating the skill frontmatter, checking directory structure, and verifying the manifest to produce concrete defect findings and actionable fixes.
To debug silently failing hooks, check the hooks configuration and executables, inspect install status, and detect conflicting plugins. A diagnostic pass confirms hook configurations and produces a prioritized defect report with precise code or configuration changes.
Validating a plugin manifest involves verifying that .claude-plugin/plugin.json, required directories, and referenced files exist and are well-formed. This structure validation catches load errors and identifies missing components before runtime execution.
Yes, you can focus the investigation on a specific skill by applying the diagnostic to local or repository-based plugins. The process validates YAML frontmatter, detects weak trigger phrases, and checks agent tool lists to isolate the defect.
MCP tools become unavailable due to incorrect hooks configuration, remote repo issues, or conflicting plugins. Diagnosing the runtime context inspects install status, checks agent tool lists, and detects conflicts to restore tool availability.
Bare variables outside code blocks cause description-driven trigger failures. Fixing them requires validating YAML frontmatter, spotting the bare variables, and applying concrete code or configuration changes recommended by a defect report.
a-ariffScaffold Claude Code plugin directories with manifests and templates.
kollaboraiTrace Kollab plugin lifecycle events to diagnose loading and hook failures.
vuminhieuDiscover, analyze, and execute MCP capabilities across configured servers.
scooter-lacroixDebug Maestro hooks by verifying registration, inspecting files, and testing execution.
