plugin-audit

To audit vercel-plugin performance, the skill extracts tool calls from conversation logs, tests hook matching, and checks plugin cache staleness. It requires access to your project logs and the plugin's hooks to identify skill injection gaps.

Skill injection gaps occur when pattern coverage is incomplete or deduplication issues exist. The audit detects these gaps by extracting and analyzing tool calls from your real-world Claude Code conversation logs.

The best way to check plugin cache staleness is by verifying the installed vercel-plugin cache against the dev version. This audit directly compares the two to detect if your project is running an outdated plugin configuration.

Yes, you can test hook matching against real conversation logs. The audit extracts tool calls from your project history and validates them against the plugin's hooks to identify pattern coverage gaps.

Yes, you need access to project logs and the plugin's hooks. The audit relies on extracting actual tool calls from conversation logs to evaluate real-world vercel-plugin performance and identify coverage gaps.