reflect

Audit Claude Code plugin structure, skills, hooks, and MCP configuration.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/iVintik/claude-plugin-ops --skill reflect-ivintik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/iVintik/claude-plugin-ops/tree/main/skills/reflect
Command: npx skills add https://github.com/iVintik/claude-plugin-ops --skill reflect-ivintik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect structural, knowledge, and configuration issues in a Claude Code plugin to surface regressions, missing references, and quality gaps before release.

Core Features & Use Cases

  • Structure validation: Checks plugin.json, skills directory presence, README.md/CLAUDE.md existence, and semantic consistency.
  • Skill and knowledge inspection: Validates SKILL.md frontmatter, ensures skill names match directories, verifies referenced knowledge files, and enforces knowledge size limits.
  • Hooks and MCP checks: Validates hooks JSON, script existence/executability, and MCP server configuration for required fields.
  • Usage examples: Run after adding new skills, changing hooks, or before publishing to detect regressions and produce a REFLECTIONS.md audit.

Quick Start

Run a comprehensive health audit of the current plugin and write findings to REFLECTIONS.md unless you pass --brief to produce only a summary.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I run a health check on a Claude Code plugin before publishing?

To run a plugin health check, use this skill to perform a comprehensive audit of your Claude Code plugin, validating structure, SKILL.md frontmatter, hooks JSON, and MCP configuration to surface regressions before release.

What does a Claude Code plugin audit inspect in the skills and knowledge directories?

A plugin audit inspects the skills and knowledge directories by validating YAML frontmatter, ensuring skill names match their directories, verifying referenced knowledge files exist, and enforcing knowledge size limits.

Can I validate Claude Code plugin hooks and MCP configuration automatically?

Yes, you can validate hooks and MCP configuration automatically by running the audit, which checks hooks JSON syntax, verifies script existence and executability, and validates MCP server configuration for required fields.

How do I generate an audit summary for a Claude Code plugin without writing a full report?

To generate a brief audit summary, run the plugin health check with the --brief flag, which outputs only a summary instead of writing the full findings to a REFLECTIONS.md file.

When should I audit my Claude Code plugin for structural and configuration issues?

You should audit your Claude Code plugin after adding new skills, updating hooks, modifying MCP configuration, or performing pre-release checks to detect structural regressions, missing references, and quality gaps.

What is the best way to find missing references in Claude Code plugin knowledge files?

The best way to find missing references is to run a comprehensive plugin health audit, which performs cross-reference checks in the skills and knowledge directories to surface unreferenced or missing files.