plugin-introspector

Analyze Claude Code plugin workflows to expose optimization opportunities.

3|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/hungrytech/hungrytech-claude-skills --skill plugin-introspector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-introspector
Source: https://github.com/hungrytech/hungrytech-claude-skills/tree/main/plugins/plugin-introspector/skills/plugin-introspector
Command: npx skills add https://github.com/hungrytech/hungrytech-claude-skills --skill plugin-introspector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

White-box monitoring and self-improvement for Claude Code workflow plugins enables end-to-end visibility into tool usage, prompts, token consumption, and execution patterns, and it generates data-driven improvement proposals to optimize performance, security, and reliability.

Core Features & Use Cases

  • End-to-end monitoring of plugin execution to identify bottlenecks, waste, and security risks
  • Data-driven improvement proposals via an orchestrated pipeline (improve/optimize) with meta-rules validation
  • Activated by keywords: "introspector", "monitor", "analyze plugin", "token usage", "dashboard", "evaluate", "optimize", "improve plugin", "security", "compliance"

Quick Start

Install and run the introspector to begin real-time monitoring and improvement generation for Claude Code plugins.

Frequently Asked Questions about plugin-introspector

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

FAQPage Schema
How do I monitor Claude Code plugin workflows for token waste and security risks?

White-box monitoring of Claude Code plugin workflows exposes tool usage, token consumption, and execution patterns. It identifies bottlenecks, waste, and security risks to provide actionable optimization opportunities across multi-agent pipelines.

What is the best way to analyze plugin execution and generate data-driven improvement proposals?

Data-driven improvement proposals are generated by an orchestrated pipeline that analyzes plugin execution. It enforces meta-rules validation and applies ROI-guided improvements to optimize performance, security, and reliability automatically.

Can I use the introspector plugin to evaluate compliance and security for multi-agent pipelines?

Yes, the introspector plugin evaluates compliance and security across multi-agent pipelines. It provides end-to-end visibility into execution patterns and enforces meta-rules to detect security risks and ensure workflow compliance.

Do I need jq installed to run the introspector plugin scripts?

Yes, jq is a required dependency to run the introspector plugin scripts. The scripts rely on jq to process and parse the JSON data extracted from Claude Code plugin workflows during monitoring and analysis.

How does white-box monitoring identify optimization opportunities in plugin workflows?

White-box monitoring identifies optimization opportunities by analyzing tool usage, prompts, and token consumption in real-time. It exposes hidden inefficiencies within the execution patterns and generates proposals guided by ROI metrics and meta-rules.

What are the limitations of using meta-rules validation for plugin workflow optimization?

Meta-rules validation is limited to the predefined constraints configured within the introspector's analysis pipeline. Optimization proposals are strictly ROI-guided, meaning changes without a clear performance, security, or reliability return are filtered out.